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.

Do you seen spindown entries in the logs (Status > Logs > Download all Logs)?:MDGM-NAS:~# cat /var/log/daemon.log | grep -i spinningJun 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.

Where specifically in the 41 files from the system logs would I find the spindown entries ?

daemon.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.

Thanks.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 loggedOct 20 08:00:05 Pippin ntpdate[3186]: step time server 207.211.82.130 offset 0.117277 secOct 20 09:37:11 Pippin kernel: sk98lin 0000:01:00.0: PME# enabledOct 20 09:37:11 Pippin kernel: sk98lin 0000:02:00.0: PME# enabledOct 20 09:37:28 Pippin kernel: sk98lin 0000:01:00.0: PME# enabledOct 20 09:37:28 Pippin kernel: sk98lin 0000:02:00.0: PME# enabledOct 20 12:00:06 Pippin ntpdate[6477]: no server suitable for synchronization found

How long have you set it to wait before spinning down the disks?

Pro Pioneer - Spin Down working or not ?

35 Replies

Replies have been turned off for this discussion

PeteCress
Apprentice
Dec 23, 2010
victorhortaliveson wrote:
...CC34 to CC35- had to use the force method...

I had to use the force method too.

Here are some notes: http://tinyurl.com/2fox2jp
dandan123
Aspirant
Jun 18, 2011
I have found something in cat /var/log/auth.log|grep -i cron

.....

Jun 18 16:08:01 NAS-Net CRON[27744]: (pam_unix) session opened for user root by (uid=0)
Jun 18 16:08:01 NAS-Net CRON[27744]: (pam_unix) session closed for user root
Jun 18 16:09:01 NAS-Net CRON[27768]: (pam_unix) session opened for user root by (uid=0)
Jun 18 16:09:01 NAS-Net CRON[27768]: (pam_unix) session closed for user root
Jun 18 16:17:01 NAS-Net CRON[28019]: (pam_unix) session opened for user root by (uid=0)
Jun 18 16:17:01 NAS-Net CRON[28019]: (pam_unix) session closed for user root
Jun 18 16:23:01 NAS-Net CRON[28184]: (pam_unix) session opened for user root by (uid=0)
Jun 18 16:23:01 NAS-Net CRON[28184]: (pam_unix) session closed for user root
Jun 18 16:38:01 NAS-Net CRON[28607]: (pam_unix) session opened for user root by (uid=0)
Jun 18 16:38:01 NAS-Net CRON[28607]: (pam_unix) session closed for user root
Jun 18 16:39:01 NAS-Net CRON[28637]: (pam_unix) session opened for user root by (uid=0)
Jun 18 16:39:01 NAS-Net CRON[28637]: (pam_unix) session closed for user root
Jun 18 16:53:01 NAS-Net CRON[29044]: (pam_unix) session opened for user root by (uid=0)
Jun 18 16:53:01 NAS-Net CRON[29044]: (pam_unix) session closed for user root
Jun 18 17:08:01 NAS-Net CRON[29473]: (pam_unix) session opened for user root by (uid=0)
Jun 18 17:08:01 NAS-Net CRON[29473]: (pam_unix) session closed for user root
Jun 18 17:09:01 NAS-Net CRON[29496]: (pam_unix) session opened for user root by (uid=0)
Jun 18 17:09:01 NAS-Net CRON[29496]: (pam_unix) session closed for user root
Jun 18 17:17:01 NAS-Net CRON[30077]: (pam_unix) session opened for user root by (uid=0)
Jun 18 17:17:01 NAS-Net CRON[30077]: (pam_unix) session closed for user root
Jun 18 17:23:01 NAS-Net CRON[30758]: (pam_unix) session opened for user root by (uid=0)
Jun 18 17:23:01 NAS-Net CRON[30758]: (pam_unix) session closed for user root
Jun 18 17:38:01 NAS-Net CRON[31504]: (pam_unix) session opened for user root by (uid=0)
Jun 18 17:38:01 NAS-Net CRON[31504]: (pam_unix) session closed for user root
Jun 18 17:39:01 NAS-Net CRON[31636]: (pam_unix) session opened for user root by (uid=0)
Jun 18 17:39:01 NAS-Net CRON[31636]: (pam_unix) session closed for user root
alldidasmc
Aspirant
Jul 13, 2011
Yep, I have those same lines in my auth file, as well. No one has been able to give me any explanation for why the root user keeps opening and closing sessions in less than one second,

-Robert
dandan123
Aspirant
Aug 22, 2011
For me is working spin-down after I changed one HDD from 1T to 2T. So, now I have 2T Segate HDDs.
alldidasmc
Aspirant
Sep 09, 2011
dandan,

You've checked the LOGs and you're sure your HD's are not spinning up? Check the System log. Close examination of the LOG files usually reveals that the drives are constantly being spun-up for no reason, so you should be sure if you don't want your drives destroyed!

-Robert

Forum Discussion

Pro Pioneer - Spin Down working or not ?

35 Replies

Related Content

RBR50 Firmware Update page just spins

netdata NT not working

Spinning up shortly after each Spinning down

Stop spin-down

Booting Spinning Up

NETGEAR Academy

ProSupport for Business