Page 1 of 1
Could not read from the boot medium!
Posted: 2. Apr 2016, 19:20
by Jay1970
Good afternoon,
I am running VirtualBox on Ubuntu 14.04 and I am attempting to virtualize a separate physical Ubuntu 14.04 box. Following are the steps I have followed attempting to virtualize the box.
- Shut down the physical device.
- Run dd if=/dev/sdc of=Disk1.raw after booting the physical device using a LiveFS CD and confirming /dev/sdc is not mounted.
- Run VBoxManage convertfromraw Disk1.raw Disk1.vdi --format VDI
- Create a VM which uses Disk1.vdi as the virtual disk.
- When the VM is booted a message stating, "FATAL: Could not read from the boot medium! System halted," is received.
Unfortunately, I do not have access to a VMWare server to use the VMWare P2V tool. I am sure this is something I am doing wrong. Any suggestions would be greatly appreciated.
Thank you!
Re: Could not read from the boot medium!
Posted: 5. Apr 2016, 04:30
by Jay1970
This evening I went back through the image I created. All of the partitions are present, are the correct size, can be mounted and the UUIDs are correct in /etc/fstab. LVMs function as expected (e.g. can be mounted and contain the correct data).
Any suggestions would be greatly appreciated.
Thank you.
Re: Could not read from the boot medium!
Posted: 5. Apr 2016, 12:35
by mpack
Please post a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.
Re: Could not read from the boot medium!
Posted: 5. Apr 2016, 23:36
by Jay1970
Log file is attached.
Thank you for your help.
Re: Could not read from the boot medium!
Posted: 6. Apr 2016, 10:13
by mpack
You are using the Ubuntu fork. If you want support here, you need to be using VirtualBox, and not someone elses rebuild of it. You need to either download and install VirtualBox from the
Downloads area here, or get support on the Ubuntu forums.
In the meantime I can point out a mistake in the VM recipe :-
VBox.log wrote:
00:00:04.027502 Host RAM: 2990MB total, 552MB available
...
00:00:04.516740 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)
00:00:04.517356 VRamSize <integer> = 0x0000000000c00000 (12 582 912, 12 MB)
Memory overcommitted - you can't spend what you don't have. OTOH 12MB sounds low for a modern OS.
VBox.log wrote:
00:00:07.768995 Guest Log: BIOS: Boot : bseqnr=1, bootseq=0231
00:00:07.769341 Guest Log: BIOS: Boot from Floppy 0 failed
00:00:07.769726 Guest Log: BIOS: Boot : bseqnr=2, bootseq=0023
00:00:07.772467 Guest Log: BIOS: CDROM boot failure code : 0003
00:00:07.772833 Guest Log: BIOS: Boot from CD-ROM failed
00:00:07.773209 Guest Log: BIOS: Boot : bseqnr=3, bootseq=0002
00:00:07.773887 Guest Log: BIOS: Boot from Hard Disk 0 failed
00:00:07.776836 Guest Log: No bootable medium found! System halted.
00:00:09.748077 Changing the VM state from 'RUNNING' to 'SUSPENDING'.
Odd. The error in the log is "No bootable medium found!", which is a very different error from the one reported.
I will not be able to respond further until I have a new log showing the same error, in VirtualBox.
Re: Could not read from the boot medium!
Posted: 6. Apr 2016, 14:50
by Perryg
"No bootable medium found! System halted" means exactly what it says and in every case is an issue with the guest. For some reason your P2V has not fulfilled the requirements to make a bootable OS.
While Don is correct that we can not help you with the Ubuntu fork of VirtualBox I can say that you should receive this error no matter which you use. You should probably try a boot repair of the guest.