[SOLVED] Unmountable Boot Volume BSOD

[justinrpg]

I am unable to boot my Windows XP Guest! all I get is a Unmountable Boot Volume BSOD!!! I have VERY IMPORTANT information on that Guest and I cannot access it!!!

[stefan.becker]

Then use your not existing recovery.

If you want help, then post details. So is help not possible.

[justinrpg]

I don't know what details you want! it happened after Windows Updates inside the VM

[Perryg]

If the updates in a guest rendered it unbootable, the only way to recover is to restore from backup.
It may be possible to repair with the original install CD, but that is between you and Microsoft.
As a last resort you may be able to attach the bad *.vdi file as a second drive to another guest.

[justinrpg]

I fixed it!!! I attached it to another VM and when I tried to access it, I got "error performing inpage operation" I google that error message and this website came up

http://www.tomshardware.com/forum/22495 ... ation-quot


I followed the steps on this website,
typed in command prompt chkdsk <drive> /F (chkdsk e: /F)
it found numerous errors that it fixed and voila!!! It boots!!!

[mpack]

Thanks for the feedback.

[ProfMac]

If the updates in a guest rendered it unbootable, the only way to recover is to restore from backup.
It may be possible to repair with the original install CD, but that is between you and Microsoft.
As a last resort you may be able to attach the bad *.vdi file as a second drive to another guest.

I am trying to restore an XP Professional guest from a host backup. The *.bkf files are on a network share, and I can access them if I use shift-F10 to bring up a cmd window and log into the share during the early restore phase.

I lost my network activity, after the backup had done a state restore. The drivers said they were installed, but they gave nothing. I installed a WiFi dongle and used it's install CD to get some network connectivity, enough so I could work more with the system. Ultimately I enabled more of the network adapters, and the ones beyond the first one had connectivity.

It seems to take a very long time to move 80GB across the network, and I had to call Microsoft to re-authorize the install.

[mpack]

Eh? What is the point of your story? Apart from the word "guest" this doesn't seem to be a VirtualBox matter at all. You don't seem to be asking a question, and what does it have to do with the OPs thread?

[jollyjonson]

actually i got this problem in my virtulbvox and then on my pc and i find it its my windows faulty for getiing this error

sorry for bad english