seagate 7200.11 dead pcb

[djhash]

HDD: Seagate Barracuda 7200.11 1TB ST31000340AS Firmware:LC11

So I just killed my lacie by plugging in the wrong power adapter. There was no smoke or anything like that, I heard the dreadful capacitor zap. tzzt..tzzt..tzzt.. and I knew I blew something.

I hoped that I blew the board that's on the lacie case, and not the drive's pcb. So I opened it up, and removed the drive, and hooked it to my PC and... the power supply simply shut off. Usually this is an indication that there is short circuit some where.

So I looked around for a way to replace the pcb, and I ran into PCB solutions. Long story short, I decided to remove the pcb and take a look at the components and see what's up. As I peeled the white/yellow insulator, I can see brownish areas, but nothing too dark to indicate a component blew out.

I took a closer look at the board and I noticed a SS diode KVP 81A has a crack right down the middle. I took my trusty multi-meter, and set it to diode/continuity, and it beeped at the terminals regardless if I touched positive-positive or positive-negative.

So I thought to myself, I can purchase the replacement board from PCB solutions for ~$50, or I can try and see if I can fix this on my own.

The question is what should I be looking for here? Are there any tests I can do to determine other damaged components? Or is a PCB swap the only way to go.

Thank you
Djhash

[fzabkar]

Remove the 12V TVS diode (KVP marking) and you should be good to go.

See http://www.users.on.net/~fzabkar/HDD/TVS_diode_FAQ.html

[djhash]

Thank you all, the drive spins right up. However apparently there is some data corruption going on.

I see the folders, but they're empty. Well a few do show a handful of files.

at that point I unmounted and tried fdisk and ntfsck, and you'll see below what i'm getting.

Can someone verify this is indeed data corruption on the platter itself, or if the board is simply spitting out bad data.

Here is dmesg, fdisk, and ntfsck output when I connect the drive.

Code:

root@Ubuntu:/media# dmesg | tail
[  630.632886] ata1.00: configured for UDMA/133
[  630.648043] ata1: EH complete
[  630.648265] scsi 0:0:0:0: Direct-Access     ATA      ST31000340AS     LC11 PQ: 0 ANSI: 5
[  630.648797] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[  630.648916] sd 0:0:0:0: [sda] Write Protect is off
[  630.648923] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[  630.648974] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[  630.649529] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  630.676044]  sda: sda1
[  630.676657] sd 0:0:0:0: [sda] Attached SCSI disk
root@Ubuntu:/media# ntfsc
ntfscat      ntfsck       ntfsclone    ntfscluster  ntfscmp      ntfscp       
root@Ubuntu:/media# ntfsc
ntfscat      ntfsck       ntfsclone    ntfscluster  ntfscmp      ntfscp       
root@Ubuntu:/media# ntfsck /dev/sda
Boot sector: Bad jump.
Boot sector: Bad NTFS magic.
Boot sector: Bytes per sector is 0.
Volume size is set to zero.
First attribute must be after the header (0).

^C
root@Ubuntu:/media# ntfsck /dev/sda
Boot sector: Bad jump.
Boot sector: Bad NTFS magic.
Boot sector: Bytes per sector is 0.
Volume size is set to zero.
First attribute must be after the header (0).
^C
root@Ubuntu:/media# fdisk /dev/sda

Command (m for help): m
Command action
   a   toggle a bootable flag
   b   edit bsd disklabel
   c   toggle the dos compatibility flag
   d   delete a partition
   l   list known partition types
   m   print this menu
   n   add a new partition
   o   create a new empty DOS partition table
   p   print the partition table
   q   quit without saving changes
   s   create a new empty Sun disklabel
   t   change a partition's system id
   u   change display/entry units
   v   verify the partition table
   w   write table to disk and exit
   x   extra functionality (experts only)

Command (m for help): p

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x454c46b5

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63  1953520064   976760001    7  HPFS/NTFS/exFAT

Command (m for help): v
Remaining 5165 unallocated 512-byte sectors

Command (m for help): q

root@Ubuntu:/media# ntfsck /dev/sda
Boot sector: Bad jump.
Boot sector: Bad NTFS magic.
Boot sector: Bytes per sector is 0.
Volume size is set to zero.
First attribute must be after the header (0).
^C
root@Ubuntu:/media# fdisk /dev/sda1

Command (m for help): p

Disk /dev/sda1: 1000.2 GB, 1000202241024 bytes
255 heads, 63 sectors/track, 121600 cylinders, total 1953520002 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

     Device Boot      Start         End      Blocks   Id  System
/dev/sda1p1   ?   218129509  1920119918   850995205   72  Unknown
/dev/sda1p2   ?   729050177  1273024900   271987362   74  Unknown
/dev/sda1p3   ?   168653938   168653938           0   65  Novell Netware 386
/dev/sda1p4      2692939776  2692991410       25817+   0  Empty

Partition table entries are not in disk order

Command (m for help): v
Warning: partition 1 overlaps partition 2.
Remaining 251529590 unallocated 512-byte sectors



let me know what information to get to you if you need more.

Thank you again.

[fzabkar]

Here is dmesg, fdisk, and ntfsck output when I connect the drive.

Code:

root@Ubuntu:/media# ntfsck /dev/sda
Boot sector: Bad jump.
Boot sector: Bad NTFS magic.
Boot sector: Bytes per sector is 0.
Volume size is set to zero.
First attribute must be after the header (0).

You appear to be confusing the physical drive (/dev/sda) with the logical volumes (/dev/sda1, /dev/sda2, /dev/sda3, etc).

The command "ntfsck /dev/sda" is performing a check of an NTFS volume beginning at physical sector 0 of sda rather than logical sector 0 of sda1. That's why the results are gibberish.

Instead you need to type "ntfsck /dev/sda1".

Code:

root@Ubuntu:/media# fdisk /dev/sda

Command (m for help): p

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x454c46b5

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63  1953520064   976760001    7  HPFS/NTFS/exFAT

Fdisk has correctly analysed the partition information in sector 0 of the physical drive sda.

Now you are asking fdisk to analyse sector 0 of the logical volume sda1 as if it were an MBR with a partition table. In fact logical sector 0 of sda1 is a boot sector, so fdisk produces gibberish, as expected.

Code:

root@Ubuntu:/media# fdisk /dev/sda1

Command (m for help): p

Disk /dev/sda1: 1000.2 GB, 1000202241024 bytes
255 heads, 63 sectors/track, 121600 cylinders, total 1953520002 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x69205244

This doesn't look like a partition table
Probably you selected the wrong device.

     Device Boot      Start         End      Blocks   Id  System
/dev/sda1p1   ?   218129509  1920119918   850995205   72  Unknown
/dev/sda1p2   ?   729050177  1273024900   271987362   74  Unknown
/dev/sda1p3   ?   168653938   168653938           0   65  Novell Netware 386
/dev/sda1p4      2692939776  2692991410       25817+   0  Empty

Partition table entries are not in disk order

let me know what information to get to you if you need more.

Thank you again.

[djhash]

umm.. yeah.. let's forget that post ever existed.. and move along now.

A new question though... apparently the drive gets to a point where it's

Code:

"Failed to read boot sector"
and
root@Ubuntu:/media# dmesg | tail
[87796.493962] sd 0:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[87796.493972] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 3f 00 00 08 00
[87796.493993] end_request: I/O error, dev sda, sector 63
[87796.494002] quiet_error: 450 callbacks suppressed
[87796.494009] Buffer I/O error on device sda1, logical block 0
[87799.357741] sd 0:0:0:0: [sda] Unhandled error code
[87799.357752] sd 0:0:0:0: [sda]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[87799.357762] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 00 00 00 00 00 00 08 00
[87799.357783] end_request: I/O error, dev sda, sector 0
[87799.357793] Buffer I/O error on device sda, logical block 0


Is there a way to tell that the I/O error is a problem with the board and not bad heads, platters, motor, actuators.. etc..

I.E. If I should spend the $50 to replace the board? I think the service where I will purchase the board will copy the firmware from the board that I send to them. And they'll send the working board with the copied firmware to me.

[fzabkar]

Can you retrieve the drive's SMART report? You could use smartmontools under Linux.

[Spildit-Temp]

This is VERY, VERY, VERY BAD advice.

DO NOT, and i repeat DO NOT run FDisk or any other sort of partition / file system fixing tools.

I've swa many times with drives that have blown TVS that for some reason (that i don't understand) the translator sub-system and sometimes the defect g-list gets damaged as well.

This is VERY TYPIC on WD drives and i've saw it on Seagate as well.

Now imagine that your translator is messed up and the drive can't properly know where on platter (cylinder/head/sector) a specific Logic Block Address is assigned .... Now imagine that the address is messed up, not only damaged in a way that the drive shows 0-lba and stop working. Now what do you think it will happen if you run a Fdisk or Checkdisk or whatever ?

Those tools will NOT SEE the correct data (because of the messed translator) and will "scramble" it further. Now even if you try to fix the translator (internaly) you will be in a mess !!!

Never, and this is important, NEVER use that type of tools that WRITE to the same drive that you are trying to recover without CLONING the drive first.

I would have -

1 - Cloned the drive.
2 - Check G-List to see if it's intact,
3 - Check Heads to see if they are working
4 - Try to regen translator,
5 - Stop relocation
6 - Try to access data or clone again to ANOTHER drive.
7 - Try to retrieve data.

[fzabkar]

This is VERY, VERY, VERY BAD advice.

DO NOT, and i repeat DO NOT run FDisk

Fdisk is perfectly safe for examining the partition information.

These are the commands the OP used. None are data destructive.

Code:

root@Ubuntu:/media# fdisk /dev/sda

Command (m for help): m
Command action

   m   print this menu
   p   print the partition table
   v   verify the partition table
   q   quit without saving changes

Command (m for help): p
Command (m for help): v
Command (m for help): q

[djhash]

This is VERY, VERY, VERY BAD advice.

DO NOT, and i repeat DO NOT run FDisk or any other sort of partition / file system fixing tools.

I didn't do any file writing with fdisk, but there was the ntfsck, that looked like it didn't do anything.

Can you retrieve the drive's SMART report? You could use smartmontools under Linux.

Code:

djhash@Ubuntu:~$ sudo smartctl --all /dev/sda
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-55-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Vendor:               /0:0:0:0
Product:             
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.


Let me know if this shows anything.

[fzabkar]

This is VERY, VERY, VERY BAD advice.

DO NOT, and i repeat DO NOT run FDisk or any other sort of partition / file system fixing tools.

I've swa many times with drives that have blown TVS that for some reason (that i don't understand) the translator sub-system and sometimes the defect g-list gets damaged as well.

I spent a lot of time looking for documentation for the NTFSCHK command but I turned up empty. If it defaults to automatic repair, then I agree that it's a bad thing to do.

I did find a web page which looks like it has some kind of preliminary source code for the ntfsck project:

https://github.com/rrelmy/asus-rt-n56u- ... s/ntfsck.c

It appears that the author did intend to give the user the option of running a readonly check.

Code:

*   -a   : auto-repair. no questions. (optional: if marked clean and -f not specified, just check if mountable)
*   -p   : auto-repair safe. no questions (optional: same)
*   -n   : only check. no repair.
*   -r   : interactively repair.

As for translator/firmware damage due to an overvoltage, I can't see how that could be possible in the OP's case. The drive was in an external enclosure and would have not been spinning at the time that the OP plugged in the adapter.

[fzabkar]

Can you retrieve the drive's SMART report? You could use smartmontools under Linux.

Code:

djhash@Ubuntu:~$ sudo smartctl --all /dev/sda
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.2.0-55-generic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

Vendor:               /0:0:0:0
Product:             
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.


Let me know if this shows anything.

All the numbers are obviously nonsensical. Sorry, I don't know much about Linux, so I can't help you.

It may be that your drive now has a firmware problem, as Spildit has suggested. Does it show up in BIOS with the correct model name and capacity?

FWIW, LC11 firmware was affected by the 7200.11 BSY bug.

[Spildit-Temp]

Fdisk is perfectly safe for examining the partition information.

These are the commands the OP used. None are data destructive.

Code:

root@Ubuntu:/media# fdisk /dev/sda

Command (m for help): m
Command action

   m   print this menu
   p   print the partition table
   v   verify the partition table
   q   quit without saving changes

Command (m for help): p
Command (m for help): v
Command (m for help): q

Yeah ... i'm always thinking on Windows !
I don't use linux that much, except the OpenBSD for server side stuff like web hosting, ftp, ssh, etc ....
I don't use LINUX based OS to diagnose drive problems / fix file system.