Pro Pioneer - Spin Down working or not ?

Thanks. Was there a version of Radiator where spin down did work ?

Yes, I think I tested it on 4.2.12 or 4.2.13 or both. I didn't try on 4.2.14 but I'd still try 4.2.14 first.

It's started working for me this evening. Interesting. Maybe someone else in the house was using the NAS.

MDGM-NAS:~# cat /var/log/daemon.log | grep -i "spinning"
Oct 21 18:58:27 MDGM-NAS noflushd[28915]: Spinning down disks.
Oct 21 18:58:37 MDGM-NAS noflushd[28915]: Disks spinning up after 0 minutes.
Oct 21 20:00:31 MDGM-NAS noflushd[28915]: Spinning down disks.
Oct 21 20:08:14 MDGM-NAS noflushd[28915]: Disks spinning up after 7 minutes.
Oct 21 21:20:10 MDGM-NAS noflushd[28915]: Spinning down disks.
Oct 21 22:12:04 MDGM-NAS noflushd[28915]: Disks spinning up after 51 minutes.

Now I find some entries in the system.log from last night where there IS some spindown activity, but not what was requested :

Oct 20 22:34:19 Pippin noflushd[4472]: Spinning down disks.
Oct 20 22:34:34 Pippin noflushd[4472]: Disks spinning up after 0 minutes.
Oct 20 23:35:24 Pippin noflushd[4472]: Spinning down disks.
Oct 20 23:38:13 Pippin noflushd[4472]: Disks spinning up after 2 minutes.

Que ?

I saw some references to WINS server being an issue - this NAS isn't a WINS server, but I deleted references to the one that is.

Well look at this - it waits till 7.30pm and then does something correctly.

Oct 21 19:39:27 Pippin noflushd[1888]: Spinning down disks.
Oct 22 00:00:12 Pippin noflushd[1888]: Disks spinning up after 260 minutes.

Clearly not right but at least it does act.

Does anyone know why the ReadyNas keeps spinning up constantly? Here's an excerpt from my log files last night; there are no lines omitted:
Oct 22 00:08:45 JitterBug noflushd[1702]: Spinning down disks.
Oct 22 00:08:55 JitterBug noflushd[1702]: Disks spinning up after 0 minutes.
Oct 22 00:49:55 JitterBug noflushd[1702]: Spinning down disks.
Oct 22 00:53:11 JitterBug noflushd[1702]: Disks spinning up after 3 minutes.
Oct 22 01:34:11 JitterBug noflushd[1702]: Spinning down disks.
Oct 22 02:05:13 JitterBug noflushd[1702]: Disks spinning up after 31 minutes.
Oct 22 02:46:11 JitterBug noflushd[1702]: Spinning down disks.
Oct 22 03:06:08 JitterBug noflushd[1702]: Disks spinning up after 19 minutes.
Oct 22 03:46:32 JitterBug noflushd[1702]: Spinning down disks.
Oct 22 04:00:13 JitterBug noflushd[1702]: Disks spinning up after 13 minutes.
Oct 22 04:40:34 JitterBug noflushd[1702]: Spinning down disks.
Oct 22 04:50:46 JitterBug noflushd[1702]: Disks spinning up after 10 minutes.
Oct 22 05:43:59 JitterBug noflushd[1702]: Spinning down disks.
Oct 22 06:13:56 JitterBug noflushd[1702]: Disks spinning up after 29 minutes.

I have an NVX running 4.2.13.

I can't find any logs where any activity occurred during these times and I am positive no one was accessing the device (there are only two users in the house and we were both in bed all night). There are no scheduled background tasks running, either, and I have time synchronization turned off.

This certainly is not saving much power and it's really bad for the disks.

I found on other threads that WINS had something to do with it, possibly.
Is your NAS a WINS server ? Turn it off.
Is there a reference to some other WINS server in the NAS setup ? Delete it.

See if that makes a difference.

However, I've just come back after being away for several hours and my Pro's drives are still not sleeping - so what do I know.

You might want to contact tech support for advice and post your case number. They would likely know a list of common problems that can cause disk spin-down to stop working.

Do you use iSCSI?

For the second day running there was some spindown, but not until 8pm or so.

viz :

Oct 22 19:23:09 Pippin noflushd[1875]: Spinning down disks.
Oct 22 19:23:23 Pippin noflushd[1875]: Disks spinning up after 0 minutes.
Oct 22 20:00:06 Pippin ntpdate[13036]: no server suitable for synchronization found
Oct 22 20:24:22 Pippin noflushd[1875]: Spinning down disks.
Oct 23 00:00:12 Pippin noflushd[1875]: Disks spinning up after 215 minutes.

I'm wondering if the time server has any bearing so I've changed the server from netgear to time.gov.

mdgm wrote:
You might want to contact tech support for advice and post your case number. They would likely know a list of common problems that can cause disk spin-down to stop working. Do you use iSCSI?

Boy, do I wish that were the case! I've been trying to get support to help me with this case for two months! They have no idea, and their suggestions are ridiculous! I'm on my fourth case regarding this issue. One timed out and closed while I was waiting for escalated help, one was escalated and then cancelled when they RMA'd my device (which didn't solve any problems), one I had to close because the tech refused to help me or escalate my case, and one is awaiting response from the escalation team. The current case number is 13478254.


I am not using iSCSI, it is not a WINS server, I do not have scheduled tasks running, I have time synchronization turned off, and no one is accessing the device.

-Robert