Содержание
- Error while booting VMDK in VMWare Player; UNMOUNTABLE_BOOT_VOLUME
- virtualbox.org
- Экран смерти — UNMOUNTABLE_BOOT_VOLUME — решение проблемы (HD)
- Ошибка UNMOUNTABLE BOOT VOLUME В Windows 10. Как можно решить проблему?
- How to solve the issue of VirtualBox showing a VM with UNMOUNTABLE_BOOT_VOLUME?
- 3 Answers 3
I wouldn’t think SysPrep has much to do with it; it basically gets Windows ready to regenerate setup information, most notably the GUID. From the sounds of it, I’d guess that the image doesn’t have storage controller drivers for the VM. What type of storage controller have you configured for your VM? And can you at least confirm the original VMDK works, using something like VMware Player? Then do the conversion and see if you can’t get it to run in a local Hyper-V instance first?
Error while booting VMDK in VMWare Player; UNMOUNTABLE_BOOT_VOLUME
Hi all and thanks in advance for taking the time to read this. My employer has provided me with three VMDK files, each representing a different hard drive of a VM. My aim is to get these converted to VHD and uploaded into an Azure environment. The issue is, after I have converted these and uploaded them into Azure, I can’t get them to complete provisioning and run cleanly. As it turns out SysPrep has not been run on this OS drive, so I imagine this could be the issue here. If anyone can confirm or deny this it would be a good start! So basically what I’m trying to do now is boot into the OS VMDK and run SysPrep on the image so I can export it and try the conversion again with the new image. However, when I try and launch the VM after configuring the settings, I get the following error on a blue screen during the boot process: UNMOUNTABLE_BOOT_VOLUME This goes back to the beginning of the boot process and will loop until the guest machine is stopped. I have tried booting in safe mode also and am having the same issue. Does anyone have any suggestion as to what the root of the issue may be? I’m new to virtualization so this is the first time I have had to do something like this, and no one in the office appears to have any further knowledge than I do. If it is of any use, the OS on the drive is a 64 bit instance of Windows Server 2008 Standard. Thanks for any and all suggestions!
asked Jul 29, 2014 at 12:51
Nick Chambers Nick Chambers
163 1 1 gold badge 1 1 silver badge 5 5 bronze badges
I wouldn’t think SysPrep has much to do with it; it basically gets Windows ready to regenerate setup information, most notably the GUID. From the sounds of it, I’d guess that the image doesn’t have storage controller drivers for the VM. What type of storage controller have you configured for your VM? And can you at least confirm the original VMDK works, using something like VMware Player? Then do the conversion and see if you can’t get it to run in a local Hyper-V instance first?
Jul 29, 2014 at 20:50
Thanks for the comment. This error message I’m getting is actually in VMWare itself, so I am unable to boot into it at all. I have also tried Oracle’s VirtualBox and am getting the exact same issue. I have installed the Hyper-V tools locally and will attempt to run the VHDs in a local instance.
virtualbox.org
The guest system was working fine (so it was on) when a power outage occurred. When I restarted Windows 8.1 and tried to run again the guest on Oracle VM VirtualBox, it got to the point where the XP logo was on the screen and the progress bar showed, but then it got to a bluescreen error, then restarted with Windows XP start options (Safe Mode, last working configuration, Normal etc). No matter which variant I choose, it goes to the same loop. The BSOD is so quick that I had to film it. It says UNMOUNTABLE_BOOT_VOLUME and error 0xED.
Nothing else was added to or removed from the system. It happened just as I restarted the host.
Is there a way to repair that? It is kinda important to me.
Last edited by sorin86 on 25. Mar 2014, 11:01, edited 1 time in total.
sorin86 Posts: 5 Joined: 18. Feb 2014, 20:13
Re: UNMOUNTABLE_BOOT_VOLUME with loop
by mpack » 18. Feb 2014, 20:49
Is the XP guest boot process entirely standard? I.e. no grub, no dual boot etc?
The first thing to notice is that the error is happening in the guest, meaning VirtualBox is still happy with the VDI file.
A power outage will cause loss of data, but that shouldn’t affect parts of the (virtual) disk already written, i.e. the boot sectors. So, provided you aren’t using snapshots this shouldn’t have caused a problem.
mpack Site Moderator Posts: 38142 Joined: 4. Sep 2008, 17:09 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Mostly XP
Re: UNMOUNTABLE_BOOT_VOLUME with loop
by sorin86 » 18. Feb 2014, 21:24
Thank you for the reply. Actually, I am not very knowledgeable about VirtualBox and virtual machines.
The XP boot is indeed «standard», no funny tricks.
I’m not sure about any snapshots.
That said, how should I begin to repair it? Are there specific steps?
sorin86 Posts: 5 Joined: 18. Feb 2014, 20:13
Re: UNMOUNTABLE_BOOT_VOLUME with loop
by mpack » 19. Feb 2014, 13:45
Before doing anything else I would make a backup of the VM folder so things can’t get any worse.
Then I would read the Microsoft Support article: Unmountable Boot Volume. Of course you can ignore the various hardware suggestions: you need to be thinking about booting from a (virtual) repair CD, or mounting the disk in another Windows VM — and running chkdsk on the damaged filesystem. You might also need to run fixboot.
Экран смерти — UNMOUNTABLE_BOOT_VOLUME — решение проблемы (HD)
In future you should consider making backups of your VM on a regular basis. If you had a recent backup this would be a trivial problem.
mpack Site Moderator Posts: 38142 Joined: 4. Sep 2008, 17:09 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Mostly XP
Re: UNMOUNTABLE_BOOT_VOLUME with loop
by sorin86 » 21. Feb 2014, 10:29
As I said, I know very little about VirtualBox and virtual machines. Therefore, your suggestions make little sense to me.
How could I boot from a CD? I’d be running Windows 8.1 as a guest and when I start the host XP, there is no option to change the boot order. It’s not like I have access to some internal XP BIOS or something. Besides, once inside the loop, there is no way out.
I have no idea how to build a virtual repair CD.
I have no idea how to «mount the disk in another Windows VM». What other VM? I only have that one.
How to run fixboot (or anything) when I’m in a no-escape loop?
Would you (or anyone) try to explain a step-by-step procedure in accessible terms? Obviously if I had been an expert in VM, I wouldn’t have needed help.
sorin86 Posts: 5 Joined: 18. Feb 2014, 20:13
Re: UNMOUNTABLE_BOOT_VOLUME with loop
by mpack » 21. Feb 2014, 14:43
You boot the guest from a virtual CD, not the host. Think of the host as a separate PC — it’s almost never relevant to the discussion.
As to how to boot a VM from a (virtual CD) you do it by attaching an ISO image to the virtual CD drive which is shown the Storage settings of you VM, and it’s also worth checking the System part of the VM settings to make sure the CD comes first in the boot order.
«Mount the the disk in another VM» == create another VM, mount the disk in it.
«How to run fixboot». As already described, you boot from a recovery CD, with fixboot on the CD. Or, run it from the other VM.
I’m afraid that I can’t give you general Windows tuition. This is a VirtualBox forum — you’re expected to understand the basic PC stuff already, otherwise VMing is kind of running before you can walk. Did someone else set up this VM for you? If you so might perhaps ask that person to help.
mpack Site Moderator Posts: 38142 Joined: 4. Sep 2008, 17:09 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Mostly XP
Re: UNMOUNTABLE_BOOT_VOLUME with loop
by sorin86 » 5. Mar 2014, 20:28
Would someone else try to respond in a more straightforward way? This respondent seems to think that everyone is an expert in VMs. Then why the forum?
Working with VMs is not basic PC knowledge.
Ошибка UNMOUNTABLE BOOT VOLUME В Windows 10. Как можно решить проблему?
Besides, I only have the host (Win 8.1 ) and the guest (Win XP). I have no boot CD (virtual or non-virtual), no ISO image. I don’t even have access to the original XP system.
How is it possible to mount a disk on another VM, since that disk is only virtual and not accessible but via the VM that is broken?
Can anyone on this forum provide a step-by-step procedure?
sorin86 Posts: 5 Joined: 18. Feb 2014, 20:13
Re: UNMOUNTABLE_BOOT_VOLUME with loop
by socratis » 6. Mar 2014, 02:03
Read the Manual. Chapter 1. First steps. Then read it again. I hope this is clear.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the » POST REPLY «, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
socratis Site Moderator Posts: 27689 Joined: 22. Oct 2010, 11:03 Location: Greece Primary OS: Mac OS X other VBox Version: PUEL Guest OSses: Win(*>98), Linux*, OSX>10.5
Re: UNMOUNTABLE_BOOT_VOLUME with loop
by sorin86 » 25. Mar 2014, 09:32
For a Windows XP Guest :
1. In the Oracle VM VirtualBox Manager, select the faulty XP guest and go to Settings/System and make sure the CD is above the Hard Disk in the Boot Order.
2. Insert the Windows XP installation CD and launch the virtual machine.
3. If you get a message like “no bootable medium found”, the the virtual machine has interpreted another virtual device as the CD drive, so right-click inside the window (or press CTRL+HOME) and correct that, by choosing the real CD drive. Restart.
4. Wait until it gets you to the welcome screen, then hit the R key on your keyboard. It will enter the recovery mode with a DOS prompt.
5. Now type chkdsk /p and hit Enter. This will launch a utility which will check for errors on your hard drive.
6. After the process is done, type fixboot and hit Enter to repair any damaged boot files which may have become corrupted. When asked to say yes or no, type the Y key on your keyboard.
7. Type exit and press the Enter key to reboot your computer (after extracting the installation CD).
If the virtual machine still doesn’t work, then it might be irreparable.
How to solve the issue of VirtualBox showing a VM with UNMOUNTABLE_BOOT_VOLUME?
and extracted the files, and set up a new VM on VirtualBox 5.0.12 using the extracted .vmdk file. The IE 11 on Windows 7 worked fine, but since I installed something, I thought I would install another copy of the VM which is fresh, so I extracted the files again and tried to use another copy of the .vmdk file to set up another VM. But VirtualBox complained that it is the same UUID and can’t create another VM, so I tried instead and used the IE 10 for Win 7 image instead (not IE 11, but IE 10). And then VirtualBox would boot up the VM and after 1.5 minutes or so, show the blue screen on the VM: It seems like it is related to that UUID issue. So I rebooted my Mac, and now set up a new VM using «IE 9 on Win 7», and this VM also have the same issue of UNMOUNTABLE_BOOT_VOLUME . So I think somehow, VirtualBox ran into some issue and didn’t set up the VM correct from this point on. I rebooted the Mac and restarted the VM and it is the same blue screen. How can this be solved? I also tried chmod -R a+rw for all the files for the extracted .vmdk file and for all the new files that VirtualBox created, so that all files have write permission for everybody, but that didn’t solve the problem.
nonopolarity
asked Dec 19, 2015 at 18:58
nonopolarity nonopolarity
9,406 25 25 gold badges 116 116 silver badges 168 168 bronze badges
3 Answers 3
I want to provide some insight as to what might be the case with UNMOUNTABLE_BOOT_VOLUME .
With those .zip files provided, if you use Mac’s default zip program to unzip it (by just double clicking on the zip file on OS X El Capitan), then it will first create a .ova file, and then it will immediately uncompress again, to 2 files: one .vmdk file and one .ovf .
Now, you cannot use those .vmdk files as is. You have to double click on .ovf for it to be opened by VirtualBox, and then it will clone the .vmdk image and make it into a VM.
I think you can also use something like the 3rd party Unarchiver, and unzip it, and it will create a .ova file from the .zip file. In this case, also just double click it for VirtualBox to use it, and I think in this case it also would not have the UNMOUNTABLE_BOOT_VOLUME problem.
Похожие статьи
-
Unmountable boot volume 0x000000ed
Содержание Синий экран смерти 0x000000ED Параметры UNMOUNTABLE_BOOT_VOLUME: Решение Похожие статьи: Reader Interactions Комментарии Fix Unmountable Boot…
-
Stopcode unmountable boot volume
Содержание Ошибка unmountable boot volume 0x000000ed Причина появления ошибки unmountable boot volume Stop ошибка 0x000000ed в Windows XP Stop ошибка…
-
Unmountable boot volume windows 10 на ноутбуке
Содержание Ошибка UNMOUNTABLE BOOT VOLUME В Windows 10. Как исправить? Как исправить ошибку UNMOUNTABLE BOOT VOLUME СПОСОБ-1: Решение проблемы с файловой…