Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

ST3000DM001 Firmware Brick?

October 20th, 2016, 6:05

Hi there,

atm I have 3 Seagate ST3000DM001 Drives.
1 PCB burned -> repaired and acces to the Data
2 Power on, click 2-10 times and power off

Seagate Barracuda ST3000DM001
PCB: 100664987 Rev B

The Terminal shows me this one
CTRL + Z will not work. If I push it... nothing happen.

Code:
Boot 0x40M
Spin Up
FAIL  Servo Op=0100 Resp=0007
ResponseFrame 0A80 004F 03B4 3580 0008 0000 0000 0000 0DFF 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 2247 0000 0020 001B 0007 0010
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 0280 0051 03B4 35C0 0008 0000 0000 0000 0DF1 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 0240 0051 03B4 35C0 0008 0000 0000 0000 0DF1 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 0240 0052 03B4 35C0 0008 0000 0000 0000 0DF1 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 0200 0052 03B4 35C0 0008 0000 0000 0000 0DF1 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 0200 0052 03B4 3600 0008 0000 0000 0000 0DE3 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 01C0 0052 03B4 3600 0008 0000 0000 0000 0DE3 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 0180 0052 03B4 3600 0008 0000 0000 0000 0DE3 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 0180 0053 03B4 3580 0008 0000 0000 0000 0DFF 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 0180 0053 03B4 35C0 0008 0000 0000 0000 0DF1 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000
FAIL  Servo Op=0100 Resp=0003
ResponseFrame 0180 0053 03B4 35C0 0008 0000 0000 0000 0DF1 0000 0000 0000 0000 0000 0000 0000 0CCF FB48 FFFF 2000 23A7 0000 0000 4448 0000 4448 0000 007F 0000 0020 001B 0004 0000


Is it a Firmwarebrick or is it something else?!

best regards
Fabian

Re: ST3000DM001 Firmware Brick?

October 20th, 2016, 6:37

This is head problem.

Re: ST3000DM001 Firmware Brick?

October 20th, 2016, 6:37

DM series and Fail Servo error. Probably heads or media damage.

Re: ST3000DM001 Firmware Brick?

October 20th, 2016, 6:45

Ok, thanks for the fast replys. It sounds not good.

For better understanding for me.
What does Servo error exacly means?

Headchange is only possible in a cleanroom as i know. What is todo after the head replacement, do I need to calibrate it?
How can I identify that the heads bad and not the media damaged?

Fabian

Re: ST3000DM001 Firmware Brick?

October 21st, 2016, 3:05

it is not DIY anymore. Without experience and tools you will kill it.

Re: ST3000DM001 Firmware Brick?

October 21st, 2016, 9:20

pepe wrote:it is not DIY anymore. Without experience and tools you will kill it.


theres no important Data on it.
So ur awnser is not that what i want.

Re: ST3000DM001 Firmware Brick?

October 21st, 2016, 9:46

Then bin it...
Let me guess, this was the 2nd most unsympatehtic answer you wanted.

why would you invest in donors, and time if the data is not important? please....

Re: ST3000DM001 Firmware Brick?

October 21st, 2016, 10:31

To learn how does it work.

atm i've round about 200-300 damaged drives to learn.
if u dont believe it ill send u a pic.

Re: ST3000DM001 Firmware Brick?

October 21st, 2016, 12:27

I think you might find yourself better served at http://www.hddoracle.com/index.php where they are more in tune with what you are trying to do.

How do you know if it is heads or media damage? Sometimes it comes down to experience...after you work with a few thousand drives of the same model, you get a good feel for it. But, a lot of the time, you just change heads and see if you can get it to work. If the patient heads don't work in the donor, you know the heads are bad. If the donor heads don't work in the patient, it could be incompatible heads and/or media damage.

Re: ST3000DM001 Firmware Brick?

October 21st, 2016, 16:40

If the patient heads don't work in the donor

it might be incompatible as well...

Fabianf: i do believe you, it's not the point.
You got pretty much the answer to your question, the rest is up to your skills and intuition. This is not a data recovery training course here, don't expect anybody to hold your hand throughout the learning curve.
All i say is that this drive is not what you should start with. 'oh no, i said too much... ' :)

Re: ST3000DM001 Firmware Brick?

October 21st, 2016, 19:22

fabianf wrote:For better understanding for me.
What does Servo error exacly means?


Servo is special tracking information written on each platter surface that is used to calibrate and align the read/write heads over the tracks and to know where on the platter it's positioned. You can learn a lot about it by just using google, or by reading old patent information from WD, Seagate, Maxtor, etc. that explains in a lot more detail.

Suffice to say, if the drive can't read the servo it can't track its location. Therefore it can't retrieve any sectors. Ergo, bad heads or severe media damage (or most often a combination of a bit of both). If the media damage is heavily affecting the service area (negative tracks that store firmware) then it may just be unrecoverable.

Normal first step is to visually inspect platters in a clean room to see if there are visible scratches. Then inspect heads under a microscope to see if they are bent, twisted, detached sliders, etc. to determine the likelihood of severe media damage. If all looks relatively good, then it's worth attempting to head swap it.
Post a reply