@pikus_09, all the pros are telling you what you don't want to hear. If you wish to eliminate the slim possibility of a PCB failure, then try transferring your ROM to a replacement PCB.

Best of luck.

_________________
A backup a day keeps DR away.

Ok, Franc, but analyzing batch ROM disagree entries is damaged portion adaptyw, so I do not think anything will transfer ROM.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

Was a "forced update" not suggested by Seagate by a chance and done by you?

because I have such a rule amendment if it goes out, always update to be downloaded to the latest version, and so it did in this case. Everything was successful, but equally 8days, hard disk ceased to be visible through the BIOS, system and terminal throwing Fail SERVO OP = 100 Resp = 0007.
And pretending to load ROM sail caught as messed up this modification proposed by the seagate. Sorry for my english.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

@pikus_09, your ROM is OK. If it were not, then the drive wouldn't spin. Instead you would see a checksum error in the terminal log, as in the following thread ...

viewtopic.php?f=1&t=29164

Anyway, your ROM consists of two similar halves, and each half consists of several sections, either code or adaptives (RAP, CAP, SAP). These adaptives are unique to your drive. For example, the CAP contains the drive's serial number.

Here is a comparison of the contents of each section:


There are some differences, but these appear to be normal. In fact the differences in at least two of the code sections are due to the CC4H firmware update. ISTM that firmware updates are written to the second half of the ROM.

Barracuda (1TB/disk platform) Firmware Update:
http://knowledge.seagate.com/articles/e ... Q/223651en
http://www.seagate.com/staticfiles/supp ... GRCC4H.iso

Header from update (GRCC4H6H.LOD, offset 0x200)

_________________
A backup a day keeps DR away.

Welcome franc, now for example. Plugged this drive and is a slight improvement, ie, the drive ejects FaiL servo op = 0100 resp = 0007 each time you click, and so ten times.
Previously, the drive clicked 11 times and log start throwing Fail servo op = 0100 resp = 0003, then fail servo Op = 0100 resp = 0003 Terminal obviously locked. sorry for my English.
Ps. So you're saying Franc that my ROM is ok. Okay, I was hoping that, however, is freaked out.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

Hello again, but it turned out that the ROM is good, and
PCB is damaged, Bad MCU.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

Seen this message a thousand times, and it was always bad read/write heads or media damage. Stop wasting time playing with the PCB, you're just making it worse.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company

Ok, So at the end, I did the test. He dialed the PCB from the disk and strapped into the terminal. And what I saw !? FAIL Servo OP = 0100 RESP = 0003 10 times.
Afterward, the strapping another PCB from another terminal Segate worked, so here suggests faulty PCB (BAD MCU).
So I personally do not think that in my case fell heads.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

Hello
I give you the new .I changed the drive head and I can recover data from my client.


good luck

_________________
Sorry from my English

For me, the PCB is Bad, Bad MCU, there are different cases of this error, some actually head fell another PCB.

_________________
Hello everyone, sorry for my poor english, because i using google translator.

How did you manage a successful head swap. We have burnt through many donors with Seagate DM series drives. Is there something I'm missing?

Assuming that there is nothing wrong with your process of swapping the head stack and that the head stack is fully compatible, you will now need to adapt the patient ROM to the new head set adaptives using something like Pc3k or MRTLab tools. There is a video posted here on the forum on how to do so with MrtLab tools. The idea is to make the original ROM have the adatives os the donor heads. This is needed for F3 Arch seagates.

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

Hello i'm live same problem

Before this error hdd power down and power up possibly 20 times and stopped last time

I can try this post suggestions but everything is normal/fine

I have another bad hdd same p/n etc.

Try board change but same status for clicks

This is showing problem has mechanical possibly plates/motor jam

And last chance open drive and see problem

Upper head break and jamming between head arm and upper plate

This case need for me a head change operation following days

hdd is died with suicide

picture is attached

Wow, usually google translate can at least make out one or two intelligible sentences on a post that long. But I can't understand anything he's saying.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company

OK, I understood that part.

_________________
Data Medics - Hard Drive, SSD, and RAID Data Recovery Service Company

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

I didnt know that you need to change ROM when you change the HSA? So you say that every HSA is unique?