[Plugin] Spin Down SAS Drives


doron

Recommended Posts

46 minutes ago, Mors said:

Though I find it very strange that I can't browse to the folder in Krusader

Unlikey the path to the OS root is mapped in Krusader, normally it will map to /mnt/user on the host.

 

MC is a text filemanager you can run in terminal.

 

as doron said hopefully the fixed will be released offically soon.

Link to comment
On 9/10/2022 at 2:09 AM, SimonF said:

You can add as a Userscript or I add in my go changes I am testing. I have a temp dir on the boot drive I add files into

 

cp /boot/temp/file /usr/local/emhttp/plugin/pluginname/....

chmod +x /usr/local/emhttp/plugin/pluginname/.... if it need to be executable. 

 

root@computenode:~# cat /boot/config/go
#!/bin/bash
# Start the Management Utility
#sed -i 's/disableLeaveAlert=true/disableLeaveAlert=true -t fontsize=20/' /etc/rc.d/rc.nginx

#cp /boot/temp/ArrayOperation.page /usr/local/emhttp/plugins/dynamix/
#cp /boot/temp/parity_list /usr/local/emhttp/plugins/dynamix/nchan/
#cp /boot/temp/mover /usr/local/sbin
#chmod +x /usr/local/emhttp/plugins/dynamix/nchan/parity_list
#chmod +x /usr/local/sbin/mover
#cp /boot/temp/smartctl_type /usr/local/sbin
#chmod +x /usr/local/sbin/smartctl_type
#cp /boot/temp/sdspin /usr/local/sbin
#chmod +x /usr/local/sbin/sdspin
#cp /boot/temp/smartctl_test /usr/local/sbin
#chmod +x /usr/local/sbin/smartctl_test
cp /boot/temp/cli64 /usr/local/sbin
chmod +x /usr/local/sbin/cli64
cp /boot/temp/mover.php /tmp
chmod +x /tmp/mover.php

/usr/local/sbin/emhttp &
root@computenode:~# 
 

 

Thanks!  I'll try to add as a user script to start on array start up . . I'll let you know how it goes.  

Link to comment
On 9/9/2022 at 10:17 PM, cbr600ds2 said:

Ahhh -   if I disable autofan then bios will control the fan right?  

 

I was reading your script "hack" and I was wondering if I got this right - then I would have to do this everytime I started the array?  Can it be added to the userscripts plugin? 

 

Im' getting this  - 

 

Script location: /tmp/user.scripts/tmpScripts/Fan script/script
Note that closing this window will abort the execution of this script
/tmp/user.scripts/tmpScripts/Fan script/script: line 2: root@Skynet:~#: command not found
cp: cannot stat '/boot/temp/cli64': No such file or directory
chmod: cannot access '/usr/local/sbin/cli64': No such file or directory
cp: cannot stat '/boot/temp/mover.php': No such file or directory
chmod: cannot access '/tmp/mover.php': No such file or directory
/tmp/user.scripts/tmpScripts/Fan script/script: line 24: root@Skynet:~#: command not found
emhttpd is already started

 

seems like I need to locate the cli and mover.php files but shouldn't those be in a standard location?  

 

 

Link to comment
7 hours ago, cbr600ds2 said:

 

Im' getting this  - 

 

Script location: /tmp/user.scripts/tmpScripts/Fan script/script
Note that closing this window will abort the execution of this script
/tmp/user.scripts/tmpScripts/Fan script/script: line 2: root@Skynet:~#: command not found
cp: cannot stat '/boot/temp/cli64': No such file or directory
chmod: cannot access '/usr/local/sbin/cli64': No such file or directory
cp: cannot stat '/boot/temp/mover.php': No such file or directory
chmod: cannot access '/tmp/mover.php': No such file or directory
/tmp/user.scripts/tmpScripts/Fan script/script: line 24: root@Skynet:~#: command not found
emhttpd is already started

 

seems like I need to locate the cli and mover.php files but shouldn't those be in a standard location?  

 

 

That is an example of my go file, you dont that.

 

Your script will only need to cp from the boot drive the modded file doron posted.

 

copy the file from this post and put in a folder on the boot drive.

 

 

I use /boot/temp

 

your script only needs

 

cp /boot/temp/autofan /usr/local/emhttp/plugins/dynamix.system.autofan/scripts

chmod +x /usr/local/emhttp/plugins/dynamix.system.autofan/scripts/autofan

 

 

Edited by SimonF
Link to comment
On 9/11/2022 at 7:04 PM, Mors said:

So everything is working now, I assume somewhere along the way (beyond the typo in SimonF's post, which I didn't catch either) I assume I must have had a typo myself. Though I find it very strange that I can't browse to the folder in Krusader, I am sure I have a setting not checked somewhere.

 

The big thing was finally seeing something about the MC command, which might be second nature to all your Linux guru's but until I remembered that is how you easily navigate and do things like put this script in the folder I felt like I was taking crazy pills a bit. One of those things where there is just so much info, and so many spaceinvader videos, that finding what you're looking for, and I spent a semi long googling and searching around these forums, can end up being quite daunting since you get a lot of relevant but not specific info.

 

Anyways, thanks to both @SimonF and @doron . If I can trouble you for one more question, now that I see what I did, why would you need a script or anything further to make this work everytime on boot? Since we replaced the already used script with your new code, wont this just automatically run on boot since Autofan uses this script?

@cbr600ds2

 

The plugin has been updated with @doronfix so you should no longer need to update the file manually.

  • Like 1
Link to comment
  • 1 month later...
3 hours ago, francishe said:

Thanks for the plg. But no luck on my 6.11.1 server. I've got 4 Seagate SAS ST6000NM0034, none of which willingly spins down at the spindown delay according to the system log.

Please provide some more context as to what does in fact happen.

Seagate SAS drives are known to not always play nice with the spin down/up instructions, but to be able to respond specifically, some info is required.

Link to comment
10 minutes ago, doron said:

Please provide some more context as to what does in fact happen.

Seagate SAS drives are known to not always play nice with the spin down/up instructions, but to be able to respond specifically, some info is required.

Thanks for the reply.

After I installed it nothing happened nor sas spindown operation could be found in the system log though I set spindown delay to 15m which worked well on other sata drives. 

Link to comment
34 minutes ago, francishe said:

Thanks for the reply.

After I installed it nothing happened nor sas spindown operation could be found in the system log though I set spindown delay to 15m which worked well on other sata drives. 

Please provide diagnostics, and/or reply --

- Do you see any syslog messages from the plugin ("SAS Assist")?

- When you click the green button to the left of a SAS drive, what do you see in syslog?

Link to comment
8 hours ago, francishe said:

Thanks for the reply.

After I installed it nothing happened nor sas spindown operation could be found in the system log though I set spindown delay to 15m which worked well on other sata drives. 

 

I am working on putting several Hitachi/HGST 3 TB SAS drives (models HUS723030ALS640 and HUS724030ALS640) into service on one of my UnRAID servers and am running into the same issue. All of the SAS drives are currently in a pair of external enclosures attached to the server via a single LSI 9201-16e with no SAS expanders.

 

Spin Down SAS Drives was installed via Community Apps on UnRAID 6.11.1.

 

Clicking on the spin-down ball results in spinning green arrows, returning to a green ball. Nothing appears to be logged in syslog.

 

Diagnostics attached.

eris-diagnostics-20221104-1138.zip

Link to comment
1 hour ago, SimonF said:

I don't see any SAS spin down messages in the logs. Disk 20 was creating errors. 

 

What are you using to run the web gui from as there are loads for nchan out of memory errors.

 

 

Disk 20 was suspect and is mid-preclear. I'm pretty sure it's going to get disposed of.

 

Default web GUI inside a Vivaldi tab. Behavior is the same (spins, goes back to green ball) from Edge and Chrome with all other web browsers closed when trying.

Most recent nchan error looked to me to be about 6 hours before I pulled diagnostics (and a few hours before I started looking into SAS spindown), and I'd rebooted my desktop between then and trying to get Spin Down SAS Drives installed/working.

 

edit: typo

Edited by jsbraby
Link to comment
26 minutes ago, jsbraby said:

Disk 20 was suspect and is mid-preclear. I'm pretty sure it's going to get disposed of.

 

Default web GUI inside a Vivaldi tab. Behavior is the same (spins, goes back to green ball) from Edge and Chrome with all other web browsers closed when trying.

Most recent nchan error looked to me to be about 6 hours before I pulled diagnostics (and a few hours before I started looking into SAS spindown), and I'd rebooted my desktop between then and trying to get Spin Down SAS Drives installed/working.

 

edit: typo

You should see messages like this in the syslog

 

Nov  4 19:04:44 Tower  emhttpd: spinning down /dev/sde
Nov  4 19:04:44 Tower SAS Assist v2022.08.02: Spinning down device /dev/sde
Nov  4 19:04:45 Tower  emhttpd: spinning down /dev/sdd
Nov  4 19:04:45 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdd
Nov  4 19:04:45 Tower  emhttpd: spinning down /dev/sdg
Nov  4 19:04:45 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdg
Nov  4 19:04:45 Tower  emhttpd: spinning down /dev/sdf
Nov  4 19:04:45 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdf
Nov  4 19:04:45 Tower  emhttpd: spinning down /dev/sdi
Nov  4 19:04:45 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdi
Nov  4 19:04:45 Tower  emhttpd: spinning down /dev/sdj
Nov  4 19:04:45 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdj

 

image.png.f78c970eb9b671d7fed6ef0f3fd909dd.png

Link to comment
On 11/4/2022 at 4:34 PM, doron said:

Please provide diagnostics, and/or reply --

- Do you see any syslog messages from the plugin ("SAS Assist")?

- When you click the green button to the left of a SAS drive, what do you see in syslog?

I suddenly realised it might need a reboot to murge it as a part of the system. I did and it's working well bringing down the power consumption by 40w.

Again thanks

  • Thanks 1
Link to comment
15 hours ago, francishe said:

I suddenly realised it might need a reboot to murge it as a part of the system. I did and it's working well bringing down the power consumption by 40w.

Again thanks

Same here. Works as expected/hoped post reboot.

 

Very grateful for SAS spindown support.

  • Like 1
Link to comment
  • 3 weeks later...

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:

 

image.png.01fc0853f4dcbb3494d6ee3555ea45d5.png

 

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

Link to comment
2 hours ago, DiRiN said:

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:

 

image.png.01fc0853f4dcbb3494d6ee3555ea45d5.png

 

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 129.58 kB · 0 downloads

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

Link to comment
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:

 

image.png.1ac0cc881c48f06539f2d23fe8cd96d2.png

 

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

 

image.png.e34825c0c844d379003f7c07203343b4.png

Link to comment
3 minutes ago, DiRiN said:

 

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:

 

image.png.1ac0cc881c48f06539f2d23fe8cd96d2.png

 

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

 

image.png.e34825c0c844d379003f7c07203343b4.png

That is strange, but thanks for the update.

 

Link to comment

I installed the plugin 2 days ago (Unraid 6.11.5) and it wasn't working at all, then I just rebooted the server and magically it started working without any issue.

Thank you so much for your work, really appreciate it! :)🙌

Btw, I'm using a mix of SAS and SATA drive, SAS drives spin down perfectly like SATA ones, both for inactivity (set at 15 mins) and when asked manually too, no issue at all!

 

SAS drives are recognized as NETAPP X477_SMEGX04TA07 in Unraid, but in reality they are Seagate Constellation ES.3 ST4000NM0023 (most probably they've been rebranded by Netapp).

 

image.thumb.png.0c4fcee1100b512fbfa20eccb1b5cd81.png

image.thumb.png.748f549ac975370e989ad23910136187.png

Link to comment
  • 4 weeks later...

HI!

 

I have installed this plugin in Unraid latest version and my SAS disks don't spin down. My hardware is HP Proliant DL380 G7 and the SAS controller P410i. Proccesor is Xeon L5640 with 72 Gigs RAM.

Logs:

 

Dec 23 21:22:19 Proliant  emhttpd: spinning down /dev/sdc
Dec 23 21:22:19 Proliant SAS Assist v2022.08.02: Spinning down device /dev/sdc
Dec 23 21:22:19 Proliant  emhttpd: sdspin /dev/sdc down: 1

 

If I use the green circle at the left of the disks it gos with two arrows rounding ant 2 seconds after it puts green circle again.

 

No docker used, no shared, no VM's...

 

Do you know if is there any problem with this controller?

Link to comment
7 minutes ago, inogueira said:

HI!

 

I have installed this plugin in Unraid latest version and my SAS disks don't spin down. My hardware is HP Proliant DL380 G7 and the SAS controller P410i. Proccesor is Xeon L5640 with 72 Gigs RAM.

Logs:

 

Dec 23 21:22:19 Proliant  emhttpd: spinning down /dev/sdc
Dec 23 21:22:19 Proliant SAS Assist v2022.08.02: Spinning down device /dev/sdc
Dec 23 21:22:19 Proliant  emhttpd: sdspin /dev/sdc down: 1

 

If I use the green circle at the left of the disks it gos with two arrows rounding ant 2 seconds after it puts green circle again.

 

No docker used, no shared, no VM's...

 

Do you know if is there any problem with this controller?

I think it is a RAID card so may not be passing commands through to the drives. 

 

what output do you get for 

sg_start  --readonly --pc=3 /dev/sdc and

sdparm -C sense /dev/sdc 

 

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.