Accidentally Damaged My PCB on Seagate Momentus 7200.2 320GB

[icetnet]

The accident cut 4 traces that connect to the integrated circuit in the center of the PCB, otherwise the drive was working great. I took it out of the notebook to put in my other drive...

It is a Seagate Momentus 7200.3 320GB (7200RPM, 16M cache) drive with a 100513573 Rev B board
SN: 5TJ0AFGH
ST9320421AS
PN: 9GE144-500
FW: SD13
+ 5V 0.62A
made on Date: 09232
at Site: WU

I have a donor drive with the exact same specs except for the "made on Date".

I swapped the PCB and the drive now spins up, but, as expected does not seek or access the partitions.

Here is the log data from plugging in the drive with the donor PCB.

Code:

kernel: [  127.390203] usb 2-2: new high speed USB device using ehci_hcd and address 5                     
kernel: [  127.543154] usb 2-2: configuration #1 chosen from 1 choice                                       
kernel: [  127.549876] scsi5 : SCSI emulation for USB Mass Storage devices                                 
kernel: [  132.554203] scsi 5:0:0:0: Direct-Access     ST932042         5TJ0DD8P      PQ: 0 ANSI: 2 CCS     
kernel: [  132.555122] sd 5:0:0:0: Attached scsi generic sg2 type 0                                         
kernel: [  132.556680] sd 5:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).                 
kernel: [  132.558016] sd 5:0:0:0: [sdb] Using 0xffffffff as device size                                   
kernel: [  132.558030] sd 5:0:0:0: [sdb] 4294967296 512-byte logical blocks: (2.19 TB/2.00 TiB)             
kernel: [  132.560450] sd 5:0:0:0: [sdb] Write Protect is off                                               
kernel: [  132.562772] sd 5:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).                 
kernel: [  132.564695] sd 5:0:0:0: [sdb] Using 0xffffffff as device size                                   
kernel: [  132.565932]  sdb:                                                                               
kernel: [  132.575164] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.575173] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.575182] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.575192] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.584415] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.584424] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.584434] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.584444] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.592569] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.592577] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.592586] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.592596] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.602591] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.602600] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.602610] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.602620] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.611783] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.611792] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.611801] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.611811] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.620334] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.620342] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.620351] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.620361] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.630571] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.630579] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.630591] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.630603] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.641550] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.641559] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.641568] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.641578] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.652719] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.652728] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.652737] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.652747] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.652800] Dev sdb: unable to read RDB block 0                                                 
kernel: [  132.660813] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.660821] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.660830] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.660840] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.668973] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.668981] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.668989] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.668999] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.678458] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.678466] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.678474] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.678484] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.686109] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.686117] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.686125] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.686135] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.694726] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.694734] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.694743] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.694753] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.704767] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.704775] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.704784] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.704794] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.704853]  unable to read partition table                                                     
kernel: [  132.706371] sd 5:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).                 
kernel: [  132.709850] sd 5:0:0:0: [sdb] Using 0xffffffff as device size                                   
kernel: [  132.712612] sd 5:0:0:0: [sdb] Attached SCSI disk                                                 
kernel: [  132.723607] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.723617] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.723626] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.723637] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.732254] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.732262] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.732270] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.732280] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.742638] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.742647] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.742656] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.742666] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.752637] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.752646] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.752656] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.752666] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.770025] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.770034] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.770043] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.770053] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.780526] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.780535] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.780545] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.780557] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  132.790883] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  132.790892] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  132.790901] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  132.790912] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  133.339193] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  133.339201] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  133.339210] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  133.339220] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  133.347192] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  133.347196] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  133.347202] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  133.347208] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       
kernel: [  133.354709] sd 5:0:0:0: [sdb] Unhandled sense code                                               
kernel: [  133.354717] sd 5:0:0:0: [sdb] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE                 
kernel: [  133.354727] sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current]                               
kernel: [  133.354737] sd 5:0:0:0: [sdb] Add. Sense: No additional sense information                       

I get the feeling that if I swap the EEPROM out on the PCBs, I'll be able to recover my data. Am I on the right path here?
NOTE: The original PCB is now toast, I tried to repair the foil runs and even the momentary heat of my iron popped the IC. No action at all from it anymore.

There are some images of the damaged PCB (prior to repair attempts) at http://picasaweb.google.com/bill.fetters/HDD#

Any help would be appreciated.

[icetnet]

Wow... No takers. Anyone? Anyone? Bueller?

[BlackST]

What exactly do you want to do ?

[icetnet]

What exactly do you want to do ?

Here's the dilemma. I would like to be able to recover data from this drive. Actually, I would like to be able to swap the donor PCB onto the original PCB and have the drive work and be able to boot back into the system on the drive (without having to recover data and discard both drives).

The theory, as I understand it, is that if I change the EEPROM from the original PCB to the donor PCB, I will have all of the 'specs' transfered and the drive will work like nothing happened to it.

The fear is that I will transfer the EEPROM to the donor PCB and end up with two completely dead drives. Thus, I am looking for any guidance, success stories, and hints that the theory matches reality and this can be done. So, this is my attempt at doing research ahead of time. I've got a good adjustable solder/desolder station and some 15 year old 'ancient' skills in PCB repair (things were much bigger back then). I'm rusty and I also don't have the testing equipment to verify systems, just some basic test gear.

So, that's my plea. Any ideas on what I should do?

[hddmania]

DIY Physical Recovery comes with a huge risk of losing everything in a few seconds...

If you are good at soldering with proper equipment with 15 years of experience, I don't see you damaging the PCB during the chip swap.

Just make sure the donor PCB is compatible so that you don't end up killing something inside the drive.

I would still say the proper diagnostic first before you do any chip or PCB swapping. Also, if you realized it was the PCB damage PLUS something else that is beyond your equipment, the physical recovery price will double or tripple after the failed DIY Recovery Attempt at the most recovery centers!!!

Right now it may be a cheap fix but if something goes wrong or misdiagnosed the problem and if you proceed with the DIY, your data may still be available for the recovery but it will be sure hit the $1,000 and up range...

Good Luck with the swap!!!

[ktheking]

First of all ,you fear is very well grounded.
You might end up destroying the data on the resulting drive by swapping the board with a board with a different mfg date.

A trick that however has the most chance to work (without swapping the platters) ,is the one with swapping the board whilst it is working (after powering off the motor with OS command) + reverse imaging with ddrescue or something else ,so that SA is not read at ALL !
But this'll only work IF the manufacter didn't change voltages (so that your mfg date isn't seperated too far).

Check these videoclips (by Jedi Master Scott) to get into the basics :
Harddrive recovery part1-7
part 1 : http://www.youtube.com/watch?v=Kx-D1nJcv0k
part 2 : http://www.youtube.com/watch?v=Tg0Uli2_rwI
part 3 : http://www.youtube.com/watch?v=Cayzw1iThjM
part 4 : http://www.youtube.com/watch?v=1_sNdPoQdcM
part 5 : http://www.youtube.com/watch?v=eOvZZakhihM
part 6 : http://www.youtube.com/watch?v=CH6pKDsggZc
part 7 : http://www.youtube.com/watch?v=TNhajraPuWY

Advanced Harddrive recovery part1-5
part 1 : http://www.youtube.com/watch?v=vCapEFNZAJ0
part 2 : http://www.youtube.com/watch?v=w2FGKD4u8TU
part 3 : http://www.youtube.com/watch?v=jAUtv6kOCGE
part 4 : http://www.youtube.com/watch?v=5xdboKrOllE
part 5 : http://www.youtube.com/watch?v=MydSI4Jv2EI

Outerz0ne 6 - Hard Drive Kung Fu Magic 1-5
part 1 : http://www.youtube.com/watch?v=uLOmywCfEDU
part 2 : http://www.youtube.com/watch?v=DGVUev8tLjc
part 3 : http://www.youtube.com/watch?v=edK0lg3Xrh4
part 4 : http://www.youtube.com/watch?v=QfSykmrwXIA
part 5 : http://www.youtube.com/watch?v=QIjT_8Bdzl8

Diagnostics for Hard Drives and Data Recovery at Phreaknic13 :
http://www.youtube.com/watch?v=5DGqUTSh ... xt_from=PL

RAID reassembly :
http://www.youtube.com/watch?v=JacKwC5S ... playnext=1

Kind regards,

K.

[pcimage]

On this particular drive you have one shot at transferring the ROM (as the info contained therein is unique, even down to the s/n) and as far as I remember these have particularly stubborn ROM chips mounted with pads rather than pins, and usually sitting on top of a large solder pad making removal very difficult and risky.

Yes, if you are successfull in transferring the ROM then it should work (assuming no preamp damage), but if you make a mistake then like hddmania says prepare yourself for a $1,000+++ bill.

It's up to you of course, if your data is worthless then give it a go.

[hddguy]

NOTE: The original PCB is now toast, I tried to repair the foil runs and even the momentary heat of my iron popped the IC. No action at all from it anymore.

Are you sure you are up to giving this a shot yourself?

[BlackST]

The fear is that I will transfer the EEPROM to the donor PCB and end up with two completely dead drives. Thus, I am looking for any guidance, success stories, and hints that the theory matches reality and this can be done. So, this is my attempt at doing research ahead of time. I've got a good adjustable solder/desolder station and some 15 year old 'ancient' skills in PCB repair (things were much bigger back then). I'm rusty and I also don't have the testing equipment to verify systems, just some basic test gear.

Everybody comes here saying that 90 years ago they repaired everything with a screwdriver and/or McGyver is a nerd in comparison, some dare and - not because they are good at it, simply they were lucky (In italian we say "hanno avuto culo" = they had a big ass) , the majority end hearing "CRACK! POOF!" seeing and a grey cloud of smoke , or hearing some grinding sound from the HDA and watch their porn and warez... oops, their data turn into dust.
The maximum damage you can face is to make two drives FUBAR, only you know what's inside and what is the value.
Of course, when reading that everyone want to give a try to put hands on HDAs or other things, the idea is that data is nothing important OR people want to learn something at other's expense. But we techies are malicious.

What I still don't get is why many people - keeping goin' on with military slang - after one or more FUBAR, keep experiencing BOHICA. But this is another story. Pathway to success is full of failures.

P.S. for who don't know/understand the acronyms , PM

[unknown]

I like the Italian proverb.

"hanno avuto culo"

[fzabkar]

The fear is that I will transfer the EEPROM to the donor PCB and end up with two completely dead drives. Thus, I am looking for any guidance, success stories, and hints that the theory matches reality and this can be done.

You could give the job to a junior TV tech with steady hands and good eyesight.

Otherwise, read about failure and success here:
diy-rom-swop-gone-wrong-t15335.html

BTW, I still say the original job just needed some wirewrap wire between the plated through holes on either side of the break. I don't understand why you had to go anywhere near any IC. :-?

[icetnet]

BTW, I still say the original job just needed some wirewrap wire between the plated through holes on either side of the break. I don't understand why you had to go anywhere near any IC.

The short answer is that there is no hole on either side of the break. There is the one hole and then the foil terminates in the IC package. Thanks though, I really appreciate the help.

@BlackST, I really appreciate the condescention. I know you are better than me. That's the idea of the forum... to get help. I'd love to give you my credentials, but I'm sure yours are much better. Thanks anyway.

On this particular drive you have one shot at transferring the ROM (as the info contained therein is unique, even down to the s/n) and as far as I remember these have particularly stubborn ROM chips mounted with pads rather than pins, and usually sitting on top of a large solder pad making removal very difficult and risky.

Yes, if you are successfull in transferring the ROM then it should work (assuming no preamp damage), but if you make a mistake then like hddmania says prepare yourself for a $1,000+++ bill.

It's up to you of course, if your data is worthless then give it a go.

Thanks. Yes, these are padded chips. I've ordered a couple of extra heat sinks just in case.


@anyone (other than BlackST): Anyone recommend a good place to have this done? Both boards have exactly the same voltage, current, firmware and other parameters, just different manufacture dates.

[fzabkar]

@BlackST, I really appreciate the condescention. I know you are better than me. That's the idea of the forum... to get help. I'd love to give you my credentials, but I'm sure yours are much better.

Most of the DR pros, including BlackST, appear to come from a software background. Some don't even understand how a multimeter works. ;-)

[drc]

I would argue that multimeter proficiency would be part of the minimal requirements to be considered a "pro" in any field that involves, you know, electricity

[fzabkar]

I would argue that multimeter proficiency would be part of the minimal requirements to be considered a "pro" in any field that involves, you know, electricity

I would have hoped so, too, but, surprisingly, that doesn't appear to be the case.

Perhaps you can show BlackST how to answer my simple question in this thread?
viewtopic.php?f=1&t=15374

[pepe]

Most of the DR pros, including BlackST, appear to come from a software background. Some don't even understand how a multimeter works.

Some multimeters have several volts on its terminals in ohmmeter mode when open circuit. This voltage together with the imput capacitance of the instrument can damage some parts, like MR heads.

Not everybody is software engneer here...

pepe

[BlackST]

Perhaps you can show BlackST how to answer my simple question in this thread?
viewtopic.php?f=1&t=15374

Frank, seems that you don't like me and only you know why, and in return I have not to like you , but this is a free world till a certain extent so you can say what you want (but me too). If you want something, ask directly but I will decide if it's worth an answer. You have a similar multimeter , you are good at googling, if you lost the specs and/or the service manual I'm sure you can get or ask it.

Moreover, Seems that all the attempts to put me under a bad light have the exactly opposite effects.

PERIOD.

[fzabkar]

Frank, seems that you don't like me and only you know why ...

I don't like you because you're arrogant, and the reason you can't see that is because you're arrogant.

Catch 22.

[BlackST]

Then I'm proud to be who I am.

[HDD Spaz]

Pitty you can't settle this in a ring

My money is on BlackST.