Seagate ST1000DM003 fw: CC44

[mike-s]

A friend of mine came to me asking that I try and do what I can to recover the data from his hard drive. Fortunately he has backups, they aren't current, but he won't have a total loss if it fails. I'm not interested in making the drive work longer than it will take to recover whatever I can from it before it is assigned door-stop duty.

The drive appears to spin up normally, but is simply invisible on the SATA port. I've successfully connected to the TTL Serial using an arduino for conversion. I am now trying to figure out exactly what my next course of action should be. Although I have had experience with unbricking the 7200.10 era hardware, so don't feel totally out of my depth. I would rather play it safe and refer to people whom have a little more experience in case there is something simple I can do to get this drive functional enough to pull the data from the drive before sending it to the great raid array in the sky.

Details:
Seagate ST1000DM003
Firmware: CC44
PCB Rev: 100687658 REV C.

Here's what I've gotten just trying to spin down/up the drive.

Code:

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
RECOV Servo Op=0600 Resp=0005
RECOV Servo Op=0600 Resp=0005
(P) SATA Reset

ASCII Diag mode

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 10.575 secs
F3 2>U

LED:000000EE FAddr:003E01FC
Rst 0x40M
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC
LED:000000EE FAddr:003E01FC


I've gotten some other logs, but to avoid splattering my logs all over the page and making it unreadable, I've attached them to this in a text file. I'll noted there appears to be plenty of drive slips in there, but I'm hoping that they are simply a sign the drive needs to be replaced rather than a cause for the drive to have failed like this.

Attachments

ST1000DM003-diag.txt

(65.78 KiB) Downloaded 981 times

[mike-s]

Bump:
So, any clues at all, anyone, please.

[mike-s]

It's looking promising,

Code:

F3 2>Z

Spin Down Complete
Elapsed Time 10.582 secs
F3 2>U

Spin Up Complete
Elapsed Time 3.493 secs
F3 2>


It now powers up without those errors, now to see IF i can get it detected in anusb enclosure so I can pull the data I need from it.

[mike-s]

Ok, I can get to the drive. Thank you very much. It looks like another case of revenge of the firmware.

If you ever come to Australia, my friend will happily buy you a drink or three.

[mike-s]

All relevant data has been copied off to a brand new external/usb drive, and as the failed drive has/had some medical records things on there I am currently 0-filling the drive before handing it back to my workmate, possibly minus the logic board to make sure it never can be used again, for better or worse.

As to Seagate, I am really really surprised that their newer generation of drives have had this much of a problem. This drive was bought in a Dell, so little say was had (or known) about potential pitfalls of using the drive. I've also got a couple of 3Tb drives mirrored in a NAS performing as a "backup of a backup of a backup", and thusly spending 99.9% of their time shutdown, I'll replace them over the next few months as I am able, eventually. And I agree about the Hitachi drives, I've got about five of them in my primary NAS and they have outlasted almost everything else in there.

And lastly, thankyou, thankyou, thankyou.
I rarely use emoticons, but I think today calls for them.

P.s. is there any writeup you or anyone else knows of explaining in more layman terms exactly what the problems that these DM drives have? I'd be really interested to have a read to understand it a bit more thoroughly.

[mikail13]

It's looking promising,

Code:

F3 2>Z

Spin Down Complete
Elapsed Time 10.582 secs
F3 2>U

Spin Up Complete
Elapsed Time 3.493 secs
F3 2>


It now powers up without those errors, now to see IF i can get it detected in anusb enclosure so I can pull the data I need from it.

You must wait hitting U until you are sure that motor fully stops.
this is because LED error.

[mike-s]

Ah, well that was a catastrophic culmination of bad choices. Thanks for the enlightenment.

[drHDD]

P.s. is there any writeup you or anyone else knows of explaining in more layman terms exactly what the problems that these DM drives have? I'd be really interested to have a read to understand it a bit more thoroughly.

It's simple. Bad quality of platters/head + bad firmware design.

It is not so simple. Seagate used in DM new technologies and of course sometimes new technologies works not so well like you expect.