Page 1 of 1
BSOD - Inaccessible_boot_device
Posted: 17. May 2009, 15:57
by pmorton
I've just upgraded Jaunty host and Virtualbox guest Win2K has stopped working. On power-up, I get BSOD and stop error message0x0000007B INACCESSIBLE_BOOT_DEVICE.
I've tried setting up a new WinXP machine in case my Win2K.vdi hard disk file has become corrupted, but I get another stop error c0000221 'Unknown Hard Error' as the point of the OS installing off the CD drive.
Can anyone shed any light on what has happened here?
Re: BSOD - Inaccessible_boot_device
Posted: 17. May 2009, 17:16
by Perryg
This could be caused by several things. If you are interested in finding out what the problem is you can look at the VBox log files and see if it points to the problem. Other than that the next step would be to re-install VBox and see if this fixes your problem.
Re: BSOD - Inaccessible_boot_device
Posted: 18. May 2009, 12:58
by pmorton
I can't see anything obvious in the log file flagging up a problem.
I've already uninstalled and purged Virtualbox and loaded 2.2, to no effect.
I did run out of hard disk space just before the problem arose. I've
resolved that by deleting files, but I'm wondering if it might be related.
Re: BSOD - Inaccessible_boot_device
Posted: 18. May 2009, 13:20
by vbox4me2
Check the IDE settings under the General section of VBox.
Re: BSOD - Inaccessible_boot_device (Ubuntu bug)
Posted: 18. May 2009, 16:45
by pmorton
I've tried them all, including PIIX3/4, to no benefit.
But I copied a Win2K.vdi file from another workstation, set it up on a hard drive away from the one which earlier
became full, gave it user:user ownership where user is a member of vboxusers, and 777 permissions, and it loaded without murmur! I then installed XP on the same drive, and it loads as well.
What can I conclude from this? Ubuntu 9.04 is leaving something behind after the root directory filled up and I freed up some space, which is still telling VirtualBox the disk is full and/or the files it needs in ~/.Virtualbox are inaccessible. It's a Ubuntu-related bug.
Thanks for your replies.