Failed set sector size Is there any way to recover?

[KeinNiemand]

I tired setting the sector size to 4096 on my brand new ST16000NM000J, attached via a USB-SATA adapter (specifically a FANTEC QB-35U31), I stupefy ignored all the warnings and probably destroyed my brand new drive.

This is the output of running the command:
Set Sector Size to 4096
Setting the drive sector size quickly.
It should complete in under 5 minutes, but interrupting it may make
the drive unusable or require performing this command again!!
The command is issued with a timeout of 1 hour, much longer than necessary,
however there are rare cases where a drive is processing something in the
background when this command is received that may make this take longer than
a few minutes. Please wait at least this hour to ensure that this completes
successfully or with the error recovery built into this software.
ERROR: The device was reset during sector size change. Device may not be usable!
Attempting Seagate quick format to recover the device.
WARNING: Seagate quick format did not complete successfully!
ERROR: Quick format did not recover the device. The device may not be usable!
Failed to set sector size!
For SCSI Drives, try a format unit operation to recover the device
Trying to do it again and even trying something as simple as reading smart status now gives me errors.

Trying the command again results in an error that setting sector size is not supported

/dev/sg1 - M000J-2TW103 - 0000000000000001 - SN04 - ATA
Set Sector Size to 4096
Setting sector size not supported on this device

Trying to do anything else on the drive like reading smart data also fails

sudo openSeaChest_SMART -d /dev/sdb --smartAttributes hybrid
==========================================================================================
 openSeaChest_SMART - openSeaChest drive utilities - NVMe Enabled
 Copyright (c) 2014-2023 Seagate Technology LLC and/or its Affiliates, All Rights Reserved
 openSeaChest_SMART Version: 2.3.2-6_2_0 X86_64
 Build Date: Dec  4 2023
 Today: Fri Oct 18 19:27:23 2024        User: root
==========================================================================================

/dev/sg1 - M000J-2TW103 - 0000000000000001 - SN04 - ATA
Error retreiving the logs.
A failure occured while trying to get SMART attributes

The only thing that still works is doing a -i to view information anything else I tried fails

sudo openSeaChest_Basics -i -d /dev/sdb
==========================================================================================
 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  4 2023
 Today: Fri Oct 18 19:32:02 2024        User: root
==========================================================================================

/dev/sg1 - M000J-2TW103 - 0000000000000001 - SN04 - ATA
        Vendor ID: ST16000N
        Model Number: M000J-2TW103
        Serial Number: 0000000000000001
        Firmware Revision: SN04
        World Wide Name: 5000C5007445118F
        Drive Capacity (TB/TiB): 16.00/14.55
        Temperature Data:
                Current Temperature (C): Not Reported
                Highest Temperature (C): Not Reported
                Lowest Temperature (C): Not Reported
        Power On Time: Not Reported
        Power On Hours: Not Reported
        MaxLBA: 31251759103
        Native MaxLBA: Not Reported
        Logical Sector Size (B): 512
        Physical Sector Size (B): 4096
        Sector Alignment: 0
        Rotation Rate (RPM): 7200
        Form Factor: 3.5"
        Last DST information:
                Not supported
        Long Drive Self Test Time: Not Supported
        Interface speed:
                Max Speed (Gb/s): 6.0
                Negotiated Speed (Gb/s): 6.0
        Annualized Workload Rate (TB/yr): Not Reported
        Total Bytes Read (B): Not Reported
        Total Bytes Written (B): Not Reported
        Encryption Support: Not Supported
        Cache Size (MiB): Not Reported
        Read Look-Ahead: Enabled
        Write Cache: Enabled
        Low Current Spinup: Disabled
        SMART Status: Unknown or Not Supported
        ATA Security Information: Not Supported
        Firmware Download Support: Full, Segmented
        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
                SPC-4
                SPC-4
                SBC-3
                UAS
        Features Supported:
                Sanitize
                SATA NCQ
                SATA Software Settings Preservation [Enabled]
                SATA Device Initiated Power Management
                Power Management
                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
        Adapter Information:
                Adapter Type: USB
                Vendor ID: 2109h
                Product ID: 0715h
                Revision: 0614h

Is there anything I can try to recover the drive or is it just straight up dead?

[onebitboy]

I had the same error after trying to set the sector size with an external USB case. It worked fine again after connecting it to an internal SATA port and setting the sector size once more.

[vonericsen]

@KeinNiemand,

Sorry you had this happen. The only thing you can do is to try the command again. I did add a --force option to try and force it to run the command again, but I cannot guarantee it will fix it.
I have been testing other possible code changes to mitigate this further for a while now, but I still have not found any improvements to this process yet.