Showing posts with label hdd recovery project. Show all posts
Showing posts with label hdd recovery project. Show all posts

01 December 2010

Hard drive recovery project, part 5

See part 4 of the hard drive recovery project here.

So to recap, here are the most likely problems:

(1) PCB1 is bad. PCB2, while the same revision, is not sufficiently similar to work with HD1.

(2) PCB1 is bad. HD1 is also bad.

While I can't definitely rule out either option, I have no evidence to suggest that HD1 is bad.  The drive did appear to spin up with PCB2 vice PCB1, and there are no sounds or other evidence which might lead me to give more credence to a physical damage to the disk scenario.

In addition, I found this:
Seagate tends to use many different programs for the same hard drive model. This is why it is very difficult to find a circuit board with the same program (firmware) as your original circuit board. It is much easier to find a physically identical board. A firmware transfer can then be done to make an identical copy.
Also:
...it seems that newer Seagate boards have MANY different firmwares (even when they have the same firmware on the label), and is therefore very hard to match.
The argument here suggests that perhaps PCB2, while listed on the drive as the same firmware, may not actually be the case.  So using the service to "clone" PCB1 would ensure that the replacement PCB does in fact have the same firmware (instead of just assuming it does in the case of PCB2, despite the label).

The other option is to take a closer look at PCB1 for signs of damage that may be able to be fixed.  This is certainly something that I can't do myself, but some friends have offered to help and I am grateful for that.

So the immediate plan of action is to do just that, examine PCB1 for signs of damage in the hopes that maybe a broken solder point can be fixed.  If that doesn't work, the cloning service (at the cost of $50) seems like a good next step.

What are your thoughts, especially regarding the cloning option?

30 November 2010

Hard drive recovery project, part 4

See part 3 of the hard drive recovery project here.

Torx screwdriver acquired, checklist complete.  Now on to the results...

I tried a variety of possible combination of devices to better isolate the problem.  For the sake of simplicity, I'll label my desktop, hard drive, and PCB as #1 and Tracy's as #2.  Tracy's HD2, PCB2 and Desktop2 are all known working devices.

So the initial problem is that HD1 and PCB1 do not work in Desktop1.  The drive does not appear to spin up at all, and we are rewarded with a message that there is no bootable device to be found.  Hard drive is not recognized in the BIOS setup.

HD1 and PCB1 in Desktop2: No bootable device. Hard drive is not recognized in the BIOS setup.

HD1 and PCB2 in Desktop3 (this was my first experiment a few weeks back): No bootable device. Hard drive is not recognized in the BIOS setup.

HD1 and PCB2 in Desktop1: BIOS is slow to start and eventually errors to a hard disk error. However, the hard drive is recognized in the BIOS and you can hear at least attempt to spin up. Also, changing the boot order to CD first and trying to boot from a CD encounters the same error.

HD1 and PCB2 in Desktop2: BIOS is slow to start and eventually errors to hard disk error. However, the hard drive is recognized in the BIOS and you can hear at least attempt to spin up. Also, changing the boot order to CD first and trying to boot from a CD encounters the same error.

HD2 and PCB1 in Desktop1: No bootable device. Hard drive is not recognized in the BIOS setup.

We know all #2 devices work, so that brings us back to the suspect devices, HD1 and PCB1.

Here are my theories:

(1) PCB1 is bad. PCB2, while the same revision, is not sufficiently similar to work with HD1.

(2) PCB1 is bad. HD1 is also bad.

Ideas?

Hard drive recovery project, part 3

See part 2 of the hard drive recovery project here.

I installed the new drive, booted up the desktop with Hirens Boot CD and used G4L (Ghost for Linux)'s Click and Clone feature to backup the hard drive (technically, this makes the new hard drive also look like the original 500GB hard drive instead of 2TB, but resizing the partition is a simpler project for another day).  I should also add that the .ZIP file that contains Hirens Boot CD has a nice script that automates burning to CD--no need to figure this out manually. A really nice touch.

About 75 minutes later and the drive was cloned.  The ultimate test was removing the original 500GB drive and leaving only the newly-cloned 2TB drive.  Power-on...success. Worked like a champ.  I think it's important to add here that I recognize that none of this is new to many people, and that things so far are happening exactly as you would expect.  The key difference here is that I have not typically done any of this before, so it's all new to me.  So feel free to call me the hard drive recovery noob, I won't mind. :-)

This post brings us to the present.  I have both drives ready to go, now I just need to find a smaller torx bit to be able to remove the PCBs from the drive casing.  Presuming I can find the right size, I hope to be able to swap out the boards tonight and figure out if this is going to work!

To be continued...

Hard drive recovery project, part 2

See part 1 of the hard drive recovery project here.

Bringing the issue to some other friends, we discussed the possibility of freezing the drive, although this seemed an unlikely solution given the problem did not appear to be mechanical.  The other possibility was that the circuit board malfunctioned.  The only way to test this is to get a circuit board from the same model hard drive with the same firmware (and oh yeah, the circuit board has to be the same revision, too).  Not impossible standards to meet, but pretty exacting nonetheless.  The reason is that the circuit board contains the drive's unique disk geometry.  Another brand or model of hard drive isn't going to work.  Even with the case of two identical revisions, there is no guarantee of it working.

About this time, I realized that when I bought my desktop, we actually bought two desktops; one for me and another for Tracy (why I didn't realize this earlier is a mystery to me).  We also bought the desktops at the same time and in the same configuration.  It seemed likely that the hard drives would be of the same make and model (they were); that they were both using the same version of firmware (they are); and upon further review it turns out that both drives are also using the same revision.  So far, so good.

Of course, using the PCB from my wife's hard drive would mean backing up that drive first as to preserve the data (and of course, if the new PCB worked, the drive would be borked anyway without a third PCB).  A quick trip to Best Buy and I picked up a 2TB drive (a pretty good deal at $99, btw).

To be continued...

Hard drive recovery project, part 1

Back in August 2009 I bought a new Dell Desktop as part of a back-to-school special and loaded it up with a ton of RAM and a few other nice upgrades.  Everything had been working great until I came home a few weeks ago and was greeted with a black screen and a message that there was no bootable drive available. Oops!

Figuring it was just a one-time error, I rebooted the computer.  Same result.  I power-cycled the computer.  Still no joy.

At this point I am getting frustrated, but there are still a lot of possibilities.  I powered off the computer, opened it up and checked and re-seated the power and SATA cables.  Fired the computer back up, nothing.  At this point I should add that the desktop had not been moved at all, so the possibility of physical damage to drive, while possible, was not high on my list of suspects.  And yes, I recognize that physical damage could indeed occur without moving the drive.  It just seemed (and seems) an unlikely culprit.

I pulled the drive and found a friend whose computer was SATA-capable (all of my older computers were not). I figured that I could further isolate the problem if the drive worked in his box.  The answer was that no, the drive did not work in his box.  In fact, to our best observation the drive wasn't even spinning up, at all.

To be continued...