[Plugin] Spin Down SAS Drives


doron

248 posts in this topic Last Reply

Recommended Posts

Install the plugin today:

 

Feb 13 18:35:55 demiplane kernel: mdcmd (144): spindown 14
Feb 13 18:35:55 demiplane SAS Assist v0.85: spinning down slot 14, device /dev/sdr (/dev/sg19)
Feb 13 18:36:07 demiplane kernel: mdcmd (145): spindown 2
Feb 13 18:36:07 demiplane SAS Assist v0.85: spinning down slot 2, device /dev/sdc (/dev/sg3)
Feb 13 18:36:08 demiplane kernel: mdcmd (146): spindown 9
Feb 13 18:36:08 demiplane SAS Assist v0.85: spinning down slot 9, device /dev/sdj (/dev/sg10)
Feb 13 18:36:27 demiplane kernel: mdcmd (147): spindown 6
Feb 13 18:36:27 demiplane SAS Assist v0.85: spinning down slot 6, device /dev/sdg (/dev/sg7)
Feb 13 18:36:38 demiplane kernel: mdcmd (148): spindown 10
Feb 13 18:36:38 demiplane kernel: mdcmd (149): spindown 13
Feb 13 18:36:39 demiplane SAS Assist v0.85: spinning down slot 10, device /dev/sdn (/dev/sg14)
Feb 13 18:36:39 demiplane SAS Assist v0.85: spinning down slot 13, device /dev/sdq (/dev/sg18)
Feb 13 18:37:17 demiplane kernel: sd 2:0:0:0: attempting task abort! scmd(0000000055d8e9bd)
Feb 13 18:37:17 demiplane kernel: sd 2:0:0:0: [sdn] tag#6800 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Feb 13 18:37:17 demiplane kernel: scsi target2:0:0: handle(0x000b), sas_address(0x5000c50059359149), phy(0)
Feb 13 18:37:17 demiplane kernel: scsi target2:0:0: enclosure logical id(0x500143800950db00), slot(1) 
Feb 13 18:37:17 demiplane kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0000000055d8e9bd)
Feb 13 18:37:24 demiplane kernel: sd 2:0:0:0: attempting task abort! scmd(0000000055d8e9bd)
Feb 13 18:37:24 demiplane kernel: sd 2:0:0:0: [sdn] tag#6800 CDB: opcode=0x1a 1a 00 1c 00 ff 00
Feb 13 18:37:24 demiplane kernel: scsi target2:0:0: handle(0x000b), sas_address(0x5000c50059359149), phy(0)
Feb 13 18:37:24 demiplane kernel: scsi target2:0:0: enclosure logical id(0x500143800950db00), slot(1) 
Feb 13 18:37:24 demiplane kernel: sd 2:0:0:0: task abort: SUCCESS scmd(0000000055d8e9bd)
Feb 13 18:37:31 demiplane kernel: sd 2:0:4:0: attempting task abort! scmd(00000000bb542357)
Feb 13 18:37:31 demiplane kernel: sd 2:0:4:0: [sdq] tag#6754 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Feb 13 18:37:31 demiplane kernel: scsi target2:0:4: handle(0x000e), sas_address(0x5000c50063298861), phy(3)
Feb 13 18:37:31 demiplane kernel: scsi target2:0:4: enclosure logical id(0x500143800950db00), slot(4) 
Feb 13 18:37:31 demiplane kernel: sd 2:0:4:0: task abort: SUCCESS scmd(00000000bb542357)
Feb 13 18:38:13 demiplane kernel: mdcmd (150): spindown 8
Feb 13 18:38:13 demiplane SAS Assist v0.85: spinning down slot 8, device /dev/sdi (/dev/sg9)
Feb 13 18:38:14 demiplane kernel: mdcmd (151): spindown 11
Feb 13 18:38:14 demiplane SAS Assist v0.85: spinning down slot 11, device /dev/sdo (/dev/sg16)
Feb 13 18:38:37 demiplane kernel: sd 2:0:2:0: attempting task abort! scmd(000000003e983a28)
Feb 13 18:38:37 demiplane kernel: sd 2:0:2:0: [sdo] tag#7608 CDB: opcode=0x4d 4d 00 40 00 00 00 00 04 00 00
Feb 13 18:38:37 demiplane kernel: scsi target2:0:2: handle(0x000c), sas_address(0x5000c5006386444d), phy(1)
Feb 13 18:38:37 demiplane kernel: scsi target2:0:2: enclosure logical id(0x500143800950db00), slot(2) 
Feb 13 18:38:37 demiplane kernel: sd 2:0:2:0: task abort: SUCCESS scmd(000000003e983a28)

 

Then I wimped out and removed it. (lol)

 

Will now pm sas-util-out

 

Dave

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, Flubster said:

Will now pm sas-util-out

Thanks for posting, and for PMing the diagnostics.

It appears as if the problem occurs only on drives connected to your second controller (The H221). Is that a correct observation? Have you looked at the firmware of this controller?

 

Unrelated, if you're open to testing something with the array stopped, you may want to run the same "sas-util" with one parameter - "test". If you choose to do that (no pressure...), then please PM me the results.

Link to post
12 hours ago, tah said:

log file showed  before red X showed up


Feb 13 15:23:58 kernel: sd 9:0:1:0: [sdd] tag#3049 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Feb 13 15:23:58 kernel: sd 9:0:1:0: [sdd] tag#3049 Sense Key : 0x2 [current] [descriptor] 
Feb 13 15:23:58 kernel: sd 9:0:1:0: [sdd] tag#3049 ASC=0x4 ASCQ=0x11 

 

Yes, this is the dreaded 4/11 state, which basically means the drive is at a state that needs an explicit START command to spin back up, and won't spin up automatically upon i/o. 

Some combinations of drives (mainly Seagate) and controllers give this - Dell controllers like yours are often (though not always) involved - haven't figured out the exact combos yet. Each report like this one enhances the community knowledge...

 

12 hours ago, tah said:

 


sde | ST6000NM0034 | 1000:0072:1028:1f1c | n/a |
sdd | ST6000NM0034 | 1000:0072:1028:1f1c | n/a |

 

anything to help to solve the problem? I need to uninstall the plugin and rebuild my array today 😢

 

Yeah, that's painful. This is the holy grail I'm after - which drive/ctrl/firmware combinations end up doing this.

Have you checked the f/w version on your controller?

Link to post

Yeah when I next take down the array I'll attempt to run the diagnostics for you.

 

I'm not surprised i'm a tad of a fringe case, running a h221 with a msa60 hp enclosure (12 disks), with 12 spare disks unconfigured on the second channel..... therefore if this would even be a supported configuration it could be msa60's backplane firmware etc.

 

God bless HP and it's oddities

 

Dave

Link to post

I have four Seagate ST33000650SS SAS drives in my array connected to LSI 9211-8i with latest IT firmware

 

Installed SAS spindown plugin

 

I click to spin down the drives, unraid shows them as spun down but they are definitely all still spinning (other SATA drives in my array spin down correctly)

 

Unraid logs:

 

Quote

Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sde
Feb 21 05:48:48 heineken SAS Assist v0.85: Spinning down device /dev/sde
Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sdk
Feb 21 05:48:48 heineken SAS Assist v0.85: Spinning down device /dev/sdk
Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sdj
Feb 21 05:48:48 heineken SAS Assist v0.85: Spinning down device /dev/sdj
Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sdi
Feb 21 05:48:48 heineken SAS Assist v0.85: Spinning down device /dev/sdi
Feb 21 05:48:48 heineken emhttpd: spinning down /dev/sdm

 

SAS util output:

 

Quote

SAS Spindown Utility (v20210201.01)

sde     | ST33000650SS  | 1000:0072:1000:3040   |  n/a  | 
sdi     | ST33000650SS  | 1000:0072:1000:3040   |  n/a  | 
sdj     | ST33000650SS  | 1000:0072:1000:3040   |  n/a  | 
sdk     | ST33000650SS  | 1000:0072:1000:3040   |  n/a  | 

 

/tmp/sas-util-out:

 

Quote

{
  "utility-run": {
    "date": "20210221-06:03 GMT",
    "version": "20210201.01",
    "Unraid version": "6.9.0-rc2",
    "message": "",
    "drives": [
      {
        "drive": {
          "model": "ST33000650SS",
          "sdparm-i": "/dev/sde: SEAGATE ST33000650SS 0004|Device identification VPD page:| Addressed logical unit:| designator type: NAA, code set: Binary| 0x5000c50055ce4473| Target port:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce4471| designator type: Relative target port, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| Relative target port: 0x1| Target device that contains addressed lu:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce4470| designator type: SCSI name string, code set: UTF-8| SCSI name string:| naa.5000C50055CE4470|RC=0",
          "controller-id": "1000:0072:1000:3040",
          "controller-slot": "02:00.2"
        }
      },
      {
        "drive": {
          "model": "ST33000650SS",
          "sdparm-i": "/dev/sdi: SEAGATE ST33000650SS 0004|Device identification VPD page:| Addressed logical unit:| designator type: NAA, code set: Binary| 0x5000c5005600b44b| Target port:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c5005600b449| designator type: Relative target port, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| Relative target port: 0x1| Target device that contains addressed lu:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c5005600b448| designator type: SCSI name string, code set: UTF-8| SCSI name string:| naa.5000C5005600B448|RC=0",
          "controller-id": "1000:0072:1000:3040",
          "controller-slot": "02:00.2"
        }
      },
      {
        "drive": {
          "model": "ST33000650SS",
          "sdparm-i": "/dev/sdj: SEAGATE ST33000650SS 0004|Device identification VPD page:| Addressed logical unit:| designator type: NAA, code set: Binary| 0x5000c50055ce340b| Target port:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce3409| designator type: Relative target port, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| Relative target port: 0x1| Target device that contains addressed lu:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce3408| designator type: SCSI name string, code set: UTF-8| SCSI name string:| naa.5000C50055CE3408|RC=0",
          "controller-id": "1000:0072:1000:3040",
          "controller-slot": "02:00.2"
        }
      },
      {
        "drive": {
          "model": "ST33000650SS",
          "sdparm-i": "/dev/sdk: SEAGATE ST33000650SS 0004|Device identification VPD page:| Addressed logical unit:| designator type: NAA, code set: Binary| 0x5000c50055ce28db| Target port:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce28d9| designator type: Relative target port, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| Relative target port: 0x1| Target device that contains addressed lu:| designator type: NAA, code set: Binary| transport: Serial Attached SCSI Protocol (SPL-4)| 0x5000c50055ce28d8| designator type: SCSI name string, code set: UTF-8| SCSI name string:| naa.5000C50055CE28D8|RC=0",
          "controller-id": "1000:0072:1000:3040",
          "controller-slot": "02:00.2"
        }
      }
    ]
  }
}
{
  "controllers": [
    {
      "controller": {
        "Slot": "02:00.2",
        "Class": "PCI bridge [0604]",
        "Vendor": "Advanced Micro Devices, Inc. [AMD] [1022]",
        "Device": "400 Series Chipset PCIe Bridge [43c6]",
        "Rev": "01"
      }
    }
  ]
}

 

Is there anything else I can try?

Link to post

Thanks for reporting, @absolute_badger.

Might be that this drive / controller combo ignores the spindown command.

 

Right after you spin down, say, /dev/sde, and get the "Spinning down" message from SAS Assist, can you issue, against the same device:

sdparm -C sense /dev/sde

and post the output?

 

Link to post
13 hours ago, doron said:

Thanks for reporting, @absolute_badger.

Might be that this drive / controller combo ignores the spindown command.

 

Right after you spin down, say, /dev/sde, and get the "Spinning down" message from SAS Assist, can you issue, against the same device:


sdparm -C sense /dev/sde

and post the output?

 

 

Done:

 

Quote

root@heineken:~# sdparm -C sense /dev/sde
    /dev/sde: SEAGATE   ST33000650SS      0004

 

Link to post
7 minutes ago, absolute_badger said:

root@heineken:~# sdparm -C sense /dev/sde
    /dev/sde: SEAGATE   ST33000650SS      0004

Is there any i/o going on against this drive (look at the read/write counters) during that time?

 

If there's none, we'd probably conclude that this drive/controller combo ignores the spindown command.

 

If you want to triple check, you may want to run this sequence in quick succession - when there's no i/o happening against the drive:

sg_start -rp3 /dev/sde
sdparm -C sense /dev/sde

If the output is the same as in the previous test, then it's settled 😞

Link to post

Hi,

 

i am currently using a Supermicro HBA with 15 Drives connected to it. 8 of them are SAS. My problem is not that the drives don't spin down. Currently they never come back up. Causing Unraid to belive that there is an IO Error. It also doesnt matter what command you throw at the spun down drive. Nothing gets them back, not even an hard reset of the server btw. 

 

A power cycle reactivates them and they show up back fine after the power cycle. 

 

Controller:

01:00.0 Serial Attached SCSI controller: Adaptec Device 8076 (rev 06)

 

Dmesg:

 

[   17.223324] pm80xx 0000:01:00.0: pm80xx: driver version 0.1.40
[   17.224929] :: pm8001_pci_alloc  523:Setting link rate to default value
[   18.243882] scsi host1: pm80xx

 

SAS Spindown Utility (v20210201.01)

sdf     | HUH721010AL5200       | 9005:8076:15d9:1600   |  n/a  | 
sde     | HUH721010AL5200       | 9005:8076:15d9:1600   |  n/a  | 
sdg     | HUH721010AL5200       | 9005:8076:15d9:1600   |  n/a  | 
sdh     | HUH721010AL5200       | 9005:8076:15d9:1600   |  n/a  | 
sdo     | ST4000NM0025  | 9005:8076:15d9:1600   |  n/a  | 
sdp     | ST4000NM0025  | 9005:8076:15d9:1600   |  n/a  | 
sdq     | ST4000NM0025  | 9005:8076:15d9:1600   |  n/a  | 
sdr     | ST4000NM0025  | 9005:8076:15d9:1600   |  n/a  | 

 

I also tryed the default method with the Idle Timer and sgutils . They spin down fine :) but never back up ..... 

 

Unraid is 6.9.0-rc2

 

Unfortnuatly the HBA is weird is hell, because Supermicro is not offering any documentation. You can find something about it here: https://www.supermicro.com/wdl/driver/SAS/Microsemi/8076/B11419 

Official product number: SMC AOC-S8076-L16E

 

Any ideas would be really appreciated.

 

Regards,

 

 

 

 

 

sas-util-out

Link to post
2 hours ago, half said:

Any ideas would be really appreciated

 

 

What results do you get with

 

sg_start -rp3 /dev/sdx

sdparm -C sense /dev/sdx

 

Also have you tried the start with sg_start?

sg_start -rs /dev/sdx may be required to spinup the drive. or just -s.

 

are you able to provide lspci -k for the card to see which driver it is using? 

 

07:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] (rev 02)
        Subsystem: Broadcom / LSI 9201-16e 6Gb/s SAS/SATA PCIe x8 External HBA
        Kernel driver in use: mpt3sas
        Kernel modules: mpt3sas

Edited by SimonF
Link to post

Hi,

 

sure thing:

 

lspci -k

01:00.0 Serial Attached SCSI controller: Adaptec Device 8076 (rev 06)
        Subsystem: Super Micro Computer Inc Device 1600
        Kernel driver in use: pm80xx
        Kernel modules: pm80xx

 

sg_start -rp3 /dev/sdf

 

sdparm -C sense /dev/sdf
    /dev/sdf: HGST      HUH721010AL5200   A21D
Additional sense: Standby condition activated by command

 

sg_start -rs .... long wait nothing happens while  I/O errors in dmesg

 

[18525.321658] sd 1:0:1:0: [sdf] tag#663 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
[18525.321660] sd 1:0:1:0: [sdf] tag#663 Sense Key : 0x2 [current] [descriptor] 
[18525.321661] sd 1:0:1:0: [sdf] tag#663 ASC=0x4 ASCQ=0x11 
[18525.321662] sd 1:0:1:0: [sdf] tag#663 CDB: opcode=0x88 88 00 00 00 00 04 8c 3f ff 00 00 00 00 08 00 00
[18525.321663] blk_update_request: I/O error, dev sdf, sector 19532873472 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[18525.321870] Buffer I/O error on dev sdf1, logical block 19532871424, async page read
[18525.321965] Buffer I/O error on dev sdf1, logical block 19532871425, async page read

 

And then kernel panic a moment after that..... 

 

 

 

Link to post

i wouldnt assume the effect to be different because -r only does ReadOnly. So not sure, as i just went trough crash 3 resets and some soft reboots will try again tomorrow. 

 

But i fear there is something weird with the Controller HDD combo. As a simple IO to the device should actually start it up again imho

Link to post
  • 2 weeks later...
7 hours ago, SimonF said:

@doron

 

Not sure if you have seen this post, this is for Ironwolf SATA drives, but some of the findings may help with the SAS Seagate issues people have.

 

https://www.seagate.com/gb/en/support/software/seachest/

 

Thanks @SimonF. Indeed a relevant thread.

 

The suggested solution (or workaround) is to disable EPC. This will alleviate the issue as described, but may also defeat the purpose of spindown; doesn't disabling EPC feature entirely also disable the various power states we're using to spin down drives? At least that is my reading of the docs.

 

I don't have Ironwolf drives to test this, but if I did I'd disable EPC and then try to spin the drive down (use sdspin in 6.9+ or hdparm previously) and check whether it actually did.

Link to post

Done a test with my 4TB SAS Drive, still works as expected, but does not indicate current state, have tried both enable and disabled.

 

Could be that my drive is  old and it doesn't make a difference.

 

root@Tower:/tmp/Seachest# SeaChest_PowerControl_1100_11923_64 -d /dev/sg6 --EPCfeature disable
==========================================================================================
 SeaChest_PowerControl - Seagate drive utilities - NVMe Enabled
 Copyright (c) 2014-2019 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 SeaChest_PowerControl Version: 1.10.0-1_19_23 X86_64
 Build Date: Jun 10 2019
 Today: Thu Mar 11 08:02:44 2021
==========================================================================================

/dev/sg6 - ST4000NM0023 -  - SCSI
Successfully Disabled EPC Feature Set on /dev/sg6.

root@Tower:/tmp/Seachest# SeaChest_Basics_280_11923_64 -id /dev/sg6
==========================================================================================
 SeaChest_Basics - Seagate drive utilities - NVMe Enabled
 Copyright (c) 2014-2019 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 SeaChest_Basics Version: 2.8.0-1_19_23 X86_64
 Build Date: Jun 10 2019
 Today: Thu Mar 11 08:02:55 2021
==========================================================================================

/dev/sg6 - ST4000NM0023 -  - SCSI
        Vendor ID: SEAGATE 
        Model Number: ST4000NM0023    
        Serial Number: 
        Firmware Revision: XMGJ
        World Wide Name: 5000C500626C01EB
        Copyright: Copyright (c) 2016 Seagate All rights reserved 
        Drive Capacity (TB/TiB): 4.00/3.64
        Temperature Data:
                Current Temperature (C): 33
                Highest Temperature (C): Not Reported
                Lowest Temperature (C): Not Reported
        Power On Time:  5 years 2 days 23 hours 50 minutes 
        Power On Hours: 43871.83
        MaxLBA: 7814037167
        Native MaxLBA: Not Reported
        Logical Sector Size (B): 512
        Physical Sector Size (B): 512
        Sector Alignment: 0
        Rotation Rate (RPM): 7200
        Form Factor: 3.5"
        Last DST information:
                Time since last DST (hours): 33708.83
                DST Status/Result: 0x1
                DST Test run: 0x1
        Long Drive Self Test Time:  9 hours 5 minutes 
        Interface speed:
                Port 0 (Current Port)
                        Max Speed (GB/s): 6.0
                        Negotiated Speed (Gb/s): 6.0
                Port 1
                        Max Speed (GB/s): 6.0
                        Negotiated Speed (Gb/s): Not Reported
        Annualized Workload Rate (TB/yr): 213.28
        Total Bytes Read (TB): 790.10
        Total Bytes Written (TB): 278.04
        Encryption Support: Not Supported
        Cache Size (MiB): Not Reported
        Read Look-Ahead: Not Supported
        Write Cache: Disabled
        SMART Status: Good
        ATA Security Information: Not Supported
        Firmware Download Support: Full, Segmented, Deferred
        Specifications Supported:
                SPC-4
        Features Supported:
                Protection Type 1
                Protection Type 2 [Enabled]
                Application Client Logging
                Self Test
                Automatic Write Reassignment [Enabled]
                Automatic Read Reassignment [Enabled]
                EPC
                Informational Exceptions [Mode 6]
                Translate Address
                Format Unit

root@Tower:/tmp/Seachest# sdparm -C sense /dev/sdg
    /dev/sdg: SEAGATE   ST4000NM0023      XMGJ
root@Tower:/tmp/Seachest# sg_start -rp 3 /dev/sdg
root@Tower:/tmp/Seachest# sdparm -C sense /dev/sdg
    /dev/sdg: SEAGATE   ST4000NM0023      XMGJ
Additional sense: Standby condition activated by command
root@Tower:/tmp/Seachest# sdparm -C sense /dev/sdg
    /dev/sdg: SEAGATE   ST4000NM0023      XMGJ
root@Tower:/tmp/Seachest# sg_start -rp 3 /dev/sdg
root@Tower:/tmp/Seachest# sdparm -C sense /dev/sdg
    /dev/sdg: SEAGATE   ST4000NM0023      XMGJ
Additional sense: Standby condition activated by command
root@Tower:/tmp/Seachest# 

 

Edited by SimonF
Link to post

Unraid 6.9.1

Hp proliant dl380e

HBA HP h220

SAS DISK from HGST partnr  HUS723030ALS640

 

Sas spin down works with delay from disk settings

Sas spin up works with spin  up button without error.

But spin up / wake from docker/plex spin up but count 4 error on disk 1 in array.

 

Why is count 4  error on disk 1?

Link to post
16 hours ago, SimonF said:

Done a test with my 4TB SAS Drive, still works as expected, but does not indicate current state, have tried both enable and disabled.

 

Could be that my drive is  old and it doesn't make a difference.

 

I didn't see an indication of EPC being disabled in the referenced post, either. The feature is marked supported but not indicated as enabled/disabled.

 

The feature that was indicated as disabled was "Low Current Spinup". This is a Seagate feature that "smoothes" the spin-up process, so the drive does not vibrate and the bearings do not get too stressed up - and in the way, makes the spin up even longer, which is probably what generates the i/o errors.

Are you able to test this one? It is described as

SeaChest_Configure_xxxx -d /dev/sgYY --lowCurrentSpinup disable

 

Link to post
36 minutes ago, doron said:

Are you able to test this one? It is described as

root@Tower:~# /tmp/Seachest/SeaChest_Configure_1170_11923_64 -d /dev/sg6 --lowCurrentSpinup disable
==========================================================================================
 SeaChest_Configure - Seagate drive utilities - NVMe Enabled
 Copyright (c) 2014-2019 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 SeaChest_Configure Version: 1.17.0-1_19_23 X86_64
 Build Date: Jun 10 2019
 Today: Thu Mar 11 10:47:03 2021
==========================================================================================

/dev/sg6 - ST4000NM0023 -  - SCSI
Set Low Current Spinup
Setting Low Current Spinup not supported on this device
 

Not supported on my Drive :(

Edited by SimonF
Link to post
10 hours ago, SimonF said:

 

Not supported on my Drive :(

 

Probably because:

 

--lowCurrentSpinup [ low | ultra | disable ]  (SATA Only) (Seagate Only)

 

😞

 

Link to post

Interesting:

 

I don't have SAS drives but I do have a USB drive (Unassigned Device) with a faulty interface that prevents unRAID from properly detecting idle status - so (a) the webGUI shows it spunup regardless of status and (b) unraid issues it a spindown command every spindown interval.

 

Faulty interface (sdb is the USB):

root@NAS:~# hdparm -C /dev/sdb

/dev/sdb:
SG_IO: bad/missing sense data, sb[]:  f0 00 01 00 50 40 00 0a 80 00 00 00 00 1d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
drive state is:  unknown

 

I installed this plugin thinking I'd use the code to write my own wrapper but mysteriously it's solved my problem - the drive's status in the webGUI is accurate and no unnecessary spindown commands.

 

Thanks? :)

 

Debug log in case you're curious:

Spoiler

 

Mar 15 12:03:41 NAS emhttpd: read SMART /dev/sdb

Mar 15 12:03:41 NAS SAS Assist v0.85: debug: smartctl wrapper caller is smartctl_type, grandpa is emhttpd, device /dev/sdb, args "-A /dev/sdb"

Mar 15 12:03:44 NAS SAS Assist v0.85: debug: smartctl wrapper caller is timeout, grandpa is sh, device /dev/sdb, args "--nocheck=standby --attributes -d auto /dev/sdb"

Mar 15 12:09:11 NAS SAS Assist v0.85: debug: smartctl wrapper caller is bash, grandpa is sshd, device /dev/sdb, args "--nocheck standby -i /dev/sdb"

Mar 15 12:12:55 NAS SAS Assist v0.85: debug: smartctl wrapper caller is smartctl_type, grandpa is emhttpd, device /dev/sdb, args "-A /dev/sdb"

Mar 15 12:18:42 NAS emhttpd: spinning down /dev/sdb

Mar 15 12:18:54 NAS SAS Assist v0.85: debug: smartctl wrapper caller is timeout, grandpa is sh, device /dev/sdb, args "--nocheck=standby --attributes -d auto /dev/sdb"

Mar 15 12:19:26 NAS SAS Assist v0.85: debug: smartctl wrapper caller is timeout, grandpa is sh, device /dev/sdb, args "--nocheck=standby --attributes -d auto /dev/sdb"

Mar 15 12:19:57 NAS SAS Assist v0.85: debug: smartctl wrapper caller is timeout, grandpa is sh, device /dev/sdb, args "--nocheck=standby --attributes -d auto /dev/sdb"

Mar 15 12:20:29 NAS SAS Assist v0.85: debug: smartctl wrapper caller is timeout, grandpa is sh, device /dev/sdb, args "--nocheck=standby --attributes -d auto /dev/sdb"

 

 

Link to post
2 hours ago, CS01-HS said:

mysteriously it's solved my problem - the drive's status in the webGUI is accurate and no unnecessary spindown commands.

What version of Unraid are you running?

 

2 hours ago, CS01-HS said:

Thanks? :)

😀

 

2 hours ago, CS01-HS said:

Debug log in case you're curious:

 

How did you set the debug on? Did you modify the code or use one of the debug triggers?

 

Link to post
25 minutes ago, doron said:

What version of Unraid are you running?

 

v6.9.1

 

27 minutes ago, doron said:

How did you set the debug on? Did you modify the code or use one of the debug triggers?

 

I changed DEBUG to true in /usr/local/emhttp/plugins/sas-spindown/functions

and ran: touch /tmp/spindownsas-debug

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.