• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Lost a hard drive...

H

Hork

Senior member
I would appreciate any help on this. Seems like when something like this happens to me my brain freezes up and I need to seek advice on what to do next.

I'm running Windows XP with SP2 and I have a primary IDE (C🙂 drive with 13GB that has my OS on it and a secondary IDE (D🙂 drive with 120GB with just data on it.

The other day I was trying to re-install Star Wars Battlefront on the secondary drive and I heard a noise that didn't sound very good. After rebooting I found that the BIOS still recognizes the drive but Windows doesn't see it at all (no D: drive).

I've already ordered a 160 GB drive, which I'm hoping to partition as 40GB C: and 120 GB D:. I should have no trouble transferring the existing C: OS and data over to the new drive, but what steps should I take to try to recover the data from the drive that crashed?

I appreciate your help.
 
I have that problem too. I have a Maxtor 200 GB drive seperated into C:\, D:\ and F:\, and a 40 GB WD drive called E:\. I just lost the 40 GB drive, and I can't find it anymore.
 
I just used GetDataBack on my drive and it worked wonderfully, BUT I was recovering data from a working drive that had been partitioned. So, Windows Drive Management could see the drive but I didn't format it. Not sure if this would be the same type of situation. I'm not sure if GDB works if Windows can't see the drive. If not, SpinRite says it does just this.

You could try the Demo version of R-Studio to at least see if it finds anything but I decided I didn't like the software, it didn't recreate all of my folders like GDB did.
 
Originally posted by: Hork
I would appreciate any help on this. Seems like when something like this happens to me my brain freezes up and I need to seek advice on what to do next.

I'm running Windows XP with SP2 and I have a primary IDE (C🙂 drive with 13GB that has my OS on it and a secondary IDE (D🙂 drive with 120GB with just data on it.

The other day I was trying to re-install Star Wars Battlefront on the secondary drive and I heard a noise that didn't sound very good. After rebooting I found that the BIOS still recognizes the drive but Windows doesn't see it at all (no D: drive).

I've already ordered a 160 GB drive, which I'm hoping to partition as 40GB C: and 120 GB D:. I should have no trouble transferring the existing C: OS and data over to the new drive, but what steps should I take to try to recover the data from the drive that crashed?

I appreciate your help.
Click to expand...

If you heard a horrible sound, chances are your data is toast. You can try the aforementioned utilities, but I doubt you'll have any luck. If it's not spinning up or the head is toast, no utility in the world can save your data.

 
Originally posted by: BadThad
If you heard a horrible sound, chances are your data is toast. You can try the aforementioned utilities, but I doubt you'll have any luck. If it's not spinning up or the head is toast, no utility in the world can save your data.
Click to expand...

I missed the horrible sound line. 🙂 SpinRite claims that if the BIOS can see the drive, then it can see the drive, it's DOS based. But BadThad is right, if the head is gone then you're SOL.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top