Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Help me with my Seagate st35000as hdd

May 12th, 2011, 6:34

I need help with what to do to get my data with my 500gb seagate HDD with burn't PCB [charcoaled 2 resistors and burned the trace the resistors were on] I already found a replacement from another 500gb with the same PCB number but I am stuck with what to do next do just take two resistors from my new PCB and try to rebuild the trace somehow or do I transfer the romchip from buren't PCB to the new one but I dont know which is it on my PCB here a scan of it

Image

Re: Help me with my Seagate st35000as hdd

May 12th, 2011, 8:31

Hi,

you have to transfer ROM chip from patient to donor PCB.

ROM chip is a 8-pin chip, it usually starts with "25"....

Simone

Re: Help me with my Seagate st35000as hdd

May 13th, 2011, 22:14

sorry but I dont think seagte still uses the 8pin chip that is why I am asking here to anyone knowledgeable here to point it out for me there in the picture

Re: Help me with my Seagate st35000as hdd

May 14th, 2011, 2:54

There u go.....
Attachments
Mod_5639734.jpg

Re: Help me with my Seagate st35000as hdd

May 15th, 2011, 13:13

The damage is consistent with an overvoltage on the +5V supply.

You could replace the burnt inductors (?) with wire links and remove the 5V TVS diode below the 8-pin flash memory IC. The diode will probably be shorted.

Before powering up the drive, check your power source.

My HDD IC database should help you identify the components:
http://www.users.on.net/~fzabkar/HDD/HDD_ICs.txt
http://www.users.on.net/~fzabkar/HDD/TVS_diodes.txt

Re: Help me with my Seagate st35000as hdd

May 15th, 2011, 20:57

Since he already has a suitable substitute, the safer thing to do (assuming he, or someone he knows has SMT repair skills) is to replace the EEPROM.

In my opinion, advising someone to bypass safety and noise-suppression devices when the reason for the failure is uncertain, is unnecessarily risky if not irresponsible . . . because it could result in cascading failure instead of data recovery.

In some cases, it might work. But why take the chance?
Post a reply