Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hard drive suddenly "Unpartitioned"

Status
Not open for further replies.

Storm251

Technical User
Jul 25, 2007
2
CA
First things first, I use Windows XP Professional on a core2duo e6300, 1 gb ram, nvdia 7900gto. The culprit of this story is a Western Digital 250gb hard drive. This story may be a little lengthy. haha.

I have had a rather odd occurrence that happened out of the blue. I was watching a movie using media player classic and when I went to pause it I accidentally hit the "slow motion" button, and this caused the entire computer to lag like I had a p-33. This is something that always happens when I misclick that so I usually just end the process (using task manager) and the computer is fine. This time it was worse than usual so I just hit the reset button and went about my business.

This is where the problem begins. Right after that reset, I would get into windows and after about 20 minutes receive a "blue screen of death" as it's often called with no real explanation. This soon started happening in 15,10,5 minutes until eventually the computer got a blue screen at the Windows XP startup screen that says UNMOUNTABLE_DEVICE. Wonderful...

So the next thing I did was boot from the Windows CD to take a look at the partition, and apparently it reads it as unpartitioned space, with the full 250gb of free space. Okay that's odd, because for some reason this "unpartitioned" drive has no trouble getting to the first windows boot screen, it's recognized in BIOS. I tried using my other hard drive(the one I am on now) to boot from to try to save the data from the WD250(the messed up one), but if I try to boot both drives at once it hangs at the first Windows XP screen and it almost seems like the two are conflicting. Maybe because both are supposed to be boot disks, both are labeled "C:", but I don't want to perform any formats if someone knows how I can save the data from my WD250, without losing the data on this hard drive I'm on now (by formatting it).

This whole things is very odd, and I need to get that data on my WD250 back badly, it is irreplaceable.
 
Sounds like the original HD has a messed up partition table.
And it's possible for it to be recognized in BIOS, since only its firmware is being read there.

If both HD's are PATA, then connect the original one as Slave.
If both HD's are SATA, then connect the other HD to the original HD's SATA port.
 
If those do not work, then see if XP's boot manager gets the other HD to boot when both drives are connected.
 
Hey, sorry for the late reply, lots of work lately. haha.

The XP Boot Manager does not detect the secondary boot at all for some reason. It jsut skips right into trying to start up XP as if I don't have two boots. I still cannot get into XP when both hard drives are plugged in (regardless of Master/Slave). It's like they are both trying to boot at once, or for some reason the slave HD is still in charge of being the boot disk (even though It's not even listed in the boot device routine anymore. And even mroe confusing is that if I try to boot with the messed up hard drive as master I get a blue screen, but if I try to boot with it as a slave it just hangs rather than crashing.

I eventually formatted my WD-80 drive (the one I'm using to try and save the "good" one with) and that made no difference at all in the situation... I think I'm probably screwed:(
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top