• [6.9.2] Parity Drive will not spin down via GUI or Schedule


    SimonF
    • Minor

    Since upgrading to 6.9.2 I cannot spin down parity via GUI, as soon as I spin down it comes back up.

     

    Apr 8 10:18:45 Tower emhttpd: spinning down /dev/sdf
    Apr 8 10:18:58 Tower SAS Assist v0.85: Spinning down device /dev/sdf
    Apr 8 10:18:58 Tower emhttpd: read SMART /dev/sdf

     

    Revert to 6.9.1 issue no longer happens.

     

    I can manually spin down the drive. All other array drives which are also SAS spin down fine.

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

     

     

    Also is it possible to get an updated version of smartctl added.

     

    Will continue to do more testing.

     




    User Feedback

    Recommended Comments



    10 hours ago, SimonF said:

    As doron said looks normal, maybe worth posting diags in a new thread. It may be a plugin/docker or some thing else reading the disks.

    Have done that a few days ago but sadly haven't heard anything back.

    I tried to purge and control all docker and plugins that usually are the culprit, to no avail. And I think if no one has looked at it so far, it's not right to start another one probably.

    Link to comment
    On 8/18/2021 at 12:59 PM, SimonF said:

    I have re-open the thread as forgot some where having issues with SATA also.

     

    Can you povide the output from these commands?

     

    /usr/local/sbin/sdspin /dev/sdx down

    echo $?

    /usr/local/sbin/sdspin /dev/sdx

    echo $?

     

    Once your parity check is complete

     

    Sorry for the late reply.  I was traveling

     

    I pick one drive on each of the two Aerca 1882i Controller in the system.

     

    root@STORAGE2:~# /usr/local/sbin/sdspin /dev/sdd down
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    root@STORAGE2:~# echo $?
    0
    root@STORAGE2:~# /usr/local/sbin/sdspin /dev/sdd
    root@STORAGE2:~# echo $?
    0
    root@STORAGE2:~# /usr/local/sbin/sdspin /dev/sdm down
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    root@STORAGE2:~# echo $?
    0
    root@STORAGE2:~# /usr/local/sbin/sdspin /dev/sdm
    root@STORAGE2:~# echo $?
    0
    root@STORAGE2:~# 

     

     

    Link to comment

    I assume you have the SAS Spindown plugin installed. Have you updated to version 0.86?

     

    Scratch that; your drives are SATA, so the above doesn't apply. Seems like you're hitting the core problem of 6.9.2/6.10.0 with Seagate drives.

    Edited by doron
    Link to comment
    On 8/18/2021 at 6:48 PM, doron said:

     

    Your drives are SATA. The SAS Spindown plugin will not do anything for you, unfortunately (will do no harm either) - it deals exclusively with SAS drives.

     

    I'm assuming the screenshots you attached are from a 6.10.0-rc1 system? Please correct me if I'm wrong, this is an important data point.

     

    If the assumption above is correct, then

    (a) This seems to be the exact same issue that started at 6.9.2; apparently it remains in 6.10.0-rc1

    (b) Apparently this does not have to do with the mpt2sas module (its version in 6.9.1 and 6.9.2 is the same, while in 6.10.0-rc1 there's a newer version. Problem did not exist in 6.9.1).

    (c) Need to look for another change that happened between kernels 5.10.21 and 5.10.28.

     

    Meanwhile, would you mind selecting one of the drives that does not have any activity against it, and on an Unraid command shell, issue these commands (replace /dev/sdX with the drive you selected):

    hdparm -y /dev/sdX
    hdparm -C /dev/sdX
    sleep 1
    hdparm -C /dev/sdX

    (yes, the last two hdparm commands are identical)

    and post the output?

     

    I'm assuming the screenshots you attached are from a 6.10.0-rc1 system? Please correct me if I'm wrong, this is an important data point.

    You are Correct 6.10.0-rc1

     

    Your drives are SATA. The SAS Spindown plugin will not do anything for you, unfortunately (will do no harm either) - it deals exclusively with SAS drives.

    2 Parity Drives are connected to the onboard sata ports (these drives spin down) as well as the cache drive. 

    The rest of the drives are connected to two (2) Areca 1882I's in JBOD mode. The drives have stopped spinning down 

     

    Meanwhile, would you mind selecting one of the drives that does not have any activity against it, and on an Unraid command shell, issue these commands (replace /dev/sdX with the drive you selected):

     

    root@STORAGE2:~# hdparm -y /dev/sdf

    /dev/sdf:
     issuing standby command
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    root@STORAGE2:~# hdparm -C /dev/sdf

    /dev/sdf:
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     drive state is:  standby
    root@STORAGE2:~# sleep 1
    root@STORAGE2:~# hdparm -C /dev/sdf

    /dev/sdf:
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     drive state is:  standby
    root@STORAGE2:~# 

     

     

     

    Link to comment

    Sorry for the previous misfire, too many sub-threads in here.

     

    7 minutes ago, chris0583 said:

    2 Parity Drives are connected to the onboard sata ports (these drives spin down) as well as the cache drive. 

    The rest of the drives are connected to two (2) Areca 1882I's in JBOD mode. The drives have stopped spinning down 

    Yes, it seems like we have narrowed this issue down to SATA drives on SAS controllers (as opposed to onboard native SATA ports).

     

    7 minutes ago, chris0583 said:

    root@STORAGE2:~# hdparm -y /dev/sdf

    /dev/sdf:
     issuing standby command
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    root@STORAGE2:~# hdparm -C /dev/sdf

    /dev/sdf:
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     drive state is:  standby
    root@STORAGE2:~# sleep 1
    root@STORAGE2:~# hdparm -C /dev/sdf

    /dev/sdf:
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     drive state is:  standby
    root@STORAGE2:~# 

    That's interesting, I'm not sure we've seen this (bad/missing sense) with "hdparm -y" before. This might be an indicator for @limetech. Is there anything extra in the syslog at the time you issue the "hdparm -y"?

    Link to comment
    3 hours ago, chris0583 said:

    I'm assuming the screenshots you attached are from a 6.10.0-rc1 system? Please correct me if I'm wrong, this is an important data point.

    You are Correct 6.10.0-rc1

     

    Your drives are SATA. The SAS Spindown plugin will not do anything for you, unfortunately (will do no harm either) - it deals exclusively with SAS drives.

    2 Parity Drives are connected to the onboard sata ports (these drives spin down) as well as the cache drive. 

    The rest of the drives are connected to two (2) Areca 1882I's in JBOD mode. The drives have stopped spinning down 

     

    Meanwhile, would you mind selecting one of the drives that does not have any activity against it, and on an Unraid command shell, issue these commands (replace /dev/sdX with the drive you selected):

     

    root@STORAGE2:~# hdparm -y /dev/sdf

    /dev/sdf:
     issuing standby command
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    root@STORAGE2:~# hdparm -C /dev/sdf

    /dev/sdf:
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     drive state is:  standby
    root@STORAGE2:~# sleep 1
    root@STORAGE2:~# hdparm -C /dev/sdf

    /dev/sdf:
    SG_IO: bad/missing sense data, sb[]:  f0 00 05 00 00 00 00 0b 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
     drive state is:  standby
    root@STORAGE2:~# 

     

     

     

    What output do you get for the following

     

    smartctl -in never /dev/sdf

    smartctl -is standby,now /dev/sdf

    Link to comment
    1 hour ago, SimonF said:

    What output do you get for the following

     

    smartctl -in never /dev/sdf

    smartctl -is standby,now /dev/sdf

    root@STORAGE2:~# smartctl -in never /dev/sdf

    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Vendor:               Seagate
    Product:              ST10000NM0016-1T
    Revision:             R001
    Compliance:           SPC-3
    User Capacity:        10,000,831,348,736 bytes [10.0 TB]
    Logical block size:   512 bytes
    Rotation Rate:        10000 rpm
    Logical Unit id:      0x001b4d20611aecf9
    Serial number:        ZA22MCLK
    Device type:          disk
    Transport protocol:   Fibre channel (FCP-2)
    Local Time is:        Tue Aug 24 14:42:34 2021 EDT
    SMART support is:     Available - device has SMART capability.
    SMART support is:     Enabled
    Temperature Warning:  Disabled or Not Supported
    Power mode is:        ACTIVE

    root@STORAGE2:~# smartctl -is standby,now /dev/sdf
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Vendor:               Seagate
    Product:              ST10000NM0016-1T
    Revision:             R001
    Compliance:           SPC-3
    User Capacity:        10,000,831,348,736 bytes [10.0 TB]
    Logical block size:   512 bytes
    Rotation Rate:        10000 rpm
    Logical Unit id:      0x001b4d20611aecf9
    Serial number:        ZA22MCLK
    Device type:          disk
    Transport protocol:   Fibre channel (FCP-2)
    Local Time is:        Tue Aug 24 14:42:46 2021 EDT
    SMART support is:     Available - device has SMART capability.
    SMART support is:     Enabled
    Temperature Warning:  Disabled or Not Supported

    Device placed in STANDBY mode

    Link to comment

    @chris0583

     

    Can you do a test with smartctl to see what type of device it detects.

     

    Which vers did spin down work previously?

     

    root@computenode:/usr/local/emhttp/plugins/snapshots# smartctl -id test /dev/sdf
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.12-Unraid] (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    /dev/sde: Device of type 'scsi' [SCSI] detected
    /dev/sde [SAT]: Device open changed type from 'scsi' to 'sat'
    /dev/sde [SAT]: Device of type 'sat' [ATA] opened

    Link to comment
    16 minutes ago, SimonF said:

    @chris0583

     

    Can you do a test with smartctl to see what type of device it detects.

     

    Which vers did spin down work previously?

     

    root@computenode:/usr/local/emhttp/plugins/snapshots# smartctl -id test /dev/sdf
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.12-Unraid] (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    /dev/sde: Device of type 'scsi' [SCSI] detected
    /dev/sde [SAT]: Device open changed type from 'scsi' to 'sat'
    /dev/sde [SAT]: Device of type 'sat' [ATA] opened

    Here ya go

     

     

    root@STORAGE2:~# smartctl -id test /dev/sdf
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    /dev/sdf: Device of type 'scsi' [SCSI] detected
    /dev/sdf: Device of type 'scsi' [SCSI] opened

    Link to comment
    13 minutes ago, chris0583 said:

    root@STORAGE2:~# smartctl -id test /dev/sdf
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    /dev/sdf: Device of type 'scsi' [SCSI] detected
    /dev/sdf: Device of type 'scsi' [SCSI] opened

     

    Wait. What?!?

    Not what I'd expect.

     

    Please paste output of:

    sdparm -ip di_target /dev/sdf

     

    Link to comment
    16 minutes ago, chris0583 said:

    root@STORAGE2:~# smartctl -id test /dev/sdf
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    /dev/sdf: Device of type 'scsi' [SCSI] detected
    /dev/sdf: Device of type 'scsi' [SCSI] opened

    I think the issue is they are running as SCSI drives and not SATA at the host level. 

     

    it may be installing @doronSAS helper plugin may help, as it will use sdparm instead of hdparm if it detects the devices correctly. Its logic for testing the drive type may need to be tweeked.

     

    try sdparm -C sense /dev/sdf

    Edited by SimonF
    Link to comment

    Yes, seems like this controller may be presenting SATA drives as SAS protocol. @chris0583, please paste the result of the sdparm command I mentioned above, which will determine it clearly:

     

    sdparm -ip di_target /dev/sdf

     

    Link to comment
    4 minutes ago, chris0583 said:

    Here ya go

     

     

    root@STORAGE2:~# smartctl -id test /dev/sdf
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    /dev/sdf: Device of type 'scsi' [SCSI] detected
    /dev/sdf: Device of type 'scsi' [SCSI] opened

    and just to give some more info to my setup. (which has not changed since the day i build the server over 2 years ago)

     

    root@STORAGE2:~# lsscsi -g|grep "Areca"
    [1:0:16:0]   process Areca    RAID controller  R001  -          /dev/sg9  < Arcea 1881i drives 1 - 8 (sdb > sdi) >
    [8:0:16:0]   process Areca    RAID controller  R001  -          /dev/sg19 < Arcea 1881i drives 1 - 8 (sdj > sdq) >

     

    root@STORAGE2:~# smartctl -a -d areca,5,1 /dev/sg9 < device 5 on controller 1 /dev/sdf >
    smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.8-Unraid] (local build)
    Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Model Family:     Seagate Enterprise Capacity 3.5 HDD
    Device Model:     ST10000NM0016-1TT101
    Serial Number:    ZA22MCLK
    LU WWN Device Id: 5 000c50 0a49e2c70
    Firmware Version: SNCC
    User Capacity:    10,000,831,348,736 bytes [10.0 TB]
    Sector Sizes:     512 bytes logical, 4096 bytes physical
    Rotation Rate:    7200 rpm
    Form Factor:      3.5 inches
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   ACS-3 T13/2161-D revision 5
    SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is:    Tue Aug 24 16:01:27 2021 EDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled

    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED

    General SMART Values:
    Offline data collection status:  (0x82) Offline data collection activity
                                            was completed without error.
                                            Auto Offline Data Collection: Enabled.
    Self-test execution status:      (   0) The previous self-test routine completed
                                            without error or no self-test has ever 
                                            been run.
    Total time to complete Offline 
    data collection:                (  575) seconds.
    Offline data collection
    capabilities:                    (0x7b) SMART execute Offline immediate.
                                            Auto Offline data collection on/off support.
                                            Suspend Offline collection upon new
                                            command.
                                            Offline surface scan supported.
                                            Self-test supported.
                                            Conveyance Self-test supported.
                                            Selective Self-test supported.
    SMART capabilities:            (0x0003) Saves SMART data before entering
                                            power-saving mode.
                                            Supports SMART auto save timer.
    Error logging capability:        (0x01) Error logging supported.
                                            General Purpose Logging supported.
    Short self-test routine 
    recommended polling time:        (   1) minutes.
    Extended self-test routine
    recommended polling time:        ( 858) minutes.
    Conveyance self-test routine
    recommended polling time:        (   2) minutes.
    SCT capabilities:              (0x50bd) SCT Status supported.
                                            SCT Error Recovery Control supported.
                                            SCT Feature Control supported.
                                            SCT Data Table supported.

    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x000f   078   064   044    Pre-fail  Always       -       63226944
      3 Spin_Up_Time            0x0003   093   091   000    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   094   094   020    Old_age   Always       -       6360
      5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x000f   095   060   045    Pre-fail  Always       -       3274812715
      9 Power_On_Hours          0x0032   068   068   000    Old_age   Always       -       28268 (58 45 0)
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
     12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       180
    184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
    187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
    188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0 0 0
    189 High_Fly_Writes         0x003a   008   008   000    Old_age   Always       -       92
    190 Airflow_Temperature_Cel 0x0022   061   044   040    Old_age   Always       -       39 (Min/Max 33/52)
    191 G-Sense_Error_Rate      0x0032   089   089   000    Old_age   Always       -       22800
    192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       102
    193 Load_Cycle_Count        0x0032   061   061   000    Old_age   Always       -       79774
    194 Temperature_Celsius     0x0022   039   056   000    Old_age   Always       -       39 (0 23 0 0 0)
    195 Hardware_ECC_Recovered  0x001a   009   003   000    Old_age   Always       -       63226944
    197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0
    198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
    240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       12558h+46m+30.045s
    241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       284713550384
    242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       1800659171012

    SMART Error Log Version: 1
    No Errors Logged

    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Short offline       Completed without error       00%        65         -
    # 2  Short offline       Completed without error       00%        39         -
    # 3  Short offline       Completed without error       00%        31         -

    SMART Selective self-test log data structure revision number 1
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Not_testing
        2        0        0  Not_testing
        3        0        0  Not_testing
        4        0        0  Not_testing
        5        0        0  Not_testing
    Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.

    Link to comment
    1 minute ago, doron said:

    Yes, seems like this controller may be presenting SATA drives as SAS protocol. @chris0583, please paste the result of the sdparm command I mentioned above, which will determine it clearly:

     

    sdparm -ip di_target /dev/sdf

     

    root@STORAGE2:~# sdparm -ip di_target /dev/sdf
        /dev/sdf: Seagate   ST10000NM0016-1T  R001
    Device identification VPD page:

    Link to comment
    8 minutes ago, chris0583 said:

    root@STORAGE2:~# sdparm -ip di_target /dev/sdf
        /dev/sdf: Seagate   ST10000NM0016-1T  R001
    Device identification VPD page:

    Thanks. Nope, not SAS protocol (admittedly it'd have been weird if it were). So SAS Spindown plugin won't help.

    Still, does: 

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

    Do anything helpful?

    Edited by doron
    Link to comment
    15 minutes ago, doron said:

    Thanks. Nope, not SAS protocol (admittedly it'd have been weird if it were). So SAS Spindown plugin won't help.

    Still, does: 

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

    Do anything helpful?

    root@STORAGE2:~# sdparm -ip di_target /dev/sdf
        /dev/sdf: Seagate   ST10000NM0016-1T  R001
    Device identification VPD page:

     

    root@STORAGE2:~# sdparm -C sense /dev/sdf
        /dev/sdf: Seagate   ST10000NM0016-1T  R001
    Decode response as sense data:
    Fixed format, current; Sense key: Illegal Request
    Additional sense: Invalid command operation code

    Link to comment

    Are there any updates on the Spindown issue.  I have upgraded to the latest RC and my drives still continue to spin all day every day..

    Link to comment
    5 minutes ago, chris0583 said:

    Are there any updates on the Spindown issue.  I have upgraded to the latest RC and my drives still continue to spin all day every day..

     

    Not that it helps you but I too was having this issue and the latest RC fixed it for me. Sorry that you are still seeing this......

    Link to comment

    BC  thanks for the update.  Glad your issue have been resolved.   I have a bit of hope that maybe there is a fix out there for me .  Would prefer not to buy a new card / cards to get this to work.

    Link to comment

    I know this issue is specifically for the Party drives not spinning down.  But my system, is still suffering from my data drives not spinning down.  It is very frustrating.  Has there been any progress made on this issue.    Everything was working just fine with spin down until a unRAID OS update that is now preventing them. 

    Link to comment
    Just now, chris0583 said:

    Everything was working just fine with spin down until a unRAID OS update that is now preventing them. 

    What release are you using? AFAIK all spin down related issues are fixed in the latest -rc, my issues were fixed.

    Link to comment
    1 hour ago, chris0583 said:

    I know this issue is specifically for the Party drives not spinning down.  But my system, is still suffering from my data drives not spinning down.  It is very frustrating.  Has there been any progress made on this issue.    Everything was working just fine with spin down until a unRAID OS update that is now preventing them. 

    Are you able to post diagnostics?

    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
    Add a comment...

    ×   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.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.