I am in need of help with a 7200.10 drive.

The drive was in a flood and burned the pcb at the motor controller.
I opened the drive and it is clean and dry.
I am unable to power the original pcb to retrieve any info.

The donor is the same fw version, with the flash transferred from the original pcb.

logs from the donor pcb on the patient drive:

Buzz HM SFI
!
(P)SATA Reset
DiskAccess ReadSector EC=47 at ffffffff.00.0002
DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Retrys
DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Retrys
DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Retrys
DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Retrys
DiskAccess ReadSector EC=47 at ffffffff.00.0002

Read Ver Failure!
DiskAccess ReadSector EC=47 at ffffffff.00.022b
Failed sys sect. write! Nwt Er 00 RdWr 15db7.00.022b
DiskAccess ReadSector EC=47 at ffffffff.00.0080
DiskAccess ReadSector EC=47 at ffffffff.00.0080
Unable To Load Overlay 01|000A

T>

Hi there !

The drive is a 7200.10 so as long as the ROM version match the SA version on the platters there isn't even the need for a ROM swap, as those drives don't store unique adaptives on ROM. Of course that it wouldn't make any difference on this case, just a note to take in account for the future. 7200.10 drives don't need ROM swap as long as ROM version on PCB is the same as SA version.

Ok, now for the log.

The drive isn't reading any firmware at all.

Unable To Load Overlay 01|000A

This means that the drive can't even read the app code to start up (from the the platters). My guess is either the heads are damaged or the platters have damage on the SA location.

Did you swap heads ?
Did you try a loader file ?

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

If you have a loader for this drive on your database (same FW version) you might want to force the drive to F> and load the app code and the rest of the firmware components from the loader just to see if the drive can start and if you can gain access to the data with DE.

Also you can try to do a head test.

If the pre-amp or heads are damaged that would be consistent with the burned pcb. You will not be able to do anything without a head swap if that is the case.

If the heads are still working and only a portion of the SA is damaged (on this case the app code) you can write it back to the drive assuming you have a copy of it on your firmware database.

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

Also read page 48 of the latest english version of the UDMA manual.
Multiple 43 and 47 errors and the format of your log looks like either lost adaptives or MORE LIKELY contaminated/damaged heads.

Again start the drive with a loader and check if you can read with head 0.

If you have a loader file for the version of firmware present on the drive i can help you out by teamviewer to do so (load from loader) with PC3000 UDMA and then test to see if drive reads at all with head 0.

But of course i can't change heads by teamviewer.

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

Hello,
Load ATA module into RAM, then it will give you ready status,
after that open pc3000 data extractor then use its active utility options, to access hdd , try this

Regards
Waqas Ali
www.sediv.net

Agree.
I would drop the drive to F and start APP code from loader as well. Then load ATA and use DE to try to get to data.
This will NOT WORK if heads/pre-amp are gone.

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

Hi again !
Please let us know if the drive cloned to the end and if you figured out what head was causing problems with the head map on DE.

As reference, of course that i didn't clear understood the log the first time i posted my reply.

As the OP drive was at T> level even with the ATA overlay errors that would mean that at least the adaptives and the APP was loaded from platter. If there were a problem loading App the drive would have dropped to F>

the more i test the more i understand and now i can clear vizualize all the initialization process of the barracuda type of drives.

Loading ATA from loader with pc3k and accessing the drive by the active utility on DE as suggested on this thread was of course the correct procedure.

On this particular case removing the heads and placing them back to the drive allow for the ATA to be loaded from the drive without error and for DE to slowly clone it.

I'm leaving this here for reference.

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

Well,
Alas they update thier manuals spildit they are dated the u5 family is recently updates though

_________________
Regards
Amarbir S Dhillon , Chandigarh Data Recovery Labs [India]
Logical,Semi Physical And Physical Data Recovery
Website-> http://www.chandigarhdatarecovery.com