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
Could not read from the boot medium
Could not read from the boot medium
- Attachments
-
- Mamut-16 USB-disk-2012-12-20-14-19-53.zip
- (17.1 KiB) Downloaded 4 times
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Could not read from the boot medium
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.
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
Sorry for the confusion about the build no.
And it HAS been running from this USB connected harddrive for more than a month.
/Poul
And it HAS been running from this USB connected harddrive for more than a month.
/Poul
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Could not read from the boot medium
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.
Note: everything VirtualBox should be shut down while performing this.