[[Plugin] Spin Down SAS Drives]

4 hours ago, SimonF said:

Have you tried the file activity plugin to see if any files being accessed.

 

I looked into the File Activity plugin as suggested. I was having issues with it, and with investigating how to get it to work I had installed the Fix Common Problems / Tips and Tweaks Plugin. I then adjusted the Tips and Tweaks plugin setting for Max Watches 'fs.inotify.max_user_watches': to 6524288 and changed the settings of the File Activity Plugin to the following:

 

 

After making all the above changes to get the Plugin for FIle Activity to work correctly, then my SAS Spindown started working correctly. lol. So now I have no idea what was causing it. But if I had to make a guess it's the inotify changes I made in Tips and Tweaks. I'll leave it as it is now that it's working. Odd little workaround, that the changes required for one to work properly causes this plugin to work properly.

 

System Logs as of now:

-----------------------------------------

Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdm
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdj
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdk
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdh
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdg
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdd
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sde
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdb
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdr
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdf
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdc
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sds
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdq
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdl
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdi
Nov 27 20:04:09 Tower  emhttpd: spinning down /dev/sdp
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdm
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdk
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdj
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdg
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdh
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sde
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdc
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdd
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdb
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdf
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdi
Nov 27 20:04:09 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdl

 

[Unraid OS version 6.11.5 available]

On 11/25/2022 at 11:03 AM, JorgeB said:

That should be reported in the existing plugin support thread:

https://forums.unraid.net/topic/97351-plugin-spin-down-sas-drives/

 

Thank you! I've done so. I appreciate the direction.

[[Plugin] Spin Down SAS Drives]

Greetings all,

 

I have an issue with a few disks also not spinning down. I've noticed this was happening ever since my upgrade to 6.11. I'm currently running 6.11.5. I've uninstalled every app / plugin that reads anything from disk or reports smart information (temp, fan control etc) and disabled docker completely. I've changed spindown to 15 minutes and I see the calls to SAS Assist, but seconds later a Read call for SMART is kicked in and it spins the disk back up. The drives with issues can be seen with green mark below:

 

 

My System Log looks like the following:

---------------------------------------------------------------------

Nov 27 13:15:40 Tower  emhttpd: spinning down /dev/sdt
Nov 27 13:15:40 Tower  emhttpd: spinning down /dev/sdn
Nov 27 13:15:40 Tower  emhttpd: spinning down /dev/sdo
Nov 27 13:15:41 Tower  emhttpd: spinning down /dev/sdu
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdm
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdj
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdk
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdh
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdg
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdd
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sde
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdb
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdr
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdf
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdc
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sds
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdi
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdm
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdg
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdj
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdd
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdh
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdb
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sde
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdk
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdf
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdi
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdc
Nov 27 13:16:25 Tower  emhttpd: read SMART /dev/sdh
Nov 27 13:16:25 Tower  emhttpd: read SMART /dev/sde
Nov 27 13:16:25 Tower  emhttpd: read SMART /dev/sdf
Nov 27 13:16:25 Tower  emhttpd: read SMART /dev/sdi
Nov 27 13:16:38 Tower  emhttpd: spinning down /dev/sdq
Nov 27 13:16:38 Tower  emhttpd: spinning down /dev/sdl
Nov 27 13:16:38 Tower  emhttpd: spinning down /dev/sdp
Nov 27 13:16:38 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdl
Nov 27 13:31:26 Tower  emhttpd: spinning down /dev/sdh
Nov 27 13:31:26 Tower  emhttpd: spinning down /dev/sde
Nov 27 13:31:26 Tower  emhttpd: spinning down /dev/sdf
Nov 27 13:31:26 Tower  emhttpd: spinning down /dev/sdi
Nov 27 13:31:26 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdh
Nov 27 13:31:26 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdf
Nov 27 13:31:26 Tower SAS Assist v2022.08.02: Spinning down device /dev/sde
Nov 27 13:31:26 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdi
Nov 27 13:31:45 Tower  emhttpd: read SMART /dev/sdh
Nov 27 13:31:45 Tower  emhttpd: read SMART /dev/sde
Nov 27 13:31:45 Tower  emhttpd: read SMART /dev/sdf
Nov 27 13:31:45 Tower  emhttpd: read SMART /dev/sdi
---------------------------------------------------------------------

 

Disk SDE Log:

-----------------------

Nov 27 12:59:55 Tower kernel: sd 1:1:19:0: [sde] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
Nov 27 12:59:55 Tower kernel: sd 1:1:19:0: [sde] 4096-byte physical blocks
Nov 27 12:59:55 Tower kernel: sd 1:1:19:0: [sde] Write Protect is off
Nov 27 12:59:55 Tower kernel: sd 1:1:19:0: [sde] Mode Sense: db 00 10 08
Nov 27 12:59:55 Tower kernel: sd 1:1:19:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA
Nov 27 12:59:55 Tower kernel: sd 1:1:19:0: [sde] Preferred minimum I/O size 4096 bytes
Nov 27 12:59:55 Tower kernel: sde: sde1
Nov 27 12:59:55 Tower kernel: sd 1:1:19:0: [sde] Attached SCSI removable disk
Nov 27 13:00:19 Tower  emhttpd: ST6000NM0034_Z4D2WVPZ0000R601KR6P_35000c500841f8d57 (sde) 512 11721045168
Nov 27 13:00:19 Tower kernel: mdcmd (5): import 4 sde 64 5860522532 0 ST6000NM0034_Z4D2WVPZ0000R601KR6P_35000c500841f8d57
Nov 27 13:00:19 Tower kernel: md: import disk4: (sde) ST6000NM0034_Z4D2WVPZ0000R601KR6P_35000c500841f8d57 size: 5860522532 
Nov 27 13:00:19 Tower  emhttpd: read SMART /dev/sde
Nov 27 13:00:25 Tower  emhttpd: shcmd (41): echo 128 > /sys/block/sde/queue/nr_requests
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sde
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sde
Nov 27 13:16:25 Tower  emhttpd: read SMART /dev/sde
Nov 27 13:31:26 Tower  emhttpd: spinning down /dev/sde
Nov 27 13:31:26 Tower SAS Assist v2022.08.02: Spinning down device /dev/sde
Nov 27 13:31:45 Tower  emhttpd: read SMART /dev/sde

 

Disk SDH Log:

------------------------

Nov 27 12:59:55 Tower kernel: sd 1:1:22:0: [sdh] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
Nov 27 12:59:55 Tower kernel: sd 1:1:22:0: [sdh] 4096-byte physical blocks
Nov 27 12:59:55 Tower kernel: sd 1:1:22:0: [sdh] Write Protect is off
Nov 27 12:59:55 Tower kernel: sd 1:1:22:0: [sdh] Mode Sense: d7 00 10 08
Nov 27 12:59:55 Tower kernel: sd 1:1:22:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA
Nov 27 12:59:55 Tower kernel: sd 1:1:22:0: [sdh] Disabling DIF Type 2 protection
Nov 27 12:59:55 Tower kernel: sd 1:1:22:0: [sdh] Enabling DIF Type 0 protection
Nov 27 12:59:55 Tower kernel: sd 1:1:22:0: [sdh] Preferred minimum I/O size 4096 bytes
Nov 27 12:59:55 Tower kernel: sdh: sdh1
Nov 27 12:59:55 Tower kernel: sd 1:1:22:0: [sdh] Attached SCSI removable disk
Nov 27 13:00:19 Tower  emhttpd: ST6000NM0034_Z4D1JRGF0000R533HWD2_35000c5008345baf3 (sdh) 512 11721045168
Nov 27 13:00:19 Tower kernel: mdcmd (6): import 5 sdh 64 5860522532 0 ST6000NM0034_Z4D1JRGF0000R533HWD2_35000c5008345baf3
Nov 27 13:00:19 Tower kernel: md: import disk5: (sdh) ST6000NM0034_Z4D1JRGF0000R533HWD2_35000c5008345baf3 size: 5860522532 
Nov 27 13:00:19 Tower  emhttpd: read SMART /dev/sdh
Nov 27 13:00:25 Tower  emhttpd: shcmd (42): echo 128 > /sys/block/sdh/queue/nr_requests
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdh
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdh
Nov 27 13:16:25 Tower  emhttpd: read SMART /dev/sdh
Nov 27 13:31:26 Tower  emhttpd: spinning down /dev/sdh
Nov 27 13:31:26 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdh
Nov 27 13:31:45 Tower  emhttpd: read SMART /dev/sdh

 

Disk SDF Log:

------------------------

Nov 27 12:59:55 Tower kernel: sd 1:1:20:0: [sdf] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
Nov 27 12:59:55 Tower kernel: sd 1:1:20:0: [sdf] 4096-byte physical blocks
Nov 27 12:59:55 Tower kernel: sd 1:1:20:0: [sdf] Write Protect is off
Nov 27 12:59:55 Tower kernel: sd 1:1:20:0: [sdf] Mode Sense: db 00 10 08
Nov 27 12:59:55 Tower kernel: sd 1:1:20:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
Nov 27 12:59:55 Tower kernel: sd 1:1:20:0: [sdf] Preferred minimum I/O size 4096 bytes
Nov 27 12:59:55 Tower kernel: sdf: sdf1
Nov 27 12:59:55 Tower kernel: sd 1:1:20:0: [sdf] Attached SCSI removable disk
Nov 27 13:00:19 Tower  emhttpd: ST6000NM0034_S4D1C5GJ0000E715D6DK_35000c50099185123 (sdf) 512 11721045168
Nov 27 13:00:19 Tower kernel: mdcmd (9): import 8 sdf 64 5860522532 0 ST6000NM0034_S4D1C5GJ0000E715D6DK_35000c50099185123
Nov 27 13:00:19 Tower kernel: md: import disk8: (sdf) ST6000NM0034_S4D1C5GJ0000E715D6DK_35000c50099185123 size: 5860522532 
Nov 27 13:00:19 Tower  emhttpd: read SMART /dev/sdf
Nov 27 13:00:25 Tower  emhttpd: shcmd (45): echo 128 > /sys/block/sdf/queue/nr_requests
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdf
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdf
Nov 27 13:16:25 Tower  emhttpd: read SMART /dev/sdf
Nov 27 13:31:26 Tower  emhttpd: spinning down /dev/sdf
Nov 27 13:31:26 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdf
Nov 27 13:31:45 Tower  emhttpd: read SMART /dev/sdf

 

Disk SDI Log:

-----------------------

Nov 27 12:59:55 Tower kernel: sd 1:1:23:0: [sdi] 11721045168 512-byte logical blocks: (6.00 TB/5.46 TiB)
Nov 27 12:59:55 Tower kernel: sd 1:1:23:0: [sdi] 4096-byte physical blocks
Nov 27 12:59:55 Tower kernel: sd 1:1:23:0: [sdi] Write Protect is off
Nov 27 12:59:55 Tower kernel: sd 1:1:23:0: [sdi] Mode Sense: d7 00 10 08
Nov 27 12:59:55 Tower kernel: sd 1:1:23:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA
Nov 27 12:59:55 Tower kernel: sd 1:1:23:0: [sdi] Preferred minimum I/O size 4096 bytes
Nov 27 12:59:55 Tower kernel: sdi: sdi1
Nov 27 12:59:55 Tower kernel: sd 1:1:23:0: [sdi] Attached SCSI removable disk
Nov 27 13:00:19 Tower  emhttpd: ST6000NM0034_S4D0BBE9_35000c5008efc9f2b (sdi) 512 11721045168
Nov 27 13:00:19 Tower kernel: mdcmd (10): import 9 sdi 64 5860522532 0 ST6000NM0034_S4D0BBE9_35000c5008efc9f2b
Nov 27 13:00:19 Tower kernel: md: import disk9: (sdi) ST6000NM0034_S4D0BBE9_35000c5008efc9f2b size: 5860522532 
Nov 27 13:00:19 Tower  emhttpd: read SMART /dev/sdi
Nov 27 13:00:25 Tower  emhttpd: shcmd (46): echo 128 > /sys/block/sdi/queue/nr_requests
Nov 27 13:16:07 Tower  emhttpd: spinning down /dev/sdi
Nov 27 13:16:07 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdi
Nov 27 13:16:25 Tower  emhttpd: read SMART /dev/sdi
Nov 27 13:31:26 Tower  emhttpd: spinning down /dev/sdi
Nov 27 13:31:26 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdi
Nov 27 13:31:45 Tower  emhttpd: read SMART /dev/sdi

tower-diagnostics-20221127-1339.zip

[Unraid OS version 6.11.5 available]

Before version 6.11 the Plugin to Spin Down SAS Drives worked just fine. Now my array is online 24/7 and temps are the highest they've ever been. Manually spinning down my array also doesn't seem to spin down all my disks even with all docker containers turned off. I've never experienced this behavior in several years of running the same setup I'm running now.

[Downgraded back to 6.6.7 due to Sqlite corruption]

I've tried the work around / fix. It did not fix the issue. So it's something bigger. I've rebuilt my entire server almost every day for 2 weeks straight with all possible solutions I could think of. Rolling back to 6.6.7 fixes all of the issues.

The only "fixes" that worked while on 6.7 was for Sonarr/Radarr/Lidarr was to go to appdata and delete log.db and restart the dockers and let them cycle through housekeeping a few times. Plex I had to delete the com.plexapp.plugins.library.db from the plex databases appdata and then readd my libraries and let it rescan and add all the metadata over again. Until you download or add something to the library, in which case it'll die again. For sab or nzbget I'd just delete the appdata folder all together and redo the entire thing. Forcing an update would sometimes fix it but rebuilding it would work for sure for at least another day.

[Downgraded back to 6.6.7 due to Sqlite corruption]

After being fed up with rebuilding my entire build almost daily, I decided to see wtf is going on with 6.7.0 Found this page. I'm going to do what was suggested above as I do not run a Cache Disk (Took it out thinking it had something to do with the corruption.) I'm going to change all my appdata to /mnt/disk1/appdata/ and see if that fixes the issue.

--------------------

24 Hour Update: Running as expected so far. No issues as of yet. Just queued up 1TB between Radarr and Sonarr. We'll see what happens after it's all finished and housekeeping kicks in.

---------------------

29 Hour Update: RIP - Task Error: database disk image is malformed.

---------------------

I stopped the Dockers having corruption issues (Radarr / Sonarr) and then deleted the logs.db file in appdata and then restarted the dockers. Seems to be working again after letting it go through its housekeeping, it picks back up where it left off before the corruption. Not sure what's causing it though?