Was imaging this drive slowly through a lot of bad sectors, only really worked in reverse and in PIO mode but was getting there. Drive stopped and started to make beeping noise from voice coil and wouldnt go to ready. Thought it was heads but have disconnected PCB from drive and PCB also wont go ready on its own or with just spindle isolated

Terminal with PCB attached
ExecuteSpinRequest

FAIL Op=0100 Resp=0007
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
No HOST FIS-ReadyStatusFlags 2002B001
Rst 0x20M
Servo Processor Is Reset.


Terminal with PCB not attached

ExecuteSpinRequest

FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
No HOST FIS-ReadyStatusFlags 2002B001

This type of error is common when motor is seized (or stiction). Does the drive spin up?

_________________
http://www.northwind.gr
SandForce SSD Recovery
Ransomware Reverse Engineering - NoMoreRansom! partners

ye, spins up fine. Head moved to platter then off back to ramps, voice coil beeps then arm moves back onto platter, tries that a few times then gives up. 13 beeps then spins down.

Isolated spindle, span down, reconnected and span up again and got this

Rst 0x20M
Servo Processor Is Reset.

RW: Disc Ctlr Initialization Completed.


ExecuteSpinRequest

FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
No HOST FIS-ReadyStatusFlags 2002B001
ASCII Diag mode

F3 T>/2

F3 2>
ASCII Diag mode

F3 T>/2

F3 2>Z

Spin Down Complete
Elapsed Time 0.045 msecs
F3 2>U


ExecuteSpinRequest

FAIL Op=0100 Resp=0007
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
FAIL Op=0100 Resp=0003
DiagError 00006008
Spin Error
Elapsed Time 22.022 secs
R/W Status 2 R/W Error 84150180

I am seeing exactly the same symptoms on a ST2000DM001. The drive is spinning up and I also get the PCB busy on its own or with the spindle isolated. How did you manage to get it out of busy? Apologies for the newbie question.

i have same problem with drive
st1000dm003 1Tb
no more recognizable from bios
no strange sound, motor spin regualrly
if connect via serial i receive the same failure

Spin Up
FAIL Servo Op=0100 Resp=0003
ResponseFrame 0480 0000 0000 3240 0008 0000 0000 0000 0EB4 0000 0000 0000 0000
0000 0000 0000 BFFA 8ECB 8800 880D 47CE 012A 11CE EBEE B3F5 53BF 0000 007F 0000
0000 001D 0004 0000


what could i do?
thanks

It's bad heads, most likely with scratches on platters. Data recovery is usually possible but not DIY.

i have zhe same problem with my disk. i guess maybe zhe pcB is wrong

I have the same problem :FAIL Servo Op=0100 Resp=0003
The head go from track o to last track, it tries two small access, then come back and repeat 12 times or similar.
At the end I cannot send any command to HDU via serial port., and the HDU seems stucked.

I found on internet many site where is described the BUSY bug.
Someone suggest to mask head connect, someone suggest to mask the mot contact pin.
The SERVO FAIL appear if I mask the motor pin.

I suspect that there is a problem on the board, in the head step motor controller.
What do you think about ?

FAIL Servo Op=0100 Resp=0003 IS NOT the BSY bug or the LBA0 problem.

Do not try to fix this issue using the "internet fix".

If data is needed from the drive, the better advice would be to take the drive to a data recovery center (not a PC repair shop) near you. This problem it's not a thing that you can fix with terminal commands.

Best regards and wishing you luck.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Nothing to do with PCB.

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

I had two of these fail simultaneously (both members of a RAID 1 array) They both became unrecognizable by the RAID controller and the BIOS. I have a few good drives of the same model. On a good drive, if you place a card between the voicecoil/head connectors and the PCB you get the following errors:

Boot 0x40M
Spin Up
FAIL Servo Op=0100 Resp=0003
0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000
ResponseFrame 1F40 0000 0000 7FC0 0008 0000 0000 0000 FBE7 0000 0000 0000 0000 0000 0000 0000 722F 31A5 0
FAIL Servo Op=0100 Resp=0003
0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000
ResponseFrame 2580 0000 0000 7FC0 0008 0000 0000 0000 FBE7 0000 0000 0000 0000 0000 0000 0000 722F 31A5 0

If you remove the card and allow the PCB to connect to the head/voicecoil connections I see this:

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
TCC:001E

(P) SATA Reset


In neither case does my CTRL-Z give me a prompt, but I think that is because my 3.3V USB serial adapter which I modified using the schematic here: http://www.mobileread.com/forums/showth ... ?p=1897643
is not sending the right voltage on TX pin, so the drive never sees the CTRL-Z.

I have been going on the assumption that these drives have the firmware BSY bug, because the odds of simultaneous disk failure are so remote. These drives did not get bumped or jarred in any way, so mechanical failure would have had to happen for other reasons. Two failures at the exact same time is something I have not come across before, but I have seen abysmal failure rates on some Seagate 1TB drives over the last 4 years or so. As soon as I work out the TX problem I'll have good and bad drives to work with. I hope it turns out to be a simple firmware issue.

thesmos,


Easily.
Kick. Vibration. From 0.2 to 1G operation time.
Scratches - dead head.
Event impact or vibration may be long, 1-2 months ago.

I would add bad mounting on case and some other. And it is not always Sunday !

What would be the chance for the firmware bug to affect the 2 drives at the same time, assuming it was a firmware bug to start with ?

It would be way more likely that a power surge, power supply or heat or vibration on the same case could damage the 2 drives, rather than a specific event on firmware when a value on a firmware table reach a specific number to lock 2 drives exactly at the same time.

Believe me or not, THIS IS NOT the bsy bug neither the LBA0 issue. If it were i would be glad to fix it for you even by remote (teamviewer). I wouldn't even need the F3 arch PC-3000 UDMA utility to fix it. BUT in your case IT'S NOT a typical firmware bug.

On your case Heads don't find servo, don't read at all. So there is values on the firmware tables locking the drive due to the firmware bug because those values aren't read at all to start with.

I would vote for bad heads, bad surface, or bad pre-amp. Drive have to be opened on a clean room by a professional to check it out. This, of course, assuming you want your data back.

Best regards and wishing good luck.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

Dear Friend kpeddie

Your drive is recoverable and yeh ur drive head is weak and without head replcement chance is 50% 50% but if the drive dont spindown the chance is 99%
in this F3 tipical for 500GB DM001/2/3/4 and also for 1tb or 2tb drives F3 remember that if the drive is not spindown and complet the init process and then show this error in terminal with bussy or any of other 6 to 7 defrent errors symptoms then i gurented i can recover it without head swap but if the drive is spindown then without head swap chances is 50% 50% this is my own work experiance i recover this F3 lots of cases and doing rightnow.
rightnow i am working on 3 2tb and 1 1tb F3 drives and many cases from 500GB F3 DM Series bcoz here mostly sold 500gb drive in my area.
your drive it not DIY but others are fixable wich one is not spindown.
And One Thing That Seagate Is Never Cry (Clicking Sound) Without Head problem. but its mostly for new series 7200.11/12/F3 but this is not suit for other older drives but i mostly seen that seagate clicking when problem is not related to firmware but physical.

sorry for my bad english.

yours friend
jignesh pankhania

Hi everybody.
Im asking about some help to diagnose my faulty and full of important data Seagate ST2000DM001.
This is my log:

Boot 0x40M
Spin Up
FAIL Servo Op=0100 Resp=0003
ResponseFrame F040 00A4 06CC 4180 0008 0000 0000 0000 0B47 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0010
FAIL Servo Op=0100 Resp=0003
ResponseFrame E900 0070 06CC 41C0 0008 0000 0000 0000 0B38 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E840 0070 06CC 4180 0008 0000 0000 0000 0B47 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E7C0 0070 06CC 4140 0008 0000 0000 0000 0B56 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E780 0070 06CC 41C0 0008 0000 0000 0000 0B38 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E740 0070 06CC 4100 0008 0000 0000 0000 0B66 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E700 0071 06CC 40C0 0008 0000 0000 0000 0B75 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E6C0 0071 06CC 4100 0008 0000 0000 0000 0B66 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E680 0071 06CC 4080 0008 0000 0000 0000 0B84 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0017 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E680 0071 06CC 4100 0008 0000 0000 0000 0B66 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0000
FAIL Servo Op=0100 Resp=0003
ResponseFrame E600 0071 06CC 40C0 0008 0000 0000 0000 0B75 0000 0000 0000 0000
0000 0000 0000 5AB3 0AA9 0C81 6E48 0AC7 E600 A57F 9CE8 FF6C 7255 0000 007F 0000
0000 0016 0004 0000

Then the motor stops.
Noway to send any command (Bricked?).
Thanks.

Hi
"Tomset" is 100% right.
Scratch on plates or head is damaged.
From Grenada 7200.14 Series, its very hard to recover data if the plates have just a little (minor) Scratch.


Regards
Waqas Ali

Finally Seagate HD is a crap, its my third died Seagate HD.
i'll never buy this s****.
Thanks for answer.
I m going to cry in my bed for data lost.

Head Problem