XP Unmountable boot volume


Recommended Posts

Hi..

I'm sorry to put in topic title the " Urgent " but this is really a urgent call for help, since she has data not backed up that she was working at the crash moment..

My cousin computer running XP SP3 Pro just died with the 0x000000ED Unmountable Boot Volume BSOD at booting...

She has a SATA disk..

Meaning that when I insert XP SP3 Pro CD it recognizes the disk but says it's empty, I guess that I need to run the MBR fix on command line.. But the CD not recognizing any files in the disk and not finding windows files, jumps to the partition creating deleting menu..

I have been trying to make some USB pen load at bios boot to somehow fix the MBR, but with no luck since it detects the USB pen at bios and the bios is configured to start from any USB pen connected, but since the disk is in NTFS it's been hard to find a way to fix the mbr, cause most tools that run from a USB pen don't work with NTFS only fat32 or fat..

Any help is deeply appreciated..

I have run all the options that came to my head..

I'm sure I'm missing some amazing tool that somehow I'm forgetting, but oh well....

Thank you :)

Edited by Anaron
Edited title + description.
Link to comment
https://www.neowin.net/forum/topic/843366-xp-unmountable-boot-volume/
Share on other sites

Do you have access to a Windows Vista\7 installation disc? It will be able to read a SATA drive no problem. If so, you can rewrite the bootsector for XP from the command line by using "bootsect /NT52 C:", assuming that the hard drive is mounted as drive C.

I'm not entirely sure that rewriting the bootsector will fix your problem. It sounds like it could be a bad hard drive. If you have access to a Fedora\Ubuntu live cd you could try using Palimpsest Disk Utility to verify the hard disk with SMART. Also consider doing a chkdsk from your Vista\7 live cd if you have not done that already.

Edited by xorangekiller

If you get that message when you insert a cd you are not booting to the cd. You need to put the cd at the top of the boot order in bios. And you do not fix the MBR from within the bios, you do it from a command line. I know you want to sound like you know what you're talking about, but it's very clear that's not the case. Just ask the questions and we'll be happy to help ;)

If you can download a copy of Ubuntu (or other Linux distro) do so then burn the ISO to disc. Next run the disc (do not install) as a demo. This will give you access to any drive that is not corrupted. If you are able to see the HDD that is the problem use Ubuntu to move the files to another HDD (external or internal).

Chances are the Hard drive is dead. Good luck.

If you get that message when you insert a cd you are not booting to the cd. You need to put the cd at the top of the boot order in bios. And you do not fix the MBR from within the bios, you do it from a command line. I know you want to sound like you know what you're talking about, but it's very clear that's not the case. Just ask the questions and we'll be happy to help ;)

Actually I do know what I'm talking about :)

I just typed to too fast without rereading what I typed, meaning I made the mistake of not making much sense, sorry about that... :)

Ok second try..

So you guys know that XP by default without using nlite or any driverpack integration doesn't support Sata disks at install..

What we do is use the F6 at install and insert a disk with SATA drivers.. And also normally after a XP installed in a SATA disk XP CD will detect the disk and support command line to fix master boot record errors or copy missing boot files...

That was why I was referring to fact it's a SATA disk...

And the fact that XP CD doesn't allow me to use the command line from the CD, since it jumps to the menu of partitions after loading the basic drivers telling me that the size of the disk is the same of free space, meaning MBR is probably corrupted..

Also what I mean when I say that I'm trying to use a USB pen, is I'm trying to boot from USB with tools that allow me to fix any boot errors, like running the fix mbr and XP CD command line support, the problem is that few tools support NTFS mostly just FAT32 or FAT ( FAT16 )...

I am able to boot from the USB, since I already changed BIOS to start from USB instead of HDD or CD-ROM

Again sorry for the fast typing and few sense I made i my first post, but I had her at my back screaming she lost her files..

... but I had her at my back screaming she lost her files..

Unless she is in your bed OR (not AND*) a family member - it is her problem that she lost her files.**

*if AND then perhaps it's gods fault she lost her files.

** oh and sorry for being crude just I hate whiny people.

How was XP originally installed on the computer? Either the manufacturer (or whoever installed it) had a disc with the SATA driver integrated, it was imaged with the driver, or the hard disk was put into AHCI compatibility mode. Check your BIOS; if your motherboard supports compatibility mode try using that.

For the record, I still think that you are best off checking if the hard drive is dead from a Linux live image, and possibly backing up the files that way too.

Unless she is in your bed OR (not AND*) a family member - it is her problem that she lost her files.**

*if AND then perhaps it's gods fault she lost her files.

** oh and sorry for being crude just I hate whiny people.

Unfortunately I have to agree with you, people don't make backups and then stuff like this happens...

And yes like the 1000 time I told her to do weekly backups, but " Oh it's boring ".

And the person fixing it is almost the culprit in there eyes for not recovering everything...

But oh well it's family got to do the right thing and try my best to recover her Windows :)

How was XP originally installed on the computer? Either the manufacturer (or whoever installed it) had a disc with the SATA driver integrated, it was imaged with the driver, or the hard disk was put into AHCI compatibility mode. Check your BIOS; if your motherboard supports compatibility mode try using that.

For the record, I still think that you are best off checking if the hard drive is dead from a Linux live image, and possibly backing up the files that way too.

It was installed with SATA drivers integrated, while it wasn't me that installed XP, the guys at the store where she goes for repairs asked me some months ago to make them a CD with that, so I suppose it's the same disc used here..

Her disk is just some months old, having lost one already six months ago..

But I'm using the same ISO that I gave those guys..

But I'm going to follow your advice and try using a LINUX distro live CD, to see what I can find in her Windows partition..

And now that she isn't screaming anymore and I'm allowed to think more calmly I'm thinking on using SpinRite...

So the this one is an easy fix

all you have to do is preform a chkdsk /f c: on the drive.

I'd recommend creating a bartpe disk. Then go into the bios and change the sata drive type to IDE (Jus don't forget to change it back when you are done). Then boot the bartpe and preform the chkdsk. Or if possible take the drive out and connect it to another windows machine and preform the check disk from there. All though that will most likely fix the problem you ahve to wonder what caused the problem in the first place. Usually its a bad sector. So it might not be such a bad idea to do a sector scan on the drive with a program like spinrite just to make sure the drive is running like it should.

Not quite sure what all the talk in this thread is about the MBR needing to be fixed. An unmountable boot volume BSOD is almost always a corrupt NTFS partion. Nothing to do with the MBR.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
    • This is how much iPhone 18 Pro could cost after Apple's price hike confirmed by Hamid Ganji Image via Apple Apple CEO Tim Cook confirmed in a recent interview that the company may have to raise prices on some of its products due to the ongoing memory shortage. While he did not elaborate on the scale of the price hikes, new estimates suggest that Pro iPhone models could become significantly more expensive this fall. The Wall Street Journal and research firm TechInsights have come up with an educated estimate of how much the upcoming iPhone 18 Pro could cost after its launch in September. The estimate is based on current increases in memory and storage chip prices. For starters, the iPhone 18 Pro base model is expected to feature 12GB of RAM and 256GB of internal storage. According to TechInsights estimates, 12GB of DRAM for the iPhone 17 Pro cost Apple $39 last year. However, for the iPhone 18 Pro, the cost of the same amount of DRAM could soar to $145. Likewise, 256GB of flash storage that previously cost $13 could now cost around $51. Producing a base iPhone 17 Pro reportedly cost Apple around $582, but TechInsights estimates that the production cost of the iPhone 18 Pro could rise to $726. If Apple wants to maintain the roughly 47% profit margin it enjoys on the iPhone 17 Pro, the base price of the iPhone 18 Pro would need to reach $1,371. After standard pricing adjustments, customers could end up paying around $1,299 for the base model. However, that may not be the end of the story. As we previously reported, the iPhone 18 Pro is said to feature a variable-aperture lens, which could cost Apple at least 50% more than the current camera system. The estimated $1,299 price tag does not include the additional cost of this upgraded camera hardware. Once that expense is factored in, the base model could cost at least $1,399. A $1,399 price tag for the base iPhone 18 Pro would represent a significant increase over the current $1,099 starting price of the iPhone 17 Pro. If Apple wants to keep its upcoming iPhones competitive, it may need to accept lower profit margins.
    • Oh man, but what if I have the PS3 version?
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!