March 5, 20215 yr Since 6.9.0 no SATA disks spin down in an array. Every 1 hour I do see the commands in syslog to spin down the disks, but they don't spin down. I stopped all docker containers, removed plugins to the minimum (Community Applications, Unassigned Devices, User Scripts, Nerd Tools for screen and python), no fancy fan scripts. The disks simply ignore the spin down commands. HBA is LSI 9300-8e, disks are mixed 6TB to 2TB. It worked for all years here up to and including 6.8.3. Now with 6.9.0 it stopped. Is there a way to brute force spin down SATA devices? If there's none I'm forced to go back to 6.8.3. IMHO, it's one of the relevant parts of Unraid to spin down unused disks. Mar 5 04:59:18 TowerVM02 emhttpd: spinning down /dev/sde Mar 5 04:59:36 TowerVM02 emhttpd: spinning down /dev/sdi Mar 5 04:59:44 TowerVM02 emhttpd: spinning down /dev/sdw Mar 5 05:00:47 TowerVM02 emhttpd: spinning down /dev/sdp Mar 5 05:00:58 TowerVM02 emhttpd: spinning down /dev/sdk Mar 5 05:01:03 TowerVM02 emhttpd: spinning down /dev/sdj Mar 5 05:01:11 TowerVM02 emhttpd: spinning down /dev/sdu Mar 5 05:01:18 TowerVM02 emhttpd: spinning down /dev/sdv Mar 5 05:01:51 TowerVM02 emhttpd: spinning down /dev/sdb Mar 5 05:01:55 TowerVM02 emhttpd: spinning down /dev/sdh Mar 5 05:01:56 TowerVM02 emhttpd: spinning down /dev/sds Mar 5 05:02:01 TowerVM02 emhttpd: spinning down /dev/sdy Mar 5 05:02:01 TowerVM02 emhttpd: spinning down /dev/sdq Mar 5 05:02:03 TowerVM02 emhttpd: spinning down /dev/sdc Mar 5 05:02:08 TowerVM02 emhttpd: spinning down /dev/sdr Mar 5 05:02:10 TowerVM02 emhttpd: spinning down /dev/sdo Mar 5 05:02:11 TowerVM02 emhttpd: spinning down /dev/sdx Mar 5 05:02:11 TowerVM02 emhttpd: spinning down /dev/sdl Mar 5 05:02:13 TowerVM02 emhttpd: spinning down /dev/sdf Mar 5 05:02:14 TowerVM02 emhttpd: spinning down /dev/sdd Mar 5 05:02:14 TowerVM02 emhttpd: spinning down /dev/sdn Mar 5 05:42:15 TowerVM02 emhttpd: spinning down /dev/sdm Mar 5 05:42:15 TowerVM02 emhttpd: spinning down /dev/sdg Mar 5 05:42:15 TowerVM02 emhttpd: spinning down /dev/sdt # Nothing between here Mar 5 05:59:19 TowerVM02 emhttpd: spinning down /dev/sde Mar 5 05:59:37 TowerVM02 emhttpd: spinning down /dev/sdi Mar 5 05:59:45 TowerVM02 emhttpd: spinning down /dev/sdw Mar 5 06:00:48 TowerVM02 emhttpd: spinning down /dev/sdp Mar 5 06:00:59 TowerVM02 emhttpd: spinning down /dev/sdk Mar 5 06:01:04 TowerVM02 emhttpd: spinning down /dev/sdj Mar 5 06:01:12 TowerVM02 emhttpd: spinning down /dev/sdu Mar 5 06:01:19 TowerVM02 emhttpd: spinning down /dev/sdv Mar 5 06:01:52 TowerVM02 emhttpd: spinning down /dev/sdb Mar 5 06:01:56 TowerVM02 emhttpd: spinning down /dev/sdh Mar 5 06:01:58 TowerVM02 emhttpd: spinning down /dev/sds Mar 5 06:02:02 TowerVM02 emhttpd: spinning down /dev/sdy Mar 5 06:02:02 TowerVM02 emhttpd: spinning down /dev/sdq Mar 5 06:02:04 TowerVM02 emhttpd: spinning down /dev/sdc Mar 5 06:02:09 TowerVM02 emhttpd: spinning down /dev/sdr Mar 5 06:02:11 TowerVM02 emhttpd: spinning down /dev/sdo Mar 5 06:02:13 TowerVM02 emhttpd: spinning down /dev/sdx Mar 5 06:02:13 TowerVM02 emhttpd: spinning down /dev/sdl Mar 5 06:02:14 TowerVM02 emhttpd: spinning down /dev/sdf Mar 5 06:02:15 TowerVM02 emhttpd: spinning down /dev/sdd Mar 5 06:02:15 TowerVM02 emhttpd: spinning down /dev/sdn Mar 5 06:42:16 TowerVM02 emhttpd: spinning down /dev/sdm Mar 5 06:42:16 TowerVM02 emhttpd: spinning down /dev/sdg Mar 5 06:42:16 TowerVM02 emhttpd: spinning down /dev/sdt # Nothing between here Mar 5 06:59:20 TowerVM02 emhttpd: spinning down /dev/sde Mar 5 06:59:38 TowerVM02 emhttpd: spinning down /dev/sdi Mar 5 06:59:46 TowerVM02 emhttpd: spinning down /dev/sdw Mar 5 07:00:49 TowerVM02 emhttpd: spinning down /dev/sdp Mar 5 07:01:00 TowerVM02 emhttpd: spinning down /dev/sdk Mar 5 07:01:05 TowerVM02 emhttpd: spinning down /dev/sdj Mar 5 07:01:13 TowerVM02 emhttpd: spinning down /dev/sdu Mar 5 07:01:20 TowerVM02 emhttpd: spinning down /dev/sdv Mar 5 07:01:53 TowerVM02 emhttpd: spinning down /dev/sdb Mar 5 07:01:57 TowerVM02 emhttpd: spinning down /dev/sdh Mar 5 07:01:59 TowerVM02 emhttpd: spinning down /dev/sds Mar 5 07:02:03 TowerVM02 emhttpd: spinning down /dev/sdy Mar 5 07:02:03 TowerVM02 emhttpd: spinning down /dev/sdq Mar 5 07:02:05 TowerVM02 emhttpd: spinning down /dev/sdc Mar 5 07:02:10 TowerVM02 emhttpd: spinning down /dev/sdr Mar 5 07:02:12 TowerVM02 emhttpd: spinning down /dev/sdo Mar 5 07:02:14 TowerVM02 emhttpd: spinning down /dev/sdx Mar 5 07:02:14 TowerVM02 emhttpd: spinning down /dev/sdl Mar 5 07:02:15 TowerVM02 emhttpd: spinning down /dev/sdf Mar 5 07:02:16 TowerVM02 emhttpd: spinning down /dev/sdd Mar 5 07:02:16 TowerVM02 emhttpd: spinning down /dev/sdn Edited March 5, 20215 yr by hawihoney
March 5, 20215 yr Author 7 minutes ago, Hugomon said: Solved (so far) installing SAS Spindown app. Thanks. Will try.
March 5, 20215 yr Community Expert @hawihoney smartctl -s standby,now /dev/sdx will allow you to test, but this will only work on SATA drives.
March 5, 20215 yr Author 1 hour ago, Hugomon said: Solved (so far) installing SAS Spindown app. That did it. Thanks a lot.
March 6, 20215 yr Author 22 hours ago, SimonF said: smartctl -s standby,now /dev/sdx Sorry to ask. What's the opposite (spinup) command? GUI and system now mismatch. Some disks "think" they are spun up - but aren't and vice versa. Plex puts contents of some disks in the trashbin because the system "thinks" disks are spun up and Plex can't read them.
March 6, 20215 yr Community Expert # # sdspin <device> [up | down | status ] # # "device" is the HDD rdev name, such as "sdd". # # up == Spin the drive up # down == Spin the drive down # status == return the current status via rc This is used by the system, but may not update the status in the GUI until the next poll.
Archived
This topic is now archived and is closed to further replies.