Seagate Barracuda 7200.10 - Unable To Load Overlay 01|000A

[drh]

Hi,

I have a 320GB Seagate Barracuda 7200.10 that has failed on me and I would very much like to try and recover the data on it. I have attached a picture of the drive which includes the model number, firmware version, etc.

I purchased a Nokia CA-42 cable which I was able to use to connect to the serial interface on the back of the drive and get into the diagnostic/firmware terminal. I was hoping someone could help me with commands to run to figure out what exactly is wrong and perhaps if there is a way I could fix it myself.

Here is what prints out when the drive is powered up:

Code:

Reset
4096k x 32 DRAM
GALAXY - 1_Disk    S-6D   09-22-06_15:48

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 15c4b.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>


Sending Ctrl+A shows:

Code:

T>Eng Rev = .0GB                                                               
Compat/Hardware = .6D1                                                         
GALAXY2D - 2_Disk    3.AAE  11-03-06_16:41 AAE,GX_2D_4H_S,3A                   
CERT Rev = .0B9                                                                 
NONE                                                                           
Mask Rom Rev = S-6D                                                             
Orig Code = AAE3A0 TONKA2_GX_3A0.0GB.0B9                                       
                                                                               
T>


Sending Ctrl+L shows:

Code:

T>GALAXY2D - 2_Disk    3.AAE  11-03-06_16:41 AAE,GX_2D_4H_S,3A                 
Built for GALAXY2D,PITKIN,Redback,TI1810 PreAmp,Agere7531 PreAmp,McKinleyDT,2DiR


As you can see I learned some commands from some basic internet research but I was hoping I could get some feedback before trying all sorts of weird things. The other two things I tried were resetting the G-list (T>i4,1,22) and clearing SMART area (1>N1) -- I know what SMART is, I think, but not G-list. Neither of these changed anything. The drive spins up and sounds fine, no weird noises.

I don't think I can afford a data recovery service, but I guess I would consider it. The most critical things are a password safe and some past tax returns/financial documents.

Thanks in advance for any help someone can provide.

Attachments

drive info

[northwind]

Well if you consider professional service, you should STOP sending commands through terminal, especially since you don't have a clue what commands you're sending in.
A one-letter command can kill your drive instantly with zero chances of recovery. Clearing G-List and SMART is not a very good idea and there is chance you have made things worse. If you value your data, stop now. If not, then, well... your data your choice.

After these warnings, I think your drive could still have a lot of chances of recovery, but i'm afraid there aren't many things you can do on your own. Does drive detect on BIOS? I highly doubt it after looking at the terminal output, but just in case.
If it does and you don't want to go to a pro and you accept risks of DIY (ie. loosing all data for ever), then you could try imaging using some non-windows utility like ddrescue and then go from there. Again (and AGAIN and AGAIN) this is very dangerous and you could end up with a non-recoverable drive (or much more expensive to recover).

If you want to go to a pro, i could look at it but i'm too far away, you can contact members jono-ats and thatdellguy they should be able to help.
At this point it shouldnt cost you an arm and a leg.

Whatever you choose, good luck.

[BlackST]

Clearing the G-list was a REALLY BAD idea , in any case I doubt it worked in this state.

Really sure you didn't play with other commands ?

[drh]

Thanks for the replies.

@northwind:
The drive is not detected by the BIOS, if I could get it to that state it would be great...

Whether or not I take it to a pro will depend on the cost. I honestly don't know what all I have on here that I would want back. My feeling is that if the fix involves opening the drive and changing heads or something like that, then the cost would be prohibitive. On the other hand if someone can swap the PCB or do something to the firmware it seems like that would be more affordable. It would be great if someone could walk me through some things to do on the terminal, to maybe figure out what the problem is exactly. I'd also be willing to pay something reasonable for that.

@BlackST:
When I ran:

Code:

T>i4,1,22


it always just returned a prompt like it didn't do anything, so maybe you are right that it didn't actually work. From looking back at all the things I've read the only other thing I would have run would have been:

Code:

T>F,,11


but I honestly can't remember if I did that or not. Mostly I was doing the other two commands because that is what I read most people having success with.

[drc]

This is a common problem, and no there is not anything you can do to fix it through terminal commands.

[drh]

If this is a common problem, hopefully there is a common solution? What's involved?

[drc]

Modifying the drive's firmware to prevent it from doing what is causing it to not init successfully

Possibly also replacing heads

[pcimage]

Modifying the drive's firmware to prevent it from doing what is causing it to not init successfully

Possibly also replacing heads

Exactly so.

[drh]

Does this error indicate something is definitely wrong with the SA of the HDD itself, or is it possible the firmware could be corrupt somehow -- meaning that swapping the PCB might actually work? Swapping the PCB is something I can do easily. Is this a waste of time? Any possible damage?

I have started to check around for prices on data recovery but I'd like to make sure I have exhausted any options of taking care of it myself.

[quasimodo]

Is this a waste of time?

Yes it is, it will not resolve the issue.

[pcimage]

Does this error indicate something is definitely wrong with the SA of the HDD itself, or is it possible the firmware could be corrupt somehow -- meaning that swapping the PCB might actually work? Swapping the PCB is something I can do easily. Is this a waste of time? Any possible damage?

I have started to check around for prices on data recovery but I'd like to make sure I have exhausted any options of taking care of it myself.

The firmware in question is not on the PCB, it is on the platters. So a PCB swap would be futile.

There is nothing you can do without the proper (expensive) tools and know how on this case I'm afraid.

Shouldnt be mega bucks for pro help on this one AT THIS STAGE, assuming it's not diy'd to death!