Riddle me this.  Are my drives spinning or not?  The lights say yes, the lack of temp says no?  I just walked in the door, nobody home all day so nothing should have been accessing anything.  Here's my logs from after mover stopped this morning:

 

 

 

 

 

Mar  4 05:41:20 NAS1 kernel: mdcmd (120): spindown 3

Mar  4 06:00:34 NAS1 kernel: mdcmd (121): spindown 1

Mar  4 06:00:34 NAS1 kernel: mdcmd (122): spindown 2

Mar  4 06:00:43 NAS1 kernel: mdcmd (123): spindown 0

Mar  4 06:00:43 NAS1 kernel: mdcmd (124): spindown 4

Mar  4 06:02:12 NAS1 emhttp: shcmd (200): /usr/sbin/hdparm -y /dev/sdh &> /dev/null

Mar  4 09:08:00 NAS1 kernel: mdcmd (125): spindown 1

Mar  4 09:08:00 NAS1 kernel: mdcmd (126): spindown 2

Mar  4 09:24:34 NAS1 kernel: EXT4-fs (loop0): error count since last fsck: 54

Mar  4 09:24:34 NAS1 kernel: EXT4-fs (loop0): initial error at time 1410555868: ext4_lookup:1437: inode 31

Mar  4 09:24:34 NAS1 kernel: EXT4-fs (loop0): last error at time 1410804989: ext4_lookup:1437: inode 31

Mar  4 11:53:17 NAS1 kernel: mdcmd (127): spindown 1

Mar  4 11:53:18 NAS1 kernel: mdcmd (128): spindown 2

Mar  4 13:32:39 NAS1 kernel: mdcmd (129): spindown 1

Mar  4 13:32:40 NAS1 kernel: mdcmd (130): spindown 2

Mar  4 14:28:43 NAS1 kernel: mdcmd (131): spindown 1

Mar  4 14:28:44 NAS1 kernel: mdcmd (132): spindown 2

Mar  4 15:42:49 NAS1 sshd[3227]: Accepted publickey for root from <removed>

Adding this and another image which is showing Parity not spinning now, and temps on all drives:

Mar  4 15:51:48 NAS1 kernel: mdcmd (133): spindown 0

 

Ok,

 

 

So, in an effort to make me look silly, all my drives spun down, and according to the gui are remaining down. since just before 5pm.

 

 

 

Mar  4 16:20:34 NAS1 kernel: mdcmd (134): spindown 4

Mar  4 16:20:40 NAS1 kernel: mdcmd (135): spindown 3

Mar  4 16:59:58 NAS1 kernel: mdcmd (136): spindown 1

Mar  4 16:59:58 NAS1 kernel: mdcmd (137): spindown 2

 

 

 

 

 

I'm still seeing my machine awake a lot of times, when no other client/connection is being done or the last one was hours ago.

 

Looking into the syslog, the S3 script says that there's still an active disk. And in the WebUI the parity disk is showing temperature info.

 

Any guidance? I think I saw somewhere that we should not use the hdparm to check on disks, but that's exactly what the sleep script does. Should we replace that with an http call?

 

Thanks,

All, the spin down issue that this thread was all about was definitely solved.  Those still experiencing this issue are in one of a few camps:

 

1)  An application on the system or on another system is doing something to keep disks spinning.

2)  A foreign script / plugin is manipulating hdparm (e.g. S3)

3)  Another problem is causing this on your system.

 

If you've eliminated #1 and #2 from your possible scenarios, then please post a new defect report and include a system log / screenshot of the webGui showing the issue in question.

 

Thanks!!

don't know if this is weird or not, but i haven't had a spinup log entry for nearly 2 days

don't know if this is weird or not, but i haven't had a spinup log entry for nearly 2 days

I thought that you only got spinup messages in the log if you do an explicit spinup from the GUI?  I do not see them in normal operation.

hence i wasn't sure if it was weird or not, just an observation that i made now i've got a graphical representation of chosen log entries in an external graylog server instance.

All, the spin down issue that this thread was all about was definitely solved.  Those still experiencing this issue are in one of a few camps:

 

1)  An application on the system or on another system is doing something to keep disks spinning.

2)  A foreign script / plugin is manipulating hdparm (e.g. S3)

3)  Another problem is causing this on your system.

 

If you've eliminated #1 and #2 from your possible scenarios, then please post a new defect report and include a system log / screenshot of the webGui showing the issue in question.

 

Thanks!!

 

Thanks for the feedback Jonp,

 

I definitely can observe that the machine is now much more stable, in regards to disk spin down. Like you said, this might be well the S3 script (foreign ).

Any recommendation on something to replace the hdparm to check the disk status? Any web call to use instead?

 

Thanks,

anthonws

 

All, the spin down issue that this thread was all about was definitely solved.  Those still experiencing this issue are in one of a few camps:

 

1)  An application on the system or on another system is doing something to keep disks spinning.

2)  A foreign script / plugin is manipulating hdparm (e.g. S3)

3)  Another problem is causing this on your system.

 

If you've eliminated #1 and #2 from your possible scenarios, then please post a new defect report and include a system log / screenshot of the webGui showing the issue in question.

 

Thanks!!

 

Thanks for the feedback Jonp,

 

I definitely can observe that the machine is now much more stable, in regards to disk spin down. Like you said, this might be well the S3 script (foreign [emoji14]).

Any recommendation on something to replace the hdparm to check the disk status? Any web call to use instead?

 

Thanks,

anthonws

Unfortunately I don't have an answer on that right now.