When starting up my PC i get..Unmountable_boot_volume.

[neil]

Last week i put together my new PC.
AMD2000XP
Epox 8KHA+
512mb cruical 2100
nothing is OC'ed

I deceided to do a fresh install of WindowsXP. Previously i was running win2k.
So i installed XP, everthing installed without a problem. My Pc was running great for about 3 days.
Then yesterday when i got home from Work i tried to turn my PC on and while it was booting up my HD starts making this unusual sound.(it seems like the head is searching for somthing, over, and over again) then i get the BSOD and the error message UNMOUNTABLE_BOOT_VOLUME. Great the first thing that i am thinking is that my HD died. Since i figured that my HD is dead, my first reaction is to make a image useing ghost. but when i try to access the drive i get an error message that 128btyes are missing.(thats not the exacat message, but it was something to that effect.) Then i tried to access the drive at the command prompt. Thats also a no go. (error mess: it said that the directory stucture was unreadable.)

Since i still figure that my HD is dead i brought it to work and maybe i can make an image off of it.
Well before i was going to do that i search the net along with the anand forums on Unmontable_boot_volume errors. I seems that for some reson Windows XP causes this error. From what i read this error comes up when your are in the process of upgrading to Windows XP. Well i wasnt in the middle of an install, upgrade, or installing new hardware.

Since i have my HD with me now at work with me, is it possible to fix this problem using chkdisk /r even thou it would be Slaved to my work pc?

Is it possible that my HD did die?
How could i test it to find out for sure?

When i get everything straighted out should i go back to Win2k to avoid this problem?, or is there are hotfix?

Sorry for the long post......
I just want to figure out what to do, so incase that i do need to buy another HD, i can order it today form work.

thanks
-neil

 

[Narse]

If your HDD is making that noise and you can't access it via Ghost or command promt, I would say that you have some bad sectors on the drive, a complete format may fix it. Aslo if you can place the drive in another XP system as slave and see if you can read it there

 

[Tedtalker1]

I have the same problem on my slave disk.Microsoft put a patch out recently for this exact problem.Search for q315403_WXP_SP1_x86_ENU.exe.I installed the patch but my drive is still unreadable.You might have better luck.I am using Diskeeper to get my important files off the disk and it's working.After I get the files I will reformat.

 

[Viper22]

Boot to the recovery console and run chkdsk /r that might fix it....also try booting to "last known good configuration".

Viper22

 

[neil]

thanks for the quick replies!

Last night i tried, booting with Last Known Good Config, and into Safe Mode but it came up with the same error.

In i little bit i am going to slave it to me PC here at work, and see if i can access it.
Also Tedtalker1, thanks for the tip no q315403, i'll try that also when i get home, if i can get the drive running


thanks again.

and i am allways open to more suggestions.

thank
-neil

 

[underpaid]

chkdsk /r from the recovery console should fix it, according to m$. If not, you may try fixboot as well. Had the same problem, was not an
upgrade though, on a customer's pc....chkdsk /r fixed the problem, but does take a while to complete. If you continue to have that problem,
you probably have faulty hardware, hdd, ram, etc.

 

[Ryan]

I Have been getting the problem a lot lately too. I have Run the recovery console, but I get the same error a few days after I run it. Here's what MS's solution for it is: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q297185, their fix doesn't work for me

 

[Tedtalker1]

Do a search for unmountable in the Technical support forum.Somebody claims to have a fix with the "fix master boot record procedure". fixmbr after chkdsk /r

 

[Tedtalker1]

Here is the causeCause.Here is the patchPatch

 

[neil]

woohoo

thanks everone

the problem was Stop 0x000000ED Error Message When Volume on IDE Drive with Caching Enabled Is Mounted (Q315403)

everything is back to running smooth..



thanks again

-neil