NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
victorhortalive
Oct 20, 2010Aspirant
Pro Pioneer - Spin Down working or not ?
I can't seem to get any response from my Pro Pioneer on Spin Down.
Either it's working and doesn't want to tell me OR it's not working !
I have 4 Seagate 2TB ST32000542AS drives with a 60min spin down. Radiator is 4.2.15.
On the NV and NV+ the drives would indicate "Sleeping" on FrontView and RAIDar - plus the NAS drive lights would dim.
Should the Pro do the same ?
Nothing is accessing the Pro as it's all Video stuff and all the Video Streamers are off.
Either it's working and doesn't want to tell me OR it's not working !
I have 4 Seagate 2TB ST32000542AS drives with a 60min spin down. Radiator is 4.2.15.
On the NV and NV+ the drives would indicate "Sleeping" on FrontView and RAIDar - plus the NAS drive lights would dim.
Should the Pro do the same ?
Nothing is accessing the Pro as it's all Video stuff and all the Video Streamers are off.
35 Replies
Replies have been turned off for this discussion
- mdgm-ntgrNETGEAR Employee RetiredDo you seen spindown entries in the logs (Status > Logs > Download all Logs)?:
MDGM-NAS:~# cat /var/log/daemon.log | grep -i spinning
Jun 18 12:15:04 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 12:15:11 MDGM-NAS noflushd[12929]: Disks spinning up after 0 minutes.
Jun 18 12:20:24 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 12:48:16 MDGM-NAS noflushd[12929]: Disks spinning up after 27 minutes.
Jun 18 12:53:44 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 13:09:01 MDGM-NAS noflushd[12929]: Disks spinning up after 15 minutes.
Jun 18 13:21:36 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 13:49:43 MDGM-NAS noflushd[12929]: Disks spinning up after 28 minutes.
Jun 18 13:56:58 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 14:11:50 MDGM-NAS noflushd[12929]: Disks spinning up after 14 minutes.
Jun 18 14:26:08 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 14:31:05 MDGM-NAS noflushd[12929]: Disks spinning up after 4 minutes.
Jun 18 14:48:01 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 15:03:34 MDGM-NAS noflushd[12929]: Disks spinning up after 15 minutes.
Jun 18 15:13:04 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 15:26:26 MDGM-NAS noflushd[12929]: Disks spinning up after 13 minutes.
Jun 18 15:32:29 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 15:33:26 MDGM-NAS noflushd[12929]: Disks spinning up after 0 minutes.
Jun 18 15:38:27 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 15:42:14 MDGM-NAS noflushd[12929]: Disks spinning up after 3 minutes.
Jun 18 15:47:22 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 16:16:24 MDGM-NAS noflushd[12929]: Disks spinning up after 29 minutes.
Jun 18 16:28:41 MDGM-NAS noflushd[12929]: Spinning down disks.
Jun 18 16:36:38 MDGM-NAS noflushd[12929]: Disks spinning up after 7 minutes. - victorhortaliveAspirantWhere specifically in the 41 files from the system logs would I find the spindown entries ?
- mdgm-ntgrNETGEAR Employee Retireddaemon.log (that's a file I used the cat shell command to read using SSH) would be one place. system.log would be another.
Search for "Spinning" in the file. - victorhortaliveAspirantThanks.
Nothing in system.log wrt spinning.
It wakes up at 7.10 - lots of entries.
From FrontView I have :
Wed Oct 20 09:37:28 CEST 2010 Automatic disk spin-down enabled.
Wed Oct 20 09:37:11 CEST 2010 Automatic disk spin-down disabled.
Tue Oct 19 12:02:09 CEST 2010 Successfully applied new network settings.
Wed Oct 20 07:10:55 CEST 2010 System is up.
(note the weird entry from Oct 19 !)
No entry in the system.log after 7.10 except :
Oct 20 07:15:23 Pippin kernel: Machine check events logged
Oct 20 08:00:05 Pippin ntpdate[3186]: step time server 207.211.82.130 offset 0.117277 sec
Oct 20 09:37:11 Pippin kernel: sk98lin 0000:01:00.0: PME# enabled
Oct 20 09:37:11 Pippin kernel: sk98lin 0000:02:00.0: PME# enabled
Oct 20 09:37:28 Pippin kernel: sk98lin 0000:01:00.0: PME# enabled
Oct 20 09:37:28 Pippin kernel: sk98lin 0000:02:00.0: PME# enabled
Oct 20 12:00:06 Pippin ntpdate[6477]: no server suitable for synchronization found - mdgm-ntgrNETGEAR Employee RetiredHow long have you set it to wait before spinning down the disks?
- victorhortaliveAspirant60mins.
Set at 9.37 but nothing listed from 9.37 till 12.06.
It was also set to spin down yesterday - no log entries for that either. - mdgm-ntgrNETGEAR Employee RetiredI'll try to use disk spin-down tonight on the Ultra 6 (different to the Pro, I know, but I don't have a Pro - hopefully someone with a Pro can check on that as that would be better). I haven't tried it for a while but it did work for me using older firmware. I'll try with 4.2.15.
You don't use your Pro as a WINS server do you? If the disks are being used (for whatever reason) the NAS won't spin down. - victorhortaliveAspirantThanks. No, nothing on there except Video stuff.
- victorhortaliveAspirantJust a thought :
It seems that each time I did something wrt spindown there WAS an entry in the system log, but no mention of spindown.
viz :
Oct 20 09:37:11 Pippin kernel: sk98lin 0000:01:00.0: PME# enabled
Oct 20 09:37:11 Pippin kernel: sk98lin 0000:02:00.0: PME# enabled
Oct 20 09:37:28 Pippin kernel: sk98lin 0000:01:00.0: PME# enabled
Oct 20 09:37:28 Pippin kernel: sk98lin 0000:02:00.0: PME# enabled
What are these ? - mdgm-ntgrNETGEAR Employee RetiredSet spin-down to 60 minutes and my disks didn't spin-down last night either. Guess there must be a problem with spindown in 4.2.15.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!