It happened a while ago, can't remember when exactly, but it worked before.

 

Drive sdc never spins down anymore, not even if you press the green button in the gui manually. There are no files in use, and I cannot see even a attempt to spin down in the logs (and no hint why it does not happen too)

 

Usually you will find entries like this:

pr 27 07:09:57 F emhttpd: spinning up /dev/sdd
Apr 27 07:09:57 F emhttpd: spinning up /dev/sdf
Apr 27 07:09:57 F emhttpd: spinning up /dev/sdg
Apr 27 07:10:10 F emhttpd: read SMART /dev/sdg
Apr 27 07:10:10 F emhttpd: read SMART /dev/sdd
Apr 27 07:10:10 F emhttpd: read SMART /dev/sde
Apr 27 07:10:10 F emhttpd: read SMART /dev/sdf
Apr 27 07:14:16 F webGUI: Successful login user root from 192.168.0.26
Apr 27 07:14:53 F kernel: mdcmd (48): set md_num_stripes 1280
Apr 27 07:14:53 F kernel: mdcmd (49): set md_queue_limit 80
Apr 27 07:14:53 F kernel: mdcmd (50): set md_sync_limit 5
Apr 27 07:14:53 F kernel: mdcmd (51): set md_write_method
Apr 27 07:14:59 F kernel: mdcmd (52): set md_num_stripes 1280
Apr 27 07:14:59 F kernel: mdcmd (53): set md_queue_limit 80
Apr 27 07:14:59 F kernel: mdcmd (54): set md_sync_limit 5
Apr 27 07:14:59 F kernel: mdcmd (55): set md_write_method
Apr 27 07:15:25 F flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Apr 27 07:40:35 F emhttpd: spinning down /dev/sdd
Apr 27 07:40:35 F emhttpd: spinning down /dev/sdf
Apr 27 07:40:35 F emhttpd: spinning down /dev/sde
Apr 27 07:40:35 F emhttpd: spinning down /dev/sdg

Note that sdc never shows up in the list!!!

All drives (including sdc) are in the same "wakeup group", but sdc runs and runs and runs..

The drive only contains movies, the only access I could see was from them folder caching plugin now and then.

I attach diagnostics, but I doubt there is anything in there (or maybe I have overlooked something?)

 

f-diagnostics-20240427-0848.zip

Nobody has an idea???

next try here:

 

Today I have rebooted UNRAID and guess what? sdc was able to spin down again!!!

But, sadly, not for long.

After some hours, the syslog showed:

May 15 15:28:23 F emhttpd: spinning down /dev/sdd
May 15 15:28:23 F emhttpd: spinning down /dev/sdf
May 15 15:28:23 F emhttpd: spinning down /dev/sde
May 15 15:28:23 F emhttpd: spinning down /dev/sdg
May 15 15:28:23 F emhttpd: spinning down /dev/sdc
May 15 16:00:02 F emhttpd: spinning up /dev/sdd
May 15 16:00:02 F emhttpd: spinning up /dev/sdf
May 15 16:00:02 F emhttpd: spinning up /dev/sde
May 15 16:00:02 F emhttpd: spinning up /dev/sdc
May 15 16:00:20 F kernel: ata52: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
May 15 16:00:20 F kernel: ata52.00: configured for UDMA/133
May 15 16:00:20 F emhttpd: sdspin /dev/sdc up: 1
May 15 16:00:20 F emhttpd: read SMART /dev/sdg
May 15 16:00:20 F emhttpd: read SMART /dev/sdd
May 15 16:00:20 F emhttpd: read SMART /dev/sde
May 15 16:00:20 F emhttpd: read SMART /dev/sdf
May 15 16:00:20 F emhttpd: read SMART /dev/sdc
May 15 16:33:07 F emhttpd: spinning down /dev/sdd
May 15 16:33:07 F emhttpd: spinning down /dev/sdf
May 15 16:33:07 F emhttpd: spinning down /dev/sde
May 15 16:33:07 F emhttpd: spinning down /dev/sdg

since this message, no attempt to spin down sdc happens anymore!

What is this and how can I get rid of it (rebooting every few hours is NOT a valid solution!)

(Obviously sdc takes almost 20s to spin up, is there any timeout configured that makes UNRAID to get nervous and black list this disk? )

 

Edited May 15, 20242 yr by MAM59

To close this case: problem solved!

 

I just moved the drive to a different bay within the same controller. Since then, spindown works flawlessly again.

 

There were no other errors besides "no to spindown", so I still dont know what happened. But at least it is gone now .