ST2000DM001

[sempre]

HELLO!

What is the likely problem?

Boot 0x40M
Spin Up
FAIL Servo Op=0100 Resp=0007
ResponseFrame 0100 0055 03B3 2A80 0008 0000 0000 0000 105D 0000 0000 0000 0000 0000 0000 0000 25DC 7E1E FFFF 2000 211B 0000 0000 EB4E 0000 EB4E 0000 2443 0000 0020 0020 000B 0010
FAIL Servo Op=0100 Resp=0007
ResponseFrame 0040 0056 03B3 2A80 0008 0000 0000 0000 105D 0000 0000 0000 0000 0000 0000 0000 25DC 7E1E FFFF 2000 211B 0000 0000 EB4E 0000 EB4E 0000 2443 0000 0020 0020 0005 0000
FAIL Servo Op=0100 Resp=0007
ResponseFrame 00C0 0056 03B3 2A40 0008 0000 0000 0000 106B 0000 0000 0000 0000 0000 0000 0000 25DC 7E1E FFFF 2000 211B 0000 0000 EB4E 0000 EB4E 0000 2443 0000 0020 0020 0005 0000
FAIL Servo Op=0100 Resp=0007
ResponseFrame 00C0 0056 03B3 2A80 0008 0000 0000 0000 105D 0000 0000 0000 0000 0000 0000 0000 25DC 7E1E FFFF 2000 211B 0000 0000 EB4E 0000 EB4E 0000 2443 0000 0020 0020 0005 0000
FAIL Servo Op=0100 Resp=0007
ResponseFrame 00C0 0056 03B3 2A80 0008 0000 0000 0000 105D 0000 0000 0000 0000 0000 0000 0000 25DC 7E1E FFFF 2000 211B 0000 0000 EB4E 0000 EB4E 0000 2443 0000 0020 0020 0005 0000
FAIL Servo Op=0100 Resp=0007
ResponseFrame 00C0 0056 03B3 2A80 0008 0000 0000 0000 105D 0000 0000 0000 0000 0000 0000 0000 25DC 7E1E FFFF 2000 211B 0000 0000 EB4E 0000 EB4E 0000 2443 0000 0020 0020 000B 0000
RECOV Servo Op=0100 Resp=0005[0x000065B4][0x00006625][0x00006625]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddWWWMMMMMM
RECOV Servo Op=0155 Resp=0005S
RECOV Servo Op=0055 Resp=0005xxxxZWZWZWZWZWZWZWZW

[data-medics]

Looks like bad heads, and someone shorting the read channel to me.

[hpw333]

yes this is bad heads

[galaxy]

THIS IS BAD HEADS ON DM SERIES

[MindMergepk]

have you verified the ROM, is it native ?
If rom is native, definitely heads or media damage too.

[sempre]

have you verified the ROM, is it native ?
If rom is native, definitely heads or media damage too.

Hello!
Thanks all replys!
I already changed the heads and twice with the same log. I think it's the media damage.

[Doomer]

Bad blocks in SA on H0

[Amarbir[CDR-Labs]]

have you verified the ROM, is it native ?
If rom is native, definitely heads or media damage too.

Hello!
Thanks all replys!
I already changed the heads and twice with the same log. I think it's the media damage.

Return heads to original donor drive and see if they still read ...

Well,
To My Firmware Guru ,Well This Approach Should Not Be Used Initially Later On You Can Try It But Not Initially Here is The Procedure For These POS Drives From Seagate When They Come For Head Replacement .

Lets Take a Example Of The ST2000DM001 Drive Being Talked Here ....

1 : Before You Quote Your Client You Should be aware this DM series drives can take 3 HSA Donors Too,Discuss this with your clients ..
2 : Take Some Money For CRI "Clean Room Inspection " .Once That Money is Received Please Open The Drive In The Clean Room And Take The Native Heads Out .Inspect The Heads At 20x And 40x Magnifications And If There is Metal Debris In Any Of The Heads You Will Come To Know Right Away Which Platter is Scored / Scratched .

3 : Kindly Note That If You Inspect Head 0 And Find Nothing ,But Head 1 Has Very Less Debris But Head 2 Has Quite a Lot of It Then There Are Chances That Head 1 Is OK And The Debris There is From The Bottom Head of The Top Platter which is head 2 in our example .

4 : Then comes the fun part ,You have to know how to physically cut heads ,work with platters .Which includes advanced techniques like totally dismantling platters and putting them back without having a issue of servo misalignment ,Now there are ways to overcome that too .

PS : I Hate These POS Drives

[sempre]

have you verified the ROM, is it native ?
If rom is native, definitely heads or media damage too.

Hello!
Thanks all replys!
I already changed the heads and twice with the same log. I think it's the media damage.

Return heads to original donor drive and see if they still read ...

Well,
To My Firmware Guru ,Well This Approach Should Not Be Used Initially Later On You Can Try It But Not Initially Here is The Procedure For These POS Drives From Seagate When They Come For Head Replacement .

Lets Take a Example Of The ST2000DM001 Drive Being Talked Here ....

1 : Before You Quote Your Client You Should be aware this DM series drives can take 3 HSA Donors Too,Discuss this with your clients ..
2 : Take Some Money For CRI "Clean Room Inspection " .Once That Money is Received Please Open The Drive In The Clean Room And Take The Native Heads Out .Inspect The Heads At 20x And 40x Magnifications And If There is Metal Debris In Any Of The Heads You Will Come To Know Right Away Which Platter is Scored / Scratched .

3 : Kindly Note That If You Inspect Head 0 And Find Nothing ,But Head 1 Has Very Less Debris But Head 2 Has Quite a Lot of It Then There Are Chances That Head 1 Is OK And The Debris There is From The Bottom Head of The Top Platter which is head 2 in our example .

4 : Then comes the fun part ,You have to know how to physically cut heads ,work with platters .Which includes advanced techniques like totally dismantling platters and putting them back without having a issue of servo misalignment ,Now there are ways to overcome that too .

PS : I Hate These POS Drives

[sempre]

have you verified the ROM, is it native ?
If rom is native, definitely heads or media damage too.

Hello!
Thanks all replys!
I already changed the heads and twice with the same log. I think it's the media damage.

Return heads to original donor drive and see if they still read ...

Well,
To My Firmware Guru ,Well This Approach Should Not Be Used Initially Later On You Can Try It But Not Initially Here is The Procedure For These POS Drives From Seagate When They Come For Head Replacement .

Lets Take a Example Of The ST2000DM001 Drive Being Talked Here ....

1 : Before You Quote Your Client You Should be aware this DM series drives can take 3 HSA Donors Too,Discuss this with your clients ..
2 : Take Some Money For CRI "Clean Room Inspection " .Once That Money is Received Please Open The Drive In The Clean Room And Take The Native Heads Out .Inspect The Heads At 20x And 40x Magnifications And If There is Metal Debris In Any Of The Heads You Will Come To Know Right Away Which Platter is Scored / Scratched .

3 : Kindly Note That If You Inspect Head 0 And Find Nothing ,But Head 1 Has Very Less Debris But Head 2 Has Quite a Lot of It Then There Are Chances That Head 1 Is OK And The Debris There is From The Bottom Head of The Top Platter which is head 2 in our example .

4 : Then comes the fun part ,You have to know how to physically cut heads ,work with platters .Which includes advanced techniques like totally dismantling platters and putting them back without having a issue of servo misalignment ,Now there are ways to overcome that too .

PS : I Hate These POS Drives

[merc88]

really sorry to ask this here but I have a similar model HDD which my DR company says they have managed to image. The resulting raw data however is jumbled up and messed. They said they are unable to read the data properly. Is there any recommendations anyone can make? I have been banned previously for asking regarding this issue.

I am not a tech guy and forgive me for asking so many questions as I want to be able understand what's going on. I just want to be able to recover my data..

[data-medics]

2 : Take Some Money For CRI "Clean Room Inspection " .Once That Money is Received Please Open The Drive In The Clean Room And Take The Native Heads Out .Inspect The Heads At 20x And

You charge for the inspection? I do that free as part of the evaluation. But, I don't usually remove and inspect the heads under a microscope until I've got an approved quote. I normally just check for obvious mangled heads, missing sliders, scratched top platter, dirty air filter, etc. Then once they approve the quote, I often inspect the heads under a microscope to determine if cleaning is likely to help and know how likely we are to need multiple heads donors.

A couple times I did have to call a customer back and let them know that the odds of success were lower than we originally anticipated, but that's only happened a couple times.

[pepe]

have you checked if SN is correct in SAP?