[NO-DATA-RECOVERY] ST2000DM001 (9YN164) wrong heads FW

[aboveunder]

Hey gurus!
I've registered here 'cause I found a lot of your posts as results when searching for fixes about Seagate.
I'm new for what concerns about this kind of low-level informations and HDD stuffs (and also their architectures).
I'm from Italy and I'm a quite amateur enthusiast when speaking about computers and Linux (so many years I don't use Windows).
Something other about me... Well, I like fishing, rally cars, and old arcade games.
I'm not an IT engineer neither an electronics expert.
First time having to deal with problematic HDD.
Hope you'll kindly take out from my troubles!!

\\\

Ok, I'll describe my issue regarding the post's title.
I was trying to update the firmware of ST2000DM001 with PN: 9YN164-500.

The disk is empty, I DO NOT need to recovery any data in it!

You'll see more infos in the attached images.
Here's a sum-up of steps I've done:

1. Thanks to this issue on GitHub (https://github.com/Seagate/openSeaChest/issues/36) I updated the firmware onto another Seagate (not the one for what I'm asking your help)
2. From that successful updating, then I tried to proceed for the update onto ST2000DM001 (PN: 9YN164-500)
3. So, I again used the same utility (closed source version): https://github.com/Seagate/ToolBin/blob/master/SeaChest/Firmware/v2.8.2/Linux/SeaChest_Firmware_282_12130_64
4. Searched for firmware via the serial number using this link: https://apps1.seagate.com/downloads/request.html
5. That leads me to here: https://www.seagate.com/it/it/support/kb/barracuda-1tbdisk-platform-firmware-update-223651en/
6. Downloaded the ISO: http://www.seagate.com/staticfiles/support/downloads/firmware/Barracuda-ALL-GRCC4H.iso
7. Extracted the ISO
8. Renamed GR-CC4H.ima to GR-CC4H.img
9. Extracted GR-CC4H.img
10. From inside it I found LOD.zip, extracted
11. Inside the zip there are the LOD firmwares and CFS config file

12. Code:

    # ./SeaChest_Firmware_282_12130_64 -d /dev/sdd --fwdlConfig GR-CC4H.CFS

13. Does nothing, no errors, but neither upgrading firmware
14. So I proceeded the manual update

15. Code:

    # ./SeaChest_Firmware_282_12130_64 -d /dev/sdd --downloadFW GRCC4H4H.LOD

16. I suddenly heard trange scratching noises and the disk became unresponsive for about 5 minutes. Maybe wrong heads firmware?
17. The program then exited successfully, but the HDD doesn't appears anymore, neither after a full computer poweroff cycle
18. I choose GRCC4H4H.LOD because of this: http://blog.asiantuntijakaveri.fi/2013/09/updating-seagate-st3000dm001-9yn166-to.html
19. and this: http://www.users.on.net/~fzabkar/HDD/GR-CC4H.TXT

Now HDD isn't recognized nor in BIOS neither in Linux and when the computer boots, I hear the HDD trying to spin up with no success (meanwhile HDD's activity LED remains steady).
After about 15 seconds, the computer boots fine, but still the disk is not recognized

Here's to you dmesg log from Linux and output log from TTL serial to USB:

Code:

ata4: softreset failed (1st FIS failed)
ata4: softreset failed (1st FIS failed)
ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata4.00: qc timeout (cmd 0xec)
ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Code:

Boot 0x40M                                                                                                                       
Servo !supported preamp ID 0000                                                                                                 
Spin Up                                                                     
FAIL  Servo Op=0100 Resp=0003                                               
ResponseFrame 04C0 0080 03B4 2800 0008 0000 0000 0000 10E6 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0010
FAIL  Servo Op=0100 Resp=0003                             
ResponseFrame FD40 0080 03B4 2880 0008 0000 0000 0000 10CB 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000
FAIL  Servo Op=0100 Resp=0003                             
ResponseFrame FD80 0080 03B4 2880 0008 0000 0000 0000 10CB 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000
FAIL  Servo Op=0100 Resp=0003                             
ResponseFrame FD80 0080 03B4 2900 0008 0000 0000 0000 10B0 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame FD80 0080 03B4 28C0 0008 0000 0000 0000 10BD 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame FD40 0080 03B4 2900 0008 0000 0000 0000 10B0 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame FD40 0080 03B4 2840 0008 0000 0000 0000 10D8 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame FD40 0080 03B4 2840 0008 0000 0000 0000 10D8 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame FD00 0080 03B4 2880 0008 0000 0000 0000 10CB 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame FD40 0080 03B4 28C0 0008 0000 0000 0000 10BD 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame FD00 0080 03B4 2840 0008 0000 0000 0000 10D8 0000 0000 0000 0000 0000 0000 0000 E6F7 8D3E D114 0400 0900 8821 DF45 BFDC E7CF B2C7 0000 007F 0000 0000 0021 0004 0000

Also, CTRL+Z does nothing.


Here's photos:

st2000dm001_9yn164 (label)

st2000dm001_9yn164 (other part number)

[pepe]

These drives are prone to develop surface and head damages just by themselves. If you already had issues with it before you forced that fw update, i think this is the case.
I doubt that any fw version for the same family would cause such log.

Code:

Servo !supported preamp ID 0000   

this one is odd as well, coz surface and head problems do not cause such log i think. Unless you have bad contact between PCB and HDA in addition.

pepe

[aboveunder]

These drives are prone to develop surface and head damages just by themselves. If you already had issues with it before you forced that fw update, i think this is the case.

No issues at all until my bad try when updating firmware.

[aboveunder]

... So guys... What do you say? Any hope to recover my HDD?

[aboveunder]

Sorry, I don't see the EDIT button for my previous post.
Forgot to tell you that the errors appear with ad without the piece of paper between PCB and motor contacts!
I'm linking you a video I just made of the inside of the HDD: https://streamable.com/oriv0j

[MasterT]

Now that you've opened the case all is left is to put it in the freezer. That should fix your problem.

[aboveunder]

Now that you've opened the case all is left is to put it in the freezer. That should fix your problem.

... LoL... Are you serious?!?

[pepe]

yeah, no point in repairing it after you opened the HDA.
The story is somewhat odd to me and i would be really interested wether that fw update could have killed the preamp, which i doubt... do you get that !supported preamp ID 0000 msg without isolating the preamp?
It is a bit confusing me, i am not even sure you put the paper between motor contacts or preamp contacts...
I also met a fw update flaw on 7200.4 drives. The client updated several drives at their company and one of them failed at some point, leaving the backed up adaptive files in the folder the update was run from. When they tried to update the next disk, the update process was unable to save the current adaptives because the files already existed, but it did not fail with an error, it continued to the update and uploaded the prev. disk's adaptives to the current one, effectively killing it for good. But even in that case the drive was OK mechanically and electrically as well, 'only' the adaptives were swapped.

Anyway, your drive is not repairable, if you had data on it it would be probably recoverable, but since you don't, there's no point trying anything.

pepe

[aboveunder]

Ok, I'm closing this request.
Marked as UNSOLVABLE.

... Guys, if someone is interested and could recover this HDD as its spare parts, then I can give to you for free, gratis, if someone would pay shipping fees from Italy.

Let me know, bye!

Thanks for all your kind support and you time!!

[MSM1992]

Hi gurus,

I followed the exact same procedure to update my ST2000DM001s firmware.

According to Seagates Download Finder (https://apps1.seagate.com/downloads/request.html) an update was recommended, but the provided program wouldn't flash it.

As the drive was supposed to be a 4 head model, I used the closed source SeaChest to apply the firmware file GRCC4H4H.LOD and guess what!
The drive stopped working and started spitting out errors on the serial interface:

Code:

Boot 0x40M
Servo !supported preamp ID 0000
Spin Up
FAIL  Servo Op=0100 Resp=0003
ResponseFrame EAC0 0000 0000 37C0 0008 0000 0000 0000 0D81 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrame E3C0 0000 0000 37C0 0008 0000 0000 0000 0D81 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrame E580 0000 0000 38C0 0008 0000 0000 0000 0D48 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrama E5C0 0000 0000 3840 0008 0000 0000 0000 0D65 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrame E600 0000 0000 3800 0008 0000 0000 0000 0D73 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrame E680 0000 0000 38C0 0008 0000 0000 0000 0D48 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrame E640 0000 0000 37C0 0008 0000 0000 0000 0D81 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrame E680 0000 0000 3800 0008 0000 0000 0000 0D73 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrame E680 0000 0000 3840 0008 0000 0000 0000 0D65 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrame E680 0000 0000 3840 0008 0000 0000 0000 0D65 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0
FAIL  Servo Op=0100 Resp=0003
ResponseFrame E680 0000 0000 37C0 0008 0000 0000 0000 0D81 0000 0000 0000 0000 0000 0000 0000 6B8A CFCF 25D2 8173 726C 0737 8A8F DB7A F676 D0


So it seems to me, that there is indeed an issue with a wrong firmware, even though Seagate recommends an update.

Fortunately, I do not need to recover any data from the drive, but I am curious, if the drive can be restored.
As aboveunder described, I am not able to enter the serial terminal. The error message doesn't even change, if the pcb is disconnected from the drive.

Does anybody have an idea how the terminal could be entered anyhow?