Issue with Setting Sector Size on Seagate ST24000NM002H after Interruption, Drive Bricked

[huahuasousou]

Hello everyone,

I am experiencing difficulties with formatting and setting the sector size on my Seagate ST24000NM002H-3KS133 drive using SeaChest tools. I perfom the commad --setSectorSize 4096. But the command showed that the setSectorSize operation failed and a quick format operation was automatically initiated to recover the drive. However, I mistakenly believed that the quick format operation had completed, so I unplugged the SATA cable, leading to a disaster. Now, the LBA is showing as 0, and the SMART information only displays basic details. Any operations I try to perform are indicated as not supported.
Below is the result of my attempt to perform the setSectorSize operation again:
setSectorSize_log.log

Here are the details of the device and system:

Environment
SeaChest Version: 4.3.6-6_2_0 X86_64
Operating System: Windows 10

Device Information
Model Number: ST24000NM002H-3KS133
Serial Number: ZYD079RP
Firmware Revision: SE05
Physical Sector Size: 4096 bytes
Logical Sector Size: 512 bytes
Steps and Commands Used:
\SeaChest_Format_x64_windows.exe -d PD1 --setSectorSize 4096 --confirm this-will-erase-data-and-may-render-the-drive-inoperable

Request
The issue to have started after an interruption during a sector size change operation (the command shown failed and try to use quick format to recover, but ). Now, the drive is unresponsive, and I suspect it might be due to an internal security lock in the firmware that has bricked the device. Could you please assist in resolving this issue? Is there any way to unlock the drive and restore its functionality? Any insights or additional steps would be greatly appreciated. If more information is needed, I can provide additional details.

Thank you for your support!

[vonericsen]

Hi @huahuasousou,

On #145 I shared a test build with a --force option. Can you give that a try and see if it solves this issue for you?

[huahuasousou]

Hi @huahuasousou,

On #145 I shared a test build with a --force option. Can you give that a try and see if it solves this issue for you?

Hi, thank you for the suggestion. I had already checked all the issues related to setSectorSize and even tried using the pre-built version with the --force option before sending it in for RMA. Unfortunately, that did not work for me.
Since the SMART information is currently unreadable, and both long and short tests cannot be performed, maybe I has thoroughly corrupted the firmware, since I was directly unplugging the SATA cable. There is likely little chance of recovery now. Nevertheless, I appreciate your response.

[vonericsen]

@huahuasousou,

Thank you for letting me know that did not work.
I am still investigating what else we can do in our tools to mitigate this further.
RMA is the best choice when at the point where the tool is unable to get it to recover.

If you have any suggestions on additional warnings that can be printed on the screen that would have helped, please let me know.