Spindown of SAS HDD, Feature coming?


tillo

17 posts in this topic Last Reply

Recommended Posts

Hi, I have a SAS drive and it just wont spin down  :'( :'( :'( :'(

 

As far as I can tell this is just the way it is, it is stated under known issues in the release note for unraid 6.2

 

Is someone working on this, is it gonna be fixed? Whats happening?

 

 

Best regards Tillo

Link to post
  • 3 months later...
  • 4 months later...
On 1/21/2017 at 4:35 AM, 1812 said:

-bump for sas support!-

 

when my sas drives are xfs, they spin down, but no when btrfs.

 

 

also, temp display? Also funny: disks show as spun down but still usable....

 

Another bump for SAS and spindown support.  Have an LSI 9207-8i.  Am also seeing * for temp display and would love to have temp display.

Not a programmer, but willing to help in any way I can. 

Link to post
  • 4 weeks later...
  • 1 year later...
19 minutes ago, AnnabellaRenee87 said:

Another shameless bump. My new Parity drive is a 4TB SAS drive, it never spins down.

Sent from my SM-G955U using Tapatalk
 

 

Some would argue it saves strain on the spindle motor thingy...

 

 

but regardless...  I'm still down for this (right after a multiple cache pools!)

Link to post
  • 5 months later...

It doesn't look like SAS spin down is on development radar.

I bet $10 that Unraid just isn't able to spin down SAS drives ;-)

My log just fills up with this (I think it best to remove SAS drives from spin down):


Jan 20 13:21:10 Tower kernel: mdcmd (132099): spindown 10
Jan 20 13:21:10 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:10 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:11 Tower kernel: mdcmd (132100): spindown 2
Jan 20 13:21:11 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:11 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:11 Tower kernel: mdcmd (132101): spindown 10
Jan 20 13:21:11 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:11 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:12 Tower kernel: mdcmd (132102): spindown 2
Jan 20 13:21:12 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:12 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:12 Tower kernel: mdcmd (132103): spindown 10
Jan 20 13:21:12 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:12 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:13 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:13 Tower kernel: mdcmd (132104): spindown 2
Jan 20 13:21:13 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:13 Tower kernel: mdcmd (132105): spindown 10
Jan 20 13:21:13 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:13 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:14 Tower kernel: mdcmd (132106): spindown 2
Jan 20 13:21:14 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:14 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:14 Tower kernel: mdcmd (132107): spindown 10
Jan 20 13:21:14 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:14 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:15 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:15 Tower kernel: mdcmd (132108): spindown 2
Jan 20 13:21:15 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:15 Tower kernel: mdcmd (132109): spindown 10
Jan 20 13:21:15 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:15 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:16 Tower kernel: mdcmd (132110): spindown 2
Jan 20 13:21:16 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:16 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:16 Tower kernel: mdcmd (132111): spindown 10
Jan 20 13:21:16 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:16 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:17 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:17 Tower kernel: mdcmd (132112): spindown 2
Jan 20 13:21:17 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:17 Tower kernel: mdcmd (132113): spindown 10
Jan 20 13:21:17 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:17 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:18 Tower kernel: mdcmd (132114): spindown 2
Jan 20 13:21:18 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:18 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:18 Tower kernel: mdcmd (132115): spindown 10
Jan 20 13:21:18 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:18 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:19 Tower kernel: mdcmd (132116): spindown 2
Jan 20 13:21:19 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:19 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:19 Tower kernel: mdcmd (132117): spindown 10
Jan 20 13:21:19 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:19 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:20 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:20 Tower kernel: mdcmd (132118): spindown 2
Jan 20 13:21:20 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:20 Tower kernel: mdcmd (132119): spindown 10
Jan 20 13:21:20 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:20 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:21 Tower kernel: mdcmd (132120): spindown 2
Jan 20 13:21:21 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:21 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:21 Tower kernel: mdcmd (132121): spindown 10
Jan 20 13:21:21 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:21 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:22 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:22 Tower kernel: mdcmd (132122): spindown 2
Jan 20 13:21:22 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:22 Tower kernel: mdcmd (132123): spindown 10
Jan 20 13:21:22 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:22 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:23 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:23 Tower kernel: mdcmd (132124): spindown 2
Jan 20 13:21:23 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:23 Tower kernel: mdcmd (132125): spindown 10
Jan 20 13:21:23 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:23 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:24 Tower kernel: mdcmd (132126): spindown 2
Jan 20 13:21:24 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:24 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:24 Tower kernel: mdcmd (132127): spindown 10
Jan 20 13:21:24 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:24 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:25 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:25 Tower kernel: mdcmd (132128): spindown 2
Jan 20 13:21:25 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:25 Tower kernel: mdcmd (132129): spindown 10
Jan 20 13:21:25 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:25 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:26 Tower kernel: mdcmd (132130): spindown 2
Jan 20 13:21:26 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:26 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:26 Tower kernel: mdcmd (132131): spindown 10
Jan 20 13:21:26 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:26 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:27 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:27 Tower kernel: mdcmd (132132): spindown 2
Jan 20 13:21:27 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:27 Tower kernel: mdcmd (132133): spindown 10
Jan 20 13:21:27 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:27 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:28 Tower kernel: mdcmd (132134): spindown 2
Jan 20 13:21:28 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:28 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:28 Tower kernel: mdcmd (132135): spindown 10
Jan 20 13:21:28 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:28 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:29 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:29 Tower kernel: mdcmd (132136): spindown 2
Jan 20 13:21:29 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:29 Tower kernel: mdcmd (132137): spindown 10
Jan 20 13:21:29 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:29 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:30 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:30 Tower kernel: mdcmd (132138): spindown 2
Jan 20 13:21:30 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:30 Tower kernel: mdcmd (132139): spindown 10
Jan 20 13:21:30 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:30 Tower kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Jan 20 13:21:31 Tower kernel: mdcmd (132140): spindown 2
Jan 20 13:21:31 Tower emhttpd: error: mdcmd, 2639: Input/output error (5): write
Jan 20 13:21:31 Tower kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Jan 20 13:21:31 Tower kernel: mdcmd (132141): spindown 10

Link to post
On 1/24/2019 at 10:00 AM, hasselltech said:

I found this link that may be able to assist with this problem but I don't currently have a dev unraid system to test this on. If anyone is willing, I'd appreciate finding out if this works on unraid
https://zackreed.me/spindown-sas-disks/

So I gave this a try on my UnRAID system and it did not seem to have an effect.  It does not appear to put the drives to sleep or UnRAID isn't seeing them as asleep.  

 

I was able to manually put them to sleep using sdparm --command=stop.  I ended up stopping my testing there.   I didn't wait to see if UnRAID would wake the disk on activity.

 

 

 

Link to post
1 hour ago, noties said:

So I gave this a try on my UnRAID system and it did not seem to have an effect.  It does not appear to put the drives to sleep or UnRAID isn't seeing them as asleep.  

 

I was able to manually put them to sleep using sdparm --command=stop.  I ended up stopping my testing there.   I didn't wait to see if UnRAID would wake the disk on activity.

 

 

 

Thanks.  I was able to set up a test host and the problem that I was experiencing was that the disk would spin immediately back up and I was not able to determine why at the time. I plan to do more testing when I have the chance. For those interested, sdparm is available from the Nerdpack plugin. 

Link to post
  • 8 months later...

A data point: My SAS drives (HGST HC520, relatively new crop) appear to spin up and down properly for Unraid, in the sense that the GUI shows them as spun down and turns their temp display into "*", and there are no i/o sense errors in syslog. 

However, spin down seems to not actually happen, judging by the fact that clicking "spin up" on the GUI "spins them up" instantly, and their temp remains around 30C while my spun down SATA drives wake up at around 24C.

 

Connection is via an on-board LSI 2308 chip.

Link to post
  • 1 month later...
1 hour ago, Spies said:

What exactly is causing spindown to be broken for SAS drives? Is it a Kernel issue? How does unRaid communication with SAS drives differ to that of SATA?

Unraid uses hdparm to spin down drives, and hdparm doesn't work with SAS devices, they need sdparm, LT is working on adding support, but it's not a simple thing, especially with limited hardware available for testing.

Link to post
2 hours ago, johnnie.black said:

Unraid uses hdparm to spin down drives, and hdparm doesn't work with SAS devices, they need sdparm, LT is working on adding support, but it's not a simple thing, especially with limited hardware available for testing.

OK, that's a shame.

Link to post
  • 5 months later...

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.