"Error loading operating system" after host reinstall
Posted: 18. Oct 2010, 15:44
I'm in the sad state where I try to boot a Windows XP guest inside an Ubuntu 10.10 host, and the guest machine only shows a black screen and the words "Error loading operating system_"
I got to this point by reinstalling my guest operating system. Windows is using raw disk access on a partition that (I think) wasn't altered during the reinstall. However, after installing virtualbox 3.2.10 fresh from the ubuntu repo, I fond that my old .vmdk files don't work. I re-created them, re-created the guest and tried booting, but I then got errors with grub saying it didn't understand the filesystem--I'd forgotten that the mbr was maintained by virtualbox, and went away when the virtualbox was reinstalled. I tried using fixmbr using a windows disk, and that resulted in the "Error loading operating system".
The files are all still there. Ubuntu can mount the (NTFS) partition just fine and read/write files. I've also tried starting ubuntu in the virtual machine using a livecd, and it can read/write files on the partition also. There must still be some problem with the mbr, but I'm at a loss for how to fix it.
I got to this point by reinstalling my guest operating system. Windows is using raw disk access on a partition that (I think) wasn't altered during the reinstall. However, after installing virtualbox 3.2.10 fresh from the ubuntu repo, I fond that my old .vmdk files don't work. I re-created them, re-created the guest and tried booting, but I then got errors with grub saying it didn't understand the filesystem--I'd forgotten that the mbr was maintained by virtualbox, and went away when the virtualbox was reinstalled. I tried using fixmbr using a windows disk, and that resulted in the "Error loading operating system".
The files are all still there. Ubuntu can mount the (NTFS) partition just fine and read/write files. I've also tried starting ubuntu in the virtual machine using a livecd, and it can read/write files on the partition also. There must still be some problem with the mbr, but I'm at a loss for how to fix it.