Page 1 of 1
Could not read from the boot medium
Posted: 20. Dec 2012, 15:41
by PoulJ
Hi,
I got above fatal error message at first boot after upgrading to Virtualbox 4.2.5.r81684 (no idea if this is related).
I might have had a crash when last used the VD.
Any chance of recovery from this ?
This is Win-7 host & guest.
Cheers,
/Poul
Re: Could not read from the boot medium
Posted: 20. Dec 2012, 15:46
by mpack
To avoid confusing other readers, your log says "4.2.4" with that build number (4.2.5 is not a release version).
According to the log you have no floppy, no CD/DVD and no hdd connected to this VM. So as Yoda said, "That is why you fail".
Your VM is called "Mamut-16 USB-disk", which carries the implication that you are possibly attempting to boot from a USB drive - not supported in VirtualBox.
The VM as currently configured could never have worked, so it can't have been affected by the update.
Re: Could not read from the boot medium
Posted: 20. Dec 2012, 17:39
by PoulJ
Sorry for the confusion about the build no.
And it HAS been running from this USB connected harddrive for more than a month.
/Poul
Re: Could not read from the boot medium
Posted: 20. Dec 2012, 17:53
by Perryg
If as you suspect you had a crash it is possible that the control file is corrupt. Look and see if you have a *.vbox-prev file in the folder that has the *.vbox file and compare. If the *.vbox-prev has the proper data then you can (after you back it up) replace the *.vbox file with the *.vbox-prev.
Note: everything VirtualBox should be shut down while performing this.