03-17-2010 01:40 PM
The accident cut 4 traces otherwise the drive was working great. I took it out of the notebook to put in my other drive...
Makes me sick. Anyway, how do I go about getting a replacement PCB? (I can swap the ROM, if needed) I just need to get the same rev of PCB right?
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
Let me know.
Thanks,
03-17-2010 07:51 PM
Hello and welcome to the forums Icetnet.
I know that feeling. Its something deep down in the pit of your gut, and empty dull but very preset feeling... sick indeed.
I feel your pain - I've been there!
About your replacement PCB - yeah, a board with the same REV will work perfectly.
In fact, I'm almost tempted to say that with THAT particular drive, a cousin PCB could also work - but I cant swear, - I'll need to research that more.
WHERE to get it is a darn good question.
You could search Ebay / one of those places for a "dead" drive and try your luck.
There was also this Chinese source I should remind myself of - the guy there stacks up on a lot of PCBs and has them cheap enough.
Could you give us a pic of the 4 conduits you severed though?
Depending on how it is - you attempt to repair is, and as long as they arent too small, I think you really could in fact repair it ![]()
Wouldnt be all that cosmetically appealing perhaps - but it would work fine ; ]
-All the best.
03-17-2010 08:37 PM
I was thinking about the repairs. I did a lot of electronics and PCB repairs in the late 80s early 90s, but these PCBs have some pretty tight foils. The pics show the severed runs just north of the 38 pin IC. The damage may have caused issue with a single run on the opposite side although it looks intact.
What would you suggest for repairs? Would an etching pen work?
As far as a cousin PCB, from the serial batch number and rev number, do I have to match further than that level?
Thanks,
Bill
03-18-2010 03:10 AM
03-21-2010 07:05 AM
04-03-2010 04:18 PM
04-03-2010 04:21 PM
Yeah, I hate to think of myself as an old timer
but I guess I am. The runs end at the IC and thus I cannot just jumper them. Lots of fun. Still working on a solution to this.
04-03-2010 08:33 PM
Here are the logs for the insertion attempt after replacing the PCB with the matching donor PCB.
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
Looks to me like the SMART data is not being sent. Is this what is on the EEPROM? It did seem to recognize the drive in the Direct-Access line. If so, which chip EXACTLY is the EEPROM? and what would be the best method of replacement?
Thanks,
04-05-2010 03:55 PM
06-03-2013 11:48 PM
This PCB swap, need to be changed BIOS. The 8pins (4 pins on each sides) with 25P05VP、25P10VP、25F512、25F1024、25F1024AN、SST25VF51
©2012 Seagate Technology LLC