6.9.x, LSI Controllers & Ironwolf Disks Disabling - Summary & Fix


Cessquill

Recommended Posts

  • 5 weeks later...
On 3/26/2023 at 2:16 PM, JorgeB said:

This issue appears to be limited to LSI SAS2 models, SAS2008 and SAS2308 chips, don't remember seeing anyone with a SAS3 model like the 9300-8i (SAS3008 chip) having the same problem. 

I have this problem with 9300-8i

this solution didn't help

Now the Seagate drive (only one) is attached to motherboard and all other drives (WD) to the LSI

Link to comment
On 1/16/2023 at 11:56 AM, unraidwok said:

Hope this helps!  I'm looking into changing HBA to one of the ones quoted in this thread to work around the problem - I dont want to be stuck on Linux kernel 5.16 forever. I will be back with updates!

 

Hi all, I previously posted about spinups causing dropouts on sas2008 using kernel 5.17 or newer. I recently upgraded to sas2308 cards to see if the issue is solved - Its not. I'm seeing precicely the same issue in the logs and the new cards are getting reset due to timeouts related to spinup. You can see the logs in my previous post - exactly the same is happenning.  Back to kernel 5.16 and time to order some SAS3008 cards to try.

Link to comment
On 4/27/2023 at 9:26 AM, unraidwok said:

 

getting reset due to timeouts related to spinup. You can see the logs in my previous post - exactly the same is happenning.  Back to kernel 5.16 and time to order some SAS3008 cards to try.


OK I've gotten somewhere with my problem. I'm now running linux 6.2.13 and have got rid of the scsi timeouts on spin-up that have plagued me since v5.17, and have re-enabled EPC. The hint for me was these lines in my logs:
 

sd 1:0:13:0: attempting task abort!scmd(0x0000000052c3e39b), outstanding for 10028 ms & timeout 60000 ms


I'd set the timeout for every drive to 60s but looks like theres an additional 10s timeout somewhere thats triggering consistently.  After much research and searching through /sys - I found that the scsi_device for each disk also has a timeout called eh_timeout. Here was the fix for me, applied via a local startup script on every boot:
 

#increase scsi interface timeout from 10s to 20s ( prevents HBA resetting link when disks take more than 10s to spin up)
# this is the solution to the HBA resets that were happenning version 5.17+ on SAS2008 and SAS2308
for scsi_device in /sys/bus/scsi/devices/*/eh_timeout ; do echo 20 > $scsi_device ; done


Theres now only one other error that i'm consistently getting. It involves WD and Hitachi drives on spin-up only, and looks like an LSI specific timeout. I havent found where to increase this yet, but it's non-fatal - the I/O error is only for read-ahead and is not passed down to userspace:

[ +11.033292] sd 1:0:11:0: [sdah] tag#259 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=11s
[  +0.000012] sd 1:0:11:0: [sdah] tag#259 Sense Key : 0x2 [current] 
[  +0.000004] sd 1:0:11:0: [sdah] tag#259 ASC=0x4 ASCQ=0x2 
[  +0.000006] sd 1:0:11:0: [sdah] tag#259 CDB: opcode=0x88 88 00 00 00 00 00 84 5e ae f8 00 00 03 80 00 00
[  +0.000004] I/O error, dev sdah, sector 2220797688 op 0x0:(READ) flags 0x80700 phys_seg 109 prio class 2

That error thusly can be treated as a warning, not error. I would love to know what UNKNOWN(0x2003) means though. Seems its vendor specific.
 

Thanks for everyone in this thread that has helped me get to this outcome of 100% resolved. :)  I wish everyone the best of luck with the ongoing unraid + LSI + Spin-up problems.

Edited by unraidwok
  • Like 1
Link to comment
  • 2 months later...

I've been following this thread for awhile and haven't seen any recent updates.  I was affected by the issues outlined in the OP but wasn't able to get rid of them without taking my LSI controller out of the equation and going back to running directly off the motherboard SATA controller.  I'm planning on bringing back the LSI card to allow me to add more disks to the array but I'm scared of running into this problem again.  With the new version of Unraid, has anyone tested whether the new version itself somehow avoids the discussed issues in this thread?

Link to comment
  • 2 weeks later...

My unRAID-system is still running version 6.5.3 and I am planning to upgrade "soon" - but just by chance I stumbled upon this thread and since I have 2 Seagate ST8000VN0022 drives in my array it seemed like a good thing to use the seachest* utils to disable EPC and lowCurrentSpinup to be on the safe side.

 

However, when running the Seachest_Configure executable with --EPCfeature disable, an error occurs stating that it is an unknown option , referring to --help for more information - and running with --help reveals that --EPCfeature is not a valid option (anymore)

 

So, does anyone know why the --EPCfeature option has been removed ? Or does anyone have an older version to share ?

 

The version I have tried reports the folllowing version information:

SeaChest_Configure Version: 2.3.1-4_1_1 X86_64

Link to comment
  • 1 month later...

Of 23 drives, 7 of these are ST8000VN004 mentioned in the OP, only 1 has been showing errors. All on LSI cards. Set it to no spin down since it's only 1 drive acting up. Hope this is addressed in a more refined fix as this server has been rock solid for years, until this.

 

Thanks to JorgeB for helping confirm it was errors on spin up and pointing me to this post as the likely culprit.

Edited by XDUDE3D
Link to comment
  • 1 month later...

I appear to be in this boat. Only one of the drives I have has been dropping Model Number ST10000NT001 (10TB). None of my others are causing issue. I have doen the steps in the OP. Hopefully after another rebuild this will solve the issue.

Edited by DuzAwe
Link to comment
  • 2 weeks later...

Thank you for the fix. I had been running P19 firmware on my dual M1015 LSI cards for the last 4 years. I upgraded to P20 firmware last week and the errors started showing up with  my 2 8TB ST8000VN004. One drive is 3 years old and the other is about 4 months old. 

 

Feb  6 03:10:09 Tower kernel: sd 1:0:3:0: device_block, handle(0x000c)
Feb  6 03:10:11 Tower kernel: sd 1:0:3:0: device_unblock and setting to running, handle(0x000c)
Feb  6 03:10:11 Tower kernel: sd 1:0:6:0: device_block, handle(0x000f)
Feb  6 03:10:12 Tower kernel: sd 1:0:3:0: [sdf] Synchronizing SCSI cache
Feb  6 03:10:12 Tower kernel: sd 1:0:3:0: [sdf] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Feb  6 03:10:12 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221104000000)
Feb  6 03:10:12 Tower kernel: mpt2sas_cm0: removing handle(0x000c), sas_addr(0x4433221104000000)
Feb  6 03:10:12 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(7)
Feb  6 03:10:12 Tower kernel: sd 1:0:4:0: device_block, handle(0x000d)
Feb  6 03:10:12 Tower kernel: sd 1:0:5:0: device_block, handle(0x000e)
Feb  6 03:10:13 Tower kernel: sd 1:0:4:0: device_unblock and setting to running, handle(0x000d)
Feb  6 03:10:13 Tower kernel: sd 1:0:5:0: device_unblock and setting to running, handle(0x000e)
Feb  6 03:10:13 Tower kernel: sd 1:0:6:0: device_unblock and setting to running, handle(0x000f)
Feb  6 03:10:14 Tower kernel: sd 1:0:4:0: [sdg] Synchronizing SCSI cache
Feb  6 03:10:14 Tower kernel: sd 1:0:4:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Feb  6 03:10:14 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221102000000)
Feb  6 03:10:14 Tower kernel: mpt2sas_cm0: removing handle(0x000d), sas_addr(0x4433221102000000)
Feb  6 03:10:14 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(1)
Feb  6 03:10:14 Tower kernel: sd 1:0:5:0: [sdh] Synchronizing SCSI cache
Feb  6 03:10:14 Tower kernel: sd 1:0:5:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Feb  6 03:10:14 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221106000000)
Feb  6 03:10:14 Tower kernel: mpt2sas_cm0: removing handle(0x000e), sas_addr(0x4433221106000000)
Feb  6 03:10:14 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(5)
Feb  6 03:10:14 Tower kernel: sd 1:0:6:0: [sdi] Synchronizing SCSI cache
Feb  6 03:10:14 Tower kernel: sd 1:0:6:0: [sdi] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Feb  6 03:10:14 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221107000000)
Feb  6 03:10:14 Tower kernel: mpt2sas_cm0: removing handle(0x000f), sas_addr(0x4433221107000000)
Feb  6 03:10:14 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(4)
Feb  6 03:14:53 Tower kernel: sd 1:0:7:0: device_block, handle(0x0010)
Feb  6 03:14:55 Tower kernel: sd 1:0:7:0: device_unblock and setting to running, handle(0x0010)
Feb  6 03:14:55 Tower kernel: sd 1:0:7:0: [sdj] tag#232 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=4s
Feb  6 03:14:55 Tower kernel: sd 1:0:7:0: [sdj] tag#232 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Feb  6 03:14:55 Tower kernel: sd 1:0:7:0: [sdj] tag#233 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=DRIVER_OK cmd_age=0s
Feb  6 03:14:55 Tower kernel: sd 1:0:7:0: [sdj] tag#233 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00
Feb  6 03:14:56 Tower emhttpd: read SMART /dev/sdj
Feb  6 03:14:56 Tower kernel: sd 1:0:7:0: [sdj] Synchronizing SCSI cache
Feb  6 03:14:56 Tower kernel: sd 1:0:7:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
Feb  6 03:14:56 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221105000000)
Feb  6 03:14:56 Tower kernel: mpt2sas_cm0: removing handle(0x0010), sas_addr(0x4433221105000000)
Feb  6 03:14:56 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b003e678f0), slot(6)
Feb  6 03:40:01 Tower root: mover: started
Feb  6 03:40:01 Tower root: file: //..4/...
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199808
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199816
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199824
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199832
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199840
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199848
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199856
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199864
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199872
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199880
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199888
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199896
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199904
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199912
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199920
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199928
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199936
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199944
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199952
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199960
Feb  6 03:40:07 Tower kernel: md: disk1 read error, sector=396199961

 

Edited by HAVOC
Link to comment

Running into this issue on 6.12.6 with some new 18th EXOs SAS Drives. I get Successfully Disabled EPC Feature Set on /dev/sg7. when I send command to any drives but then directly afterwards it still shows EPC enabled. Anyone seen this or have any suggestions?

Link to comment
On 2/12/2024 at 4:34 AM, dawson2938 said:

Running into this issue on 6.12.6 with some new 18th EXOs SAS Drives. I get Successfully Disabled EPC Feature Set on /dev/sg7. when I send command to any drives but then directly afterwards it still shows EPC enabled. Anyone seen this or have any suggestions?

Yes, I'm not able to keep the config changes permanent on a new ST4000VN006. Tried on Unraid and my Win PC.

Prompts are sucessfully confirmed but are back to defaults after cold reboot.

 

Link to comment
1 hour ago, optiman said:

Have you checked to see if a firmware update is available?  I had to update the firmware on one of my drives before it would work.  Even if there is no update, try flashing the firmware anyway, can't hurt.

I checked, there is no update available. FW Rev SC60

 

Link to comment

Going down the rabbit hole today with a manufacturer recertified Seagate Exos X22 ST20000NM004E from serverpartdeals.  Unraid 6.12.8.  LSI 9211-8i running P20. Threw errors minutes after Parity build completed. Suspecting EPC / power controls etc. Appreciate the details shared by all in the thread.

 

Update:  Was not able to disable using the standard seachest utilities.  Others have mentioned similar issues. Maybe removed ?

 

Was however able to use OpenSeaChest utilities in Windows to disable EPC on this specific drive. https://github.com/Seagate/openSeaChest/releases . v23.12 on Win64.

 

Pulled the drive out of unraid just to work on it standalone in a different system. Decided to try Windows 11 for fun.

 

Not everybody is an expert Linux Sysadmin so here are some screenshots to try and disable EPC on Seagate EXOS in Windows 10/11.

 

Download and unzip the contents of openSeaChest for windows. Move the unzipped file folder somewhere easy for you to manuever from command line.  I moved my folder to the c:\ drive. I renamed the folder c:\openSeaChest.

 

Open a windows command prompt terminal as admin and Change Directory to the file folder location of your openSeaChest executables. Inside you will find all of the application tools.

 

 

C:\openSeaChest>dir
 Volume in drive C has no label.
 Volume Serial Number is EAF4-51CF

 Directory of C:\openSeaChest

02/19/2024  11:31 AM    <DIR>          .
12/01/2023  05:29 PM    <DIR>          man
12/01/2023  05:28 PM           991,232 openSeaChest_Basics.exe
12/01/2023  05:28 PM           975,872 openSeaChest_Configure.exe
12/01/2023  05:28 PM         1,000,960 openSeaChest_Erase.exe
12/01/2023  05:28 PM           907,776 openSeaChest_Firmware.exe
12/01/2023  05:28 PM           972,288 openSeaChest_Format.exe
12/01/2023  05:28 PM           935,424 openSeaChest_GenericTests.exe
12/01/2023  05:28 PM         1,039,360 openSeaChest_Info.exe
12/01/2023  05:28 PM           928,768 openSeaChest_Logs.exe
12/01/2023  05:28 PM           960,512 openSeaChest_NVMe.exe
12/01/2023  05:28 PM           997,376 openSeaChest_PassthroughTest.exe
12/01/2023  05:28 PM           953,344 openSeaChest_PowerControl.exe
12/01/2023  05:28 PM           906,752 openSeaChest_Reservations.exe
12/01/2023  05:28 PM           917,504 openSeaChest_Security.exe
12/01/2023  05:29 PM         1,135,616 openSeaChest_SMART.exe
12/01/2023  05:29 PM           891,904 openSeaChest_ZBD.exe
              15 File(s)     14,514,688 bytes
               2 Dir(s)  486,452,842,496 bytes free

 

Next was to scan for devices on my system using -s switch

      openSeaChest_Basics.exe -s

 

C:\openSeaChest>openSeaChest_Basics.exe -s
==========================================================================================
 openSeaChest_Basics - openSeaChest drive utilities - NVMe Enabled
 Copyright (c) 2014-2023 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 openSeaChest_Basics Version: 3.5.4-6_2_0 X86_64
 Build Date: Dec  1 2023
 Today: Mon Feb 19 11:32:59 2024        User: admin
==========================================================================================
Vendor   Handle       Model Number            Serial Number          FwRev
SATA     PD0          ST20000NM004E-3HR103    xxxxxxxx               SN01
NVMe     PD1          SHPP41-2000GM           xxxxxxxxxxxxxxxxx      51060A20
NVMe     PD2          Samsung SSD 980 PRO 1TB xxxxxxxxxxxxxxxxx      5B2QGXA7

 

 'PD0' is the Seagate SATA Drive I'm targeting to make changes to. You may have a different device Handle.

 

Next was to get more specific information on device PD0 using the -i command where xxx  is your device.

      openSeaChest_Basics.exe -d xxx -i

 

C:\openSeaChest>openSeaChest_Basics.exe -d PD0 -i
==========================================================================================
 openSeaChest_Basics - openSeaChest drive utilities - NVMe Enabled
 Copyright (c) 2014-2023 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 openSeaChest_Basics Version: 3.5.4-6_2_0 X86_64
 Build Date: Dec  1 2023
 Today: Mon Feb 19 11:33:29 2024        User: admin
==========================================================================================

\\.\PhysicalDrive0 - ST20000NM004E-3HR103 - xxxxxxxxx - SN01 - ATA
        Model Number: ST20000NM004E-3HR103
        Serial Number: xxxxxxxxx
        Firmware Revision: SN01
        World Wide Name: xxxxxxxxxxxxxxxxx
        Date Of Manufacture: Week 35, 2023
        Drive Capacity (TB/TiB): 20.00/18.19
        Native Drive Capacity (TB/TiB): 20.00/18.19
        Temperature Data:
                Current Temperature (C): 25
                Highest Temperature (C): 32
                Lowest Temperature (C): 24
        Power On Time:  2 days 14 hours
        Power On Hours: 62.00
        MaxLBA: 39063650303
        Native MaxLBA: 39063650303
        Logical Sector Size (B): 512
        Physical Sector Size (B): 4096
        Sector Alignment: 0
        Rotation Rate (RPM): 7200
        Form Factor: 3.5"
        Last DST information:
                DST has never been run
        Long Drive Self Test Time:  1 day 4 hours 34 minutes
        Interface speed:
                Max Speed (Gb/s): 6.0
                Negotiated Speed (Gb/s): 6.0
        Annualized Workload Rate (TB/yr): 2923.26
        Total Bytes Read (GB): 88.00
        Total Bytes Written (TB): 20.60
        Encryption Support: Not Supported
        Cache Size (MiB): 512.00
        Read Look-Ahead: Enabled
        Write Cache: Enabled
        Low Current Spinup: Disabled
        SMART Status: Good
        ATA Security Information: Supported, Frozen
        Firmware Download Support: Full, Segmented, Deferred
        Specifications Supported:
                ACS-4
                ACS-3
                ACS-2
                ATA8-ACS
                ATA/ATAPI-7
                ATA/ATAPI-6
                ATA/ATAPI-5
                SATA 3.3
                SATA 3.2
                SATA 3.1
                SATA 3.0
                SATA 2.6
                SATA 2.5
                SATA II: Extensions
                SATA 1.0a
                ATA8-AST
        Features Supported:
                Sanitize
                SATA NCQ
                SATA Software Settings Preservation [Enabled]
                SATA Device Initiated Power Management
                Power Management
                Security
                SMART [Enabled]
                48bit Address
                HPA Security Extension
                PUIS
                GPL
                Streaming
                SMART Self-Test
                SMART Error Logging
                Write-Read-Verify
                DSN
                AMAC
                EPC [Enabled]
                Sense Data Reporting
                SCT Write Same
                SCT Error Recovery Control
                SCT Feature Control
                SCT Data Tables
                Host Logging
                Set Sector Configuration
                Storage Element Depopulation + Restore
                Field Accessible Reliability Metrics (FARM)
                Seagate In Drive Diagnostics (IDD)
        Adapter Information:
                Adapter Type: PCI
                Vendor ID: 8086h
                Product ID: 7AE2h
                Revision: 0011h

 

Running the -i command showed:  EPC [Enabled]

                              also showed: Low Current Startup: Disabled

 

Can be verified by also running openSeaChest_PowerControl.exe -d xxx -i

 

Now time to disable EPC by running:

      openSeaChest_PowerControl.exe -d xxx --EPCfeature disable   (Disables EPC where xxx is your device)

 

C:\openSeaChest>openSeaChest_PowerControl.exe -d PD0 --EPCfeature disable
==========================================================================================
 openSeaChest_PowerControl - openSeaChest drive utilities - NVMe Enabled
 Copyright (c) 2014-2023 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 openSeaChest_PowerControl Version: 3.4.0-6_2_0 X86_64
 Build Date: Dec  1 2023
 Today: Mon Feb 19 11:37:53 2024        User: admin
==========================================================================================

\\.\PhysicalDrive0 - ST20000NM004E-3HR103 - xxxxxxxx - SN01 - ATA
Successfully Disabled EPC Feature Set on \\.\PhysicalDrive0.

 

Confirmed that EPC was now disabled by running -i switch again from _Basics or PowerControl information. Also did a full power down (not reboot) to fully reset the hard drive and drive mainboard. The settings stuck. Confirmed below as EPC no longer shows EPC [Enabled]

 

C:\openSeaChest>openSeaChest_Basics.exe -d PD0 -i
==========================================================================================
 openSeaChest_Basics - openSeaChest drive utilities - NVMe Enabled
 Copyright (c) 2014-2023 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 openSeaChest_Basics Version: 3.5.4-6_2_0 X86_64
 Build Date: Dec  1 2023
 Today: Mon Feb 19 11:42:34 2024        User: admin
==========================================================================================

\\.\PhysicalDrive0 - ST20000NM004E-3HR103 - xxxxxxxx - SN01 - ATA
        Model Number: ST20000NM004E-3HR103
        Serial Number: xxxxxxxxx
        Firmware Revision: SN01
        World Wide Name: xxxxxxxxxxxxxx
        Date Of Manufacture: Week 35, 2023
        Drive Capacity (TB/TiB): 20.00/18.19
        Native Drive Capacity (TB/TiB): 20.00/18.19
        Temperature Data:
                Current Temperature (C): 30
                Highest Temperature (C): 32
                Lowest Temperature (C): 24
        Power On Time:  2 days 14 hours
        Power On Hours: 62.00
        MaxLBA: 39063650303
        Native MaxLBA: 39063650303
        Logical Sector Size (B): 512
        Physical Sector Size (B): 4096
        Sector Alignment: 0
        Rotation Rate (RPM): 7200
        Form Factor: 3.5"
        Last DST information:
                DST has never been run
        Long Drive Self Test Time:  1 day 4 hours 34 minutes
        Interface speed:
                Max Speed (Gb/s): 6.0
                Negotiated Speed (Gb/s): 6.0
        Annualized Workload Rate (TB/yr): 2923.26
        Total Bytes Read (GB): 88.00
        Total Bytes Written (TB): 20.60
        Encryption Support: Not Supported
        Cache Size (MiB): 512.00
        Read Look-Ahead: Enabled
        Write Cache: Enabled
        Low Current Spinup: Disabled
        SMART Status: Good
        ATA Security Information: Supported, Frozen
        Firmware Download Support: Full, Segmented, Deferred
        Specifications Supported:
                ACS-4
                ACS-3
                ACS-2
                ATA8-ACS
                ATA/ATAPI-7
                ATA/ATAPI-6
                ATA/ATAPI-5
                SATA 3.3
                SATA 3.2
                SATA 3.1
                SATA 3.0
                SATA 2.6
                SATA 2.5
                SATA II: Extensions
                SATA 1.0a
                ATA8-AST
        Features Supported:
                Sanitize
                SATA NCQ
                SATA Software Settings Preservation [Enabled]
                SATA Device Initiated Power Management
                Power Management
                Security
                SMART [Enabled]
                48bit Address
                HPA Security Extension
                PUIS
                GPL
                Streaming
                SMART Self-Test
                SMART Error Logging
                Write-Read-Verify
                DSN
                AMAC
                EPC
                Sense Data Reporting
                SCT Write Same
                SCT Error Recovery Control
                SCT Feature Control
                SCT Data Tables
                Host Logging
                Set Sector Configuration
                Storage Element Depopulation + Restore
                Field Accessible Reliability Metrics (FARM)
                Seagate In Drive Diagnostics (IDD)
        Adapter Information:
                Adapter Type: PCI
                Vendor ID: 8086h
                Product ID: 7AE2h
                Revision: 0011h

 

lowCurrentSpinup was already Disabled by default for this drive.

If you need to disable Low Current Spinup you can try to do so with this command where xxx is your device Handle using their Configure utility:

 

openSeaChest_Configure.exe -d xxx --lowCurrentSpinup disable

openSeaChest_Configure.exe -d xxx --lowCurrentSpinup disable 

 

Hope it helps others. Good luck. 

 

Edited by wuudogg
details for windows and openSeaChest
Link to comment

Join the conversation

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

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

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

×   Your previous content has been restored.   Clear editor

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