[Plugin] Spin Down SAS Drives


doron

248 posts in this topic Last Reply

Recommended Posts

I didn't mean to imply the syslog errors in my previous post were read errors.

 

image.thumb.png.6a524a65034643f6fd64c7005a931aea.png

This is after a parity check on a previously good drive.

Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826600
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826608
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826616
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826624
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826632
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826640
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826648
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826656
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826664
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826672
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826680
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826688
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826696
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826704
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826712
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826720
Oct 12 09:42:17 Beast kernel: md: disk7 read error, sector=5848826728
Oct 12 09:43:55 Beast kernel: md: sync done. time=45545sec

 

5 hours ago, doron said:

Thanks. How did you determine that the drive is not spun down?

The unraid icon remained green and data was still immediately accessible.

The particular drive I tested with was not showing any traffic throughout my testing.

 

I did try using this command, but there was no output;

sg_start  --readonly --pc=3 /dev/sde

Link to post
  • Replies 247
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Unraid does a nice job of controlling HDD's energy consumption (and probably longevity) by spinning down (mechanical) hard drives when idle for a set period of time. Unfortunately the technique u

It is

Thank you so much for writing this - I'm really glad you're finding it helpful.   Your post is my reward, really. If you want, you can pay it forward - put those dollars in a charity of your

Posted Images

1 hour ago, jenga201 said:

I did try using this command, but there was no output;

sg_start  --readonly --pc=3 /dev/sde

This is just spin the drive down, you need to run sdparm --command=sense /dev/sdX to see the status of the drive

 

root@Tower:/usr/local/sbin# sg_start -r --pc=3 /dev/sdk
root@Tower:/usr/local/sbin# sdparm   --command=sense /dev/sdk
    /dev/sdk: HITACHI   HMRSK2000GBAS07K  3P02
Additional sense: Standby condition activated by command

 

Link to post

Ok, it seems to work using the sg_start and sdparm commands only.

The UI just doesn't reflect the state of the drive properly.

 

I think the read errors are due to spinning down the drive while it was being accessed.

They aren't going away, so I'll probably just try replacing/formatting that drive again.

Link to post
5 minutes ago, jenga201 said:

Ok, it seems to work using the sg_start and sdparm commands only.

The UI just doesn't reflect the state of the drive properly.

Indeed, the UI doesn't sense it when you spin the drive down from the command line.

However if you use the plugin in normal course of things, when Unraid is the one to schedule the spin down, it should work fine and be reflected in the UI in green/grey (it does here, I'm using the plugin for a couple weeks now).

5 minutes ago, jenga201 said:

I think the read errors are due to spinning down the drive while it was being accessed.

(Sorry for misreading your previous message - I thought you were referring to the log messages you quoted.)

If you did it manually via the console (using sg_start and sdparm) - while the array was started - then this might be it.

If you did it in sync with Unraid (i.e. either via its own scheduled spindown or by pushing the green button) - I'd think not.

5 minutes ago, jenga201 said:

They aren't going away, so I'll probably just try replacing/formatting that drive again.

You can rebuild that drive, which should restore its contents.

Link to post

Hi,

This is a great initiative! But I'm having some trouble to get my HP SAS drive spun down.

 

The drive looks spun down i unraid, but not when i check in CLI.

root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7

Then if i manually spin down the drive.

root@Tower:~# sg_start  --readonly --pc=3 /dev/sdh
root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
Additional sense: Standby condition activated by command

Looks like it's working, but if i spin up the drive and wait 15min, it's the same over again, looks spun down in unraid, but really isn't

 

It's a HP SAS drive connected to LSI SAS controller. And i have noticed that the drive has different names (power conditions) than other drives (STANDBY_Z)

root@Tower:~# sdparm --flexible -6 -p po -l /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
    Direct access device specific parameters: WP=0  DPOFUA=1
Power condition [po] mode page:
  PM_BG         2  [cha: y, def:  2, sav:  2]  Power management, background functions, precedence
  STANDBY_Y     0  [cha: y, def:  0, sav:  0]  Standby_y timer enable
  IDLE_C        0  [cha: y, def:  0, sav:  0]  Idle_c timer enable
  IDLE_B        0  [cha: y, def:  0, sav:  0]  Idle_b timer enable
  IDLE_A        1  [cha: y, def:  1, sav:  1]  Idle_a timer enable
  STANDBY_Z     0  [cha: y, def:  0, sav:  0]  Standby_z timer enable
  IACT          20  [cha: y, def: 20, sav: 20]  Idle_a condition timer (100 ms)
  SZCT          -1  [cha: y, def: -1, sav: -1]  Standby_z condition timer (100 ms)
  IBCT          -1  [cha: y, def: -1, sav: -1]  Idle_b condition timer (100 ms)
  ICCT          -1  [cha: y, def: -1, sav: -1]  Idle_c condition timer (100 ms)
  SYCT          -1  [cha: y, def: -1, sav: -1]  Standby_y condition timer (100 ms)
  CCF_IDLE      2  [cha: y, def:  2, sav:  2]  check condition if from idle_c
  CCF_STAND     2  [cha: y, def:  2, sav:  2]  check condition if from a standby
  CCF_STOPP     2  [cha: y, def:  2, sav:  2]  check condition if from stopped

 

Log from unraid spin down.

Oct 19 11:14:49 Tower kernel: mdcmd (65): spindown 3
Oct 19 11:14:49 Tower emhttpd: error: mdcmd, 2783: Input/output error (5): write
Oct 19 11:14:49 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5
Oct 19 11:14:50 Tower kernel: mdcmd (66): spindown 3
Oct 19 11:15:07 Tower SAS Assist v0.6[20803]: spinning down slot 3, device /dev/sdh (/dev/sg7)
Oct 19 11:15:07 Tower SAS Assist v0.6[20827]: spinning down slot 3, device /dev/sdh (/dev/sg7)

 

Any ideas that could help me?

Thanks!

 

Link to post
12 minutes ago, jowe said:

Any ideas that could help me?

A few questions:

 

- What happens if you manually spin down /dev/sg7 ?

- When you check sense right after you see the message "spinning down slot 3, device /dev/sdh (/dev/sg7)" - do you see the device spun down? (additional sense etc.)

- Do you always get two messages of "spinning down" instead of one?

Edited by doron
Link to post
8 minutes ago, doron said:

A few questions:

 

- What happens if you manually spin down /dev/sg7 ?

- When you check sense right after you see the message "spinning down slot 3, device /dev/sdh (/dev/sg7)" - do you see the device spun down? (additional sense etc.)

- Do you always get two messages of "spinning down" instead of one?

Hi, 

Manually spinning down sg7 works.

root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
root@Tower:~# sg_start  --readonly --pc=3 /dev/sg7
root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
Additional sense: Standby condition activated by command

When i check the disk right after unraid shows it as spun down with "sdparm --command=sense /dev/sdh" It not in standby even though unraid GUI says it is. Looks just like this.

root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7


Yes i get that line 2 times. Will check a 3rd time just to be sure.

Link to post
23 minutes ago, jowe said:

Yes i get that line 2 times. Will check a 3rd time just to be sure.

Same again 

Oct 19 12:17:52 Tower kernel: mdcmd (74): spindown 3
Oct 19 12:17:52 Tower emhttpd: error: mdcmd, 2783: Input/output error (5): write
Oct 19 12:17:52 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5
Oct 19 12:17:53 Tower kernel: mdcmd (75): spindown 3
Oct 19 12:18:09 Tower SAS Assist v0.6[14705]: spinning down slot 3, device /dev/sdh (/dev/sg7)
Oct 19 12:18:09 Tower SAS Assist v0.6[14729]: spinning down slot 3, device /dev/sdh (/dev/sg7)
root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7

I'll try to reinstall the plugin.

 

 

Link to post
1 minute ago, jowe said:

I'll try to reinstall the plugin.

Hang on.

 

What's interesting is that the command you issue manually is the same command issued by the plugin when it reports "spinning down". So something might be spinning the drive back up before you are testing.

 

The double message might be a result of your rsyslog configuration (have you changed it from default?). I have a new version of the plugin which I have not pushed out yet which should also address that. Would you mind testing something?

 

If okay with you please replace the entire contents of the file /etc/rsyslog.d/99-spinsasdown.conf with this:

# SAS Spindown Assist v0.69k
$RuleSet local

if $msg contains "spindown" and $.sasdone != 1 then {
        ^/usr/local/bin/unraid-spinsasdown
        set $.sasdone = 1 ;
        }

# Some SAS devices spew errors when hit with ATA spindown opcode; filter out
if re_match($msg, ".*error: mdcmd.*Input/output error \\(5\\): write.*") or
   re_match($msg, ".*md: do_drive_cmd:.*ATA_OP e0 ioctl error.*")
   then stop
$RuleSet remote
if re_match($msg, ".*error: mdcmd.*Input/output error \\(5\\): write.*") or
   re_match($msg, ".*md: do_drive_cmd:.*ATA_OP e0 ioctl error.*")
   then stop

Once you save the file, restart rsyslog server:

/etc/rc.d/rc.rsyslog restart

Let me know how it fares.

 

As I said this is part of an upcoming version of the plugin. BTW this has an extra benefit - it should filter out the i/o error messages that you see in your log whenever Unraid tries to spin down a SAS device.

 

Last question: What SAS controller are you using?

Link to post
1 hour ago, doron said:

Let me know how it fares.

 

I have tried it and now i get nothing in the log at all, all disks went down to standby, but the SAS drive. But not a single line in the log.

image.png.bf6175a7a0f88fd62a6782a64c683c32.png

Still showing the "green" button, but no temp.

 

Another thing i saw in the log before changing the 99-spinsasdown.conf file, was that it's trying to spin down disk3 2 times. Maybe that why the 2 lines from the plugin. That might be a problem?

 

I have not changed the rsyslog configuration.

 

1 hour ago, doron said:

Last question: What SAS controller are you using?

Using a  LSI SAS 9211-4i Flashed to IT mode.

Edited by jowe
rsyslog configuration
Link to post
1 minute ago, jowe said:

I have tried it and now i get nothing in the log at all,

Nothing?! As in no log lines at all?!

 

(If so, something must have gone wrong with the copy/paste. Did you get any error messages when you restarted rsyslogd?

Anyway, if that's the case just delete the file (99-spinsasdown.conf) and then remove/install the plugin.)

 

1 minute ago, jowe said:

all disks went down to standby, but the SAS drive. But not a single line in the log.

image.png.bf6175a7a0f88fd62a6782a64c683c32.png

Still showing the "green" button, but no temp.

The green button will not always reflect status (sometimes it will, but not with all drives/controllers). The proper indication for debugging is the sdparm command.

1 minute ago, jowe said:

 

Another thing i saw in the log before changing the 99-spinsasdown.conf file, was that it's trying to spin down disk3 2 times. Maybe that why the 2 lines from the plugin. That might be a problem?

Yes that was my assumption, which is why I asked for the test.

Link to post
16 minutes ago, doron said:

Nothing?! As in no log lines at all?!

Nothing at all  :) Will try again, i used winscp to edit the file. That should work right?
 

16 minutes ago, doron said:

The green button will not always reflect status (sometimes it will, but not with all drives/controllers). The proper indication for debugging is the sdparm command.

I know, it's not updated all the time, but usually when unraid is spinning down the disks, it will change the status.

 

16 minutes ago, doron said:

Yes that was my assumption, which is why I asked for the test.


Oct 19 14:40:56 Tower kernel: mdcmd (398): spinup 3
Oct 19 14:40:56 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e3 ioctl error: -5

Oct 19 15:19:03 Tower kernel: mdcmd (409): spindown 3
Oct 19 15:19:03 Tower emhttpd: error: mdcmd, 2783: Input/output error (5): write
Oct 19 15:19:03 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5
Oct 19 15:19:04 Tower kernel: mdcmd (410): spindown 3
Oct 19 15:19:20 Tower SAS Assist v0.6[11358]: spinning down slot 3, device /dev/sdh (/dev/sg7)
Oct 19 15:19:20 Tower SAS Assist v0.6[11412]: spinning down slot 3, device /dev/sdh (/dev/sg7)

 

 

Link to post

Same again, pasted the text below. And restarted rc.rsyslogd. 

root@Tower:~# /etc/rc.d/rc.rsyslogd restart
Starting rsyslogd daemon:
/usr/sbin/rsyslogd -i /var/run/rsyslogd.pid

 

Nothing in the log when i manually spin up / down disks. (And probably not when done automatically either).

 

image.png.a44238bd0e0f06a4978dc8b83fbed026.png

 

 

If i put the disk to sleep more than once it's still in standby. But the first time nothing happened.

 

root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
root@Tower:~# sg_start  --readonly --pc=3 /dev/sg7
root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7

root@Tower:~# sg_start  --readonly --pc=3 /dev/sg7
root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
Additional sense: Standby condition activated by command
root@Tower:~# sg_start  --readonly --pc=3 /dev/sg7
root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
Additional sense: Standby condition activated by command
root@Tower:~# sg_start  --readonly --pc=3 /dev/sg7
root@Tower:~# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
Additional sense: Standby condition activated by command
 

Edited by jowe
Link to post
8 hours ago, jowe said:

 Nothing in the log unfortunately. 

If you still have an empty log (assuming the modified 99-... file is there), I'd like to get to the bottom of this. Have you made changes (or installed 3rd party stuff that makes changes) to rsyslog.conf etc.?

Do you have other "interesting" items in /etc/rsyslog.d/ ?

Can you pm me your /etc/rsyslog.conf ?

Link to post
6 hours ago, doron said:

Can you pm me your /etc/rsyslog.conf ?

Hi, the log is empty as soon as i restart rc.rsyslogd. I used that file for an hour or so yesterday, and didn't get a single line in the log. I also went back to 6.8.3 yesterday due to performance problems. But i have the same issue with the log. And no spindown of SAS.

I also have the same problem with 3 WD RED SATA drives. On the same controller i have 4 drives that go to standby as they should. They are actually on different channels. So the 4 drives working are on one, and 4 not working are on another. Maybe something there?! I had the same problem years ago with my WD RED not spinning down, but if i remember correctly i solved it somehow. Dont remember how...

 

I have sent the file.

Link to post
10 hours ago, SimonF said:

Have you checked the smartctl wrapper is working correctly also? Otherwise the device poll will wake up the drive or any actions that do a smartctl in unraid.

How can I check that?

I have disabled my hddtemp script, but i do have "cache dirs" running, can disable that for now.

Link to post

Hi, i modified the script, and got it working. It's VERY simplified. And cusom to my setup.

 

I modified 99-spinsasdown.conf to trigger "spindown 3" For my SAS disk 3.

:msg,contains,"spindown 3" ^/usr/local/bin/unraid-spinsasdown

 

And in your script unraid-spinsasdown I removed all intelligence and just spin down the correct disk.

sg_start  --readonly --pc=3 /dev/sg7

 

Unraid log after spin up / spin down in GUI

Oct 21 10:27:41 Tower kernel: mdcmd (99): spinup 3
Oct 21 10:27:41 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e3 ioctl error: -5
Oct 21 10:28:03 Tower kernel: mdcmd (100): spindown 3
Oct 21 10:28:03 Tower emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 21 10:28:03 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5

 

And checking status

root@Tower:/# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
Additional sense: Standby condition activated by command
 

Edit:

Tried again, waited 15 min and got this, and disk not spun down..

Oct 21 10:45:52 Tower kernel: mdcmd (103): spinup 3
Oct 21 10:45:52 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e3 ioctl error: -5

Oct 21 11:00:53 Tower kernel: mdcmd (104): spindown 3
Oct 21 11:00:53 Tower emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 21 11:00:53 Tower kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5
Oct 21 11:00:54 Tower kernel: mdcmd (105): spindown 3
Oct 21 11:01:10 Tower rsyslogd: program '/usr/local/bin/unraid-spinsasdown' (pid 23020) exited with status 2 [v8.1908.0]

 

 

Edit 2

If i run /usr/local/bin/unraid-spinsasdown from CLI, the disk spins down

 

root@Tower:/mnt/disk1/media/org.rel# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
root@Tower:/mnt/disk1/media/org.rel# /usr/local/bin/unraid-spinsasdown
root@Tower:/mnt/disk1/media/org.rel# sdparm --command=sense /dev/sdh
    /dev/sdh: HP        MB8000JFECQ       HPD7
Additional sense: Standby condition activated by command
 

Edited by jowe
Link to post

Well Install Reboot and tried it and got

 

Quote

Oct 29 01:26:42 SERVERHOSTNAME emhttpd: Spinning down all drives...
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (69): spindown 0
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk0: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (70): spindown 1
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk1: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (71): spindown 2
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk2: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (72): spindown 3
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk3: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (73): spindown 4
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk4: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (74): spindown 5
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk5: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (75): spindown 6
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk6: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (76): spindown 7
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk7: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (77): spindown 8
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk8: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (78): spindown 9
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: error: mdcmd, 2723: Input/output error (5): write
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: shcmd (838): /usr/sbin/hdparm -y /dev/nvme0n1
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk9: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (79): spindown 10
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk10: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME kernel: mdcmd (80): spindown 29
Oct 29 01:26:42 SERVERHOSTNAME kernel: md: do_drive_cmd: disk29: ATA_OP e0 ioctl error: -5
Oct 29 01:26:42 SERVERHOSTNAME root: HDIO_DRIVE_CMD(standby) failed: Inappropriate ioctl for device
Oct 29 01:26:42 SERVERHOSTNAME root:
Oct 29 01:26:42 SERVERHOSTNAME root: /dev/nvme0n1:
Oct 29 01:26:42 SERVERHOSTNAME root: issuing standby command
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: shcmd (838): exit status: 25
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: shcmd (839): /usr/sbin/hdparm -y /dev/nvme1n1
Oct 29 01:26:42 SERVERHOSTNAME root: HDIO_DRIVE_CMD(standby) failed: Inappropriate ioctl for device
Oct 29 01:26:42 SERVERHOSTNAME root:
Oct 29 01:26:42 SERVERHOSTNAME root: /dev/nvme1n1:
Oct 29 01:26:42 SERVERHOSTNAME root: issuing standby command
Oct 29 01:26:42 SERVERHOSTNAME emhttpd: shcmd (839): exit status: 25
Oct 29 01:26:59 SERVERHOSTNAME SAS Assist v0.6[13372]: spinning down slot 0, device /dev/sdb (/dev/sg1)
Oct 29 01:27:17 SERVERHOSTNAME SAS Assist v0.6[14216]: spinning down slot 1, device /dev/sdd (/dev/sg3)
Oct 29 01:27:27 SERVERHOSTNAME kernel: sd 1:0:0:0: attempting task abort! scmd(00000000cecd20de)
Oct 29 01:27:27 SERVERHOSTNAME kernel: sd 1:0:0:0: [sdb] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:27:27 SERVERHOSTNAME kernel: scsi target1:0:0: handle(0x000a), sas_address(0x5000c500a73aff7d), phy(12)
Oct 29 01:27:27 SERVERHOSTNAME kernel: scsi target1:0:0: enclosure logical id(0x50030480008c3fbf), slot(0)
Oct 29 01:27:27 SERVERHOSTNAME kernel: scsi target1:0:0: enclosure level(0x0000), connector name( )
Oct 29 01:27:27 SERVERHOSTNAME kernel: sd 1:0:0:0: task abort: SUCCESS scmd(00000000cecd20de)
Oct 29 01:27:34 SERVERHOSTNAME SAS Assist v0.6[14907]: spinning down slot 2, device /dev/sde (/dev/sg4)
Oct 29 01:27:38 SERVERHOSTNAME kernel: sd 1:0:2:0: attempting task abort! scmd(00000000a3cb0183)
Oct 29 01:27:38 SERVERHOSTNAME kernel: sd 1:0:2:0: [sdd] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:27:38 SERVERHOSTNAME kernel: scsi target1:0:2: handle(0x000c), sas_address(0x5000c500a73a564d), phy(14)
Oct 29 01:27:38 SERVERHOSTNAME kernel: scsi target1:0:2: enclosure logical id(0x50030480008c3fbf), slot(2)
Oct 29 01:27:38 SERVERHOSTNAME kernel: scsi target1:0:2: enclosure level(0x0000), connector name( )
Oct 29 01:27:38 SERVERHOSTNAME kernel: sd 1:0:2:0: task abort: SUCCESS scmd(00000000a3cb0183)
Oct 29 01:27:51 SERVERHOSTNAME kernel: sd 1:0:3:0: attempting task abort! scmd(00000000d733f31d)
Oct 29 01:27:51 SERVERHOSTNAME kernel: sd 1:0:3:0: [sde] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:27:51 SERVERHOSTNAME kernel: scsi target1:0:3: handle(0x000d), sas_address(0x5000c500a73de5b5), phy(15)
Oct 29 01:27:51 SERVERHOSTNAME kernel: scsi target1:0:3: enclosure logical id(0x50030480008c3fbf), slot(3)
Oct 29 01:27:51 SERVERHOSTNAME kernel: scsi target1:0:3: enclosure level(0x0000), connector name( )
Oct 29 01:27:51 SERVERHOSTNAME kernel: sd 1:0:3:0: task abort: SUCCESS scmd(00000000d733f31d)
Oct 29 01:27:52 SERVERHOSTNAME SAS Assist v0.6[15662]: spinning down slot 3, device /dev/sdf (/dev/sg5)
Oct 29 01:28:04 SERVERHOSTNAME kernel: sd 1:0:4:0: attempting task abort! scmd(000000004eaec635)
Oct 29 01:28:04 SERVERHOSTNAME kernel: sd 1:0:4:0: [sdf] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:28:04 SERVERHOSTNAME kernel: scsi target1:0:4: handle(0x000e), sas_address(0x5000c500a73a2675), phy(16)
Oct 29 01:28:04 SERVERHOSTNAME kernel: scsi target1:0:4: enclosure logical id(0x50030480008c3fbf), slot(4)
Oct 29 01:28:04 SERVERHOSTNAME kernel: scsi target1:0:4: enclosure level(0x0000), connector name( )
Oct 29 01:28:04 SERVERHOSTNAME kernel: sd 1:0:4:0: task abort: SUCCESS scmd(000000004eaec635)
Oct 29 01:28:09 SERVERHOSTNAME SAS Assist v0.6[16180]: spinning down slot 4, device /dev/sdg (/dev/sg6)
Oct 29 01:28:16 SERVERHOSTNAME kernel: sd 1:0:5:0: attempting task abort! scmd(000000002e38697d)
Oct 29 01:28:16 SERVERHOSTNAME kernel: sd 1:0:5:0: [sdg] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:28:16 SERVERHOSTNAME kernel: scsi target1:0:5: handle(0x000f), sas_address(0x5000c50095526295), phy(17)
Oct 29 01:28:16 SERVERHOSTNAME kernel: scsi target1:0:5: enclosure logical id(0x50030480008c3fbf), slot(5)
Oct 29 01:28:16 SERVERHOSTNAME kernel: scsi target1:0:5: enclosure level(0x0000), connector name( )
Oct 29 01:28:16 SERVERHOSTNAME kernel: sd 1:0:5:0: task abort: SUCCESS scmd(000000002e38697d)
Oct 29 01:28:26 SERVERHOSTNAME SAS Assist v0.6[16861]: spinning down slot 5, device /dev/sdh (/dev/sg7)
Oct 29 01:28:34 SERVERHOSTNAME kernel: sd 1:0:6:0: attempting task abort! scmd(00000000f538fcfc)
Oct 29 01:28:34 SERVERHOSTNAME kernel: sd 1:0:6:0: [sdh] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:28:34 SERVERHOSTNAME kernel: scsi target1:0:6: handle(0x0010), sas_address(0x5000c500a61f58f1), phy(18)
Oct 29 01:28:34 SERVERHOSTNAME kernel: scsi target1:0:6: enclosure logical id(0x50030480008c3fbf), slot(6)
Oct 29 01:28:34 SERVERHOSTNAME kernel: scsi target1:0:6: enclosure level(0x0000), connector name( )
Oct 29 01:28:34 SERVERHOSTNAME kernel: sd 1:0:6:0: task abort: SUCCESS scmd(00000000f538fcfc)
Oct 29 01:28:43 SERVERHOSTNAME kernel: sd 1:0:7:0: attempting task abort! scmd(000000000b859790)
Oct 29 01:28:43 SERVERHOSTNAME kernel: sd 1:0:7:0: [sdi] tag#291 CDB: opcode=0x1a 1a 00 1c 00 ff 00
Oct 29 01:28:43 SERVERHOSTNAME kernel: scsi target1:0:7: handle(0x0011), sas_address(0x5000c500a61f52d5), phy(19)
Oct 29 01:28:43 SERVERHOSTNAME kernel: scsi target1:0:7: enclosure logical id(0x50030480008c3fbf), slot(7)
Oct 29 01:28:43 SERVERHOSTNAME kernel: scsi target1:0:7: enclosure level(0x0000), connector name( )
Oct 29 01:28:44 SERVERHOSTNAME SAS Assist v0.6[17615]: spinning down slot 6, device /dev/sdi (/dev/sg8)
Oct 29 01:28:44 SERVERHOSTNAME kernel: sd 1:0:7:0: task abort: SUCCESS scmd(000000000b859790)
Oct 29 01:28:51 SERVERHOSTNAME kernel: sd 1:0:7:0: attempting task abort! scmd(000000000b859790)
Oct 29 01:28:51 SERVERHOSTNAME kernel: sd 1:0:7:0: [sdi] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:28:51 SERVERHOSTNAME kernel: scsi target1:0:7: handle(0x0011), sas_address(0x5000c500a61f52d5), phy(19)
Oct 29 01:28:51 SERVERHOSTNAME kernel: scsi target1:0:7: enclosure logical id(0x50030480008c3fbf), slot(7)
Oct 29 01:28:51 SERVERHOSTNAME kernel: scsi target1:0:7: enclosure level(0x0000), connector name( )
Oct 29 01:28:51 SERVERHOSTNAME kernel: sd 1:0:7:0: task abort: SUCCESS scmd(000000000b859790)
Oct 29 01:28:58 SERVERHOSTNAME kernel: sd 1:0:8:0: attempting task abort! scmd(0000000032dea8e1)
Oct 29 01:28:58 SERVERHOSTNAME kernel: sd 1:0:8:0: [sdj] tag#291 CDB: opcode=0x1a 1a 00 1c 00 ff 00
Oct 29 01:28:58 SERVERHOSTNAME kernel: scsi target1:0:8: handle(0x0012), sas_address(0x5000c500a61f710d), phy(20)
Oct 29 01:28:58 SERVERHOSTNAME kernel: scsi target1:0:8: enclosure logical id(0x50030480008c3fbf), slot(8)
Oct 29 01:28:58 SERVERHOSTNAME kernel: scsi target1:0:8: enclosure level(0x0000), connector name( )
Oct 29 01:29:01 SERVERHOSTNAME SAS Assist v0.6[18297]: spinning down slot 7, device /dev/sdj (/dev/sg9)
Oct 29 01:29:01 SERVERHOSTNAME kernel: sd 1:0:8:0: task abort: SUCCESS scmd(0000000032dea8e1)
Oct 29 01:29:08 SERVERHOSTNAME kernel: sd 1:0:8:0: attempting task abort! scmd(0000000032dea8e1)
Oct 29 01:29:08 SERVERHOSTNAME kernel: sd 1:0:8:0: [sdj] tag#291 CDB: opcode=0x1a 1a 00 1c 00 ff 00
Oct 29 01:29:08 SERVERHOSTNAME kernel: scsi target1:0:8: handle(0x0012), sas_address(0x5000c500a61f710d), phy(20)
Oct 29 01:29:08 SERVERHOSTNAME kernel: scsi target1:0:8: enclosure logical id(0x50030480008c3fbf), slot(8)
Oct 29 01:29:08 SERVERHOSTNAME kernel: scsi target1:0:8: enclosure level(0x0000), connector name( )
Oct 29 01:29:08 SERVERHOSTNAME kernel: sd 1:0:8:0: task abort: SUCCESS scmd(0000000032dea8e1)
Oct 29 01:29:16 SERVERHOSTNAME kernel: sd 1:0:9:0: attempting task abort! scmd(00000000efdc7f06)
Oct 29 01:29:16 SERVERHOSTNAME kernel: sd 1:0:9:0: [sdk] tag#291 CDB: opcode=0x1a 1a 00 1c 00 ff 00
Oct 29 01:29:16 SERVERHOSTNAME kernel: scsi target1:0:9: handle(0x0013), sas_address(0x5000c500a61cc7f5), phy(21)
Oct 29 01:29:16 SERVERHOSTNAME kernel: scsi target1:0:9: enclosure logical id(0x50030480008c3fbf), slot(9)
Oct 29 01:29:16 SERVERHOSTNAME kernel: scsi target1:0:9: enclosure level(0x0000), connector name( )
Oct 29 01:29:19 SERVERHOSTNAME SAS Assist v0.6[18961]: spinning down slot 8, device /dev/sdk (/dev/sg10)
Oct 29 01:29:19 SERVERHOSTNAME kernel: sd 1:0:9:0: task abort: SUCCESS scmd(00000000efdc7f06)
Oct 29 01:29:26 SERVERHOSTNAME kernel: sd 1:0:9:0: attempting task abort! scmd(00000000efdc7f06)
Oct 29 01:29:26 SERVERHOSTNAME kernel: sd 1:0:9:0: [sdk] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:29:26 SERVERHOSTNAME kernel: scsi target1:0:9: handle(0x0013), sas_address(0x5000c500a61cc7f5), phy(21)
Oct 29 01:29:26 SERVERHOSTNAME kernel: scsi target1:0:9: enclosure logical id(0x50030480008c3fbf), slot(9)
Oct 29 01:29:26 SERVERHOSTNAME kernel: scsi target1:0:9: enclosure level(0x0000), connector name( )
Oct 29 01:29:26 SERVERHOSTNAME kernel: sd 1:0:9:0: task abort: SUCCESS scmd(00000000efdc7f06)
Oct 29 01:29:33 SERVERHOSTNAME kernel: sd 1:0:10:0: attempting task abort! scmd(0000000030113452)
Oct 29 01:29:33 SERVERHOSTNAME kernel: sd 1:0:10:0: [sdl] tag#291 CDB: opcode=0x1a 1a 00 1c 00 ff 00
Oct 29 01:29:33 SERVERHOSTNAME kernel: scsi target1:0:10: handle(0x0014), sas_address(0x5000c500a61f2909), phy(22)
Oct 29 01:29:33 SERVERHOSTNAME kernel: scsi target1:0:10: enclosure logical id(0x50030480008c3fbf), slot(10)
Oct 29 01:29:33 SERVERHOSTNAME kernel: scsi target1:0:10: enclosure level(0x0000), connector name( )
Oct 29 01:29:36 SERVERHOSTNAME SAS Assist v0.6[19771]: spinning down slot 9, device /dev/sdl (/dev/sg11)
Oct 29 01:29:36 SERVERHOSTNAME kernel: sd 1:0:10:0: task abort: SUCCESS scmd(0000000030113452)
Oct 29 01:29:43 SERVERHOSTNAME kernel: sd 1:0:10:0: attempting task abort! scmd(0000000030113452)
Oct 29 01:29:43 SERVERHOSTNAME kernel: sd 1:0:10:0: [sdl] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:29:43 SERVERHOSTNAME kernel: scsi target1:0:10: handle(0x0014), sas_address(0x5000c500a61f2909), phy(22)
Oct 29 01:29:43 SERVERHOSTNAME kernel: scsi target1:0:10: enclosure logical id(0x50030480008c3fbf), slot(10)
Oct 29 01:29:43 SERVERHOSTNAME kernel: scsi target1:0:10: enclosure level(0x0000), connector name( )
Oct 29 01:29:43 SERVERHOSTNAME kernel: sd 1:0:10:0: task abort: SUCCESS scmd(0000000030113452)
Oct 29 01:29:50 SERVERHOSTNAME kernel: sd 1:0:11:0: attempting task abort! scmd(00000000eb842a25)
Oct 29 01:29:50 SERVERHOSTNAME kernel: sd 1:0:11:0: [sdm] tag#291 CDB: opcode=0x1a 1a 00 1c 00 ff 00
Oct 29 01:29:50 SERVERHOSTNAME kernel: scsi target1:0:11: handle(0x0015), sas_address(0x5000c500a61f31b9), phy(23)
Oct 29 01:29:50 SERVERHOSTNAME kernel: scsi target1:0:11: enclosure logical id(0x50030480008c3fbf), slot(11)
Oct 29 01:29:50 SERVERHOSTNAME kernel: scsi target1:0:11: enclosure level(0x0000), connector name( )
Oct 29 01:29:54 SERVERHOSTNAME SAS Assist v0.6[20523]: spinning down slot 10, device /dev/sdm (/dev/sg12)
Oct 29 01:29:54 SERVERHOSTNAME kernel: sd 1:0:11:0: task abort: SUCCESS scmd(00000000eb842a25)
Oct 29 01:30:01 SERVERHOSTNAME kernel: sd 1:0:11:0: attempting task abort! scmd(00000000eb842a25)
Oct 29 01:30:01 SERVERHOSTNAME kernel: sd 1:0:11:0: [sdm] tag#291 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Oct 29 01:30:01 SERVERHOSTNAME kernel: scsi target1:0:11: handle(0x0015), sas_address(0x5000c500a61f31b9), phy(23)
Oct 29 01:30:01 SERVERHOSTNAME kernel: scsi target1:0:11: enclosure logical id(0x50030480008c3fbf), slot(11)
Oct 29 01:30:01 SERVERHOSTNAME kernel: scsi target1:0:11: enclosure level(0x0000), connector name( )
Oct 29 01:30:01 SERVERHOSTNAME kernel: sd 1:0:11:0: task abort: SUCCESS scmd(00000000eb842a25)
Oct 29 01:30:11 SERVERHOSTNAME SAS Assist v0.6[21225]: spinning down slot 29, device /dev/sdc (/dev/sg2)
Oct 29 01:30:17 SERVERHOSTNAME kernel: sd 1:0:1:0: attempting task abort! scmd(000000002bd64478)
Oct 29 01:30:17 SERVERHOSTNAME kernel: sd 1:0:1:0: [sdc] tag#3783 CDB: opcode=0x1a 1a 00 1c 00 ff 00
Oct 29 01:30:17 SERVERHOSTNAME kernel: scsi target1:0:1: handle(0x000b), sas_address(0x5000c50095024ed9), phy(13)
Oct 29 01:30:17 SERVERHOSTNAME kernel: scsi target1:0:1: enclosure logical id(0x50030480008c3fbf), slot(1)
Oct 29 01:30:17 SERVERHOSTNAME kernel: scsi target1:0:1: enclosure level(0x0000), connector name( )
Oct 29 01:30:17 SERVERHOSTNAME kernel: sd 1:0:1:0: task abort: SUCCESS scmd(000000002bd64478)
Oct 29 01:30:24 SERVERHOSTNAME kernel: sd 1:0:1:0: attempting task abort! scmd(000000002bd64478)
Oct 29 01:30:24 SERVERHOSTNAME kernel: sd 1:0:1:0: [sdc] tag#3783 CDB: opcode=0x1a 1a 00 1c 00 ff 00
Oct 29 01:30:24 SERVERHOSTNAME kernel: scsi target1:0:1: handle(0x000b), sas_address(0x5000c50095024ed9), phy(13)
Oct 29 01:30:24 SERVERHOSTNAME kernel: scsi target1:0:1: enclosure logical id(0x50030480008c3fbf), slot(1)
Oct 29 01:30:24 SERVERHOSTNAME kernel: scsi target1:0:1: enclosure level(0x0000), connector name( )
Oct 29 01:30:24 SERVERHOSTNAME kernel: sd 1:0:1:0: task abort: SUCCESS scmd(000000002bd64478)

 

Link to post
8 hours ago, Titus said:

Well Install Reboot and tried it and got

 

 

Thanks for reporting that.

Have you at any time tried the manual command to spin a drive down? Such as

sg_start -r --pc=3 /dev/sdX

I wonder whether it gets stuck the same way, and then gets a "task abort" a bit later. I haven't seen similar reports up until now.

Link to post

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.