"No bootable media found" after moving VM
Posted: 6. Dec 2017, 07:32
Background
I created a VM on my hard drive by importing a virtual appliance (.ova) file.
I created a virtual disk for the VM.
I enabled encryption.
What happened
I wanted to move my virtual hard disk to a USB flash drive because it was getting pretty big and I needed space on my HDD.
I formatted my flash drive to NTFS, to support files over 4GB.
I followed the guide at the link below to move the virtual machine disk (.vmdk) file from my VirtualBox VMs folder (in my users folder) to the flash drive: http://dirkstrauss.com/moving-virtualbox-vm/
The issue
When attempting to boot my virtual machine up after following the guide, I get the following error: "FATAL: No bootable medium found! System halted."
I'm also not prompted with the encryption password box at startup anymore.
Troubleshooting
I created a new encrypted VM from the same virtual appliance (.ova) file, and it worked perfectly.
I tried comparing the details and settings of the new machine and the broken machine, but they were all identical, except for encryption. (Also excluding the different location of the .vmdk file, of course.)
I re-enabled encryption in the broken machine's settings with the same password. This made the password box pop up when attempting to boot, but I get the same fatal error after typing in the password.
The only clue I have thus far is that right-clicking the broken virtual machine and clicking "Show in Explorer" brings me to the VirtualBox VMs folder in my Users folder, instead of the root of my flash drive where I moved the .vmdk file to.
I even tried following the guide (at the link above) again to move the .vmdk file back to its original folder in the VirtualBox VMs folder on my hard drive. No difference—I still got the same error.
With the .vmdk file moved back onto my hard drive, the details and settings of my broken machine and new machine are completely identical, yet one works and one doesn't at all.
Thoughts?
It seems like I would be getting that error message if I forgot to add the .vmdk file to my SAS/SATA controller, but I definitely followed all of the steps in that guide.
If additional info for troubleshooting is needed, ask away. Thanks!
I created a VM on my hard drive by importing a virtual appliance (.ova) file.
I created a virtual disk for the VM.
I enabled encryption.
What happened
I wanted to move my virtual hard disk to a USB flash drive because it was getting pretty big and I needed space on my HDD.
I formatted my flash drive to NTFS, to support files over 4GB.
I followed the guide at the link below to move the virtual machine disk (.vmdk) file from my VirtualBox VMs folder (in my users folder) to the flash drive: http://dirkstrauss.com/moving-virtualbox-vm/
The issue
When attempting to boot my virtual machine up after following the guide, I get the following error: "FATAL: No bootable medium found! System halted."
I'm also not prompted with the encryption password box at startup anymore.
Troubleshooting
I created a new encrypted VM from the same virtual appliance (.ova) file, and it worked perfectly.
I tried comparing the details and settings of the new machine and the broken machine, but they were all identical, except for encryption. (Also excluding the different location of the .vmdk file, of course.)
I re-enabled encryption in the broken machine's settings with the same password. This made the password box pop up when attempting to boot, but I get the same fatal error after typing in the password.
The only clue I have thus far is that right-clicking the broken virtual machine and clicking "Show in Explorer" brings me to the VirtualBox VMs folder in my Users folder, instead of the root of my flash drive where I moved the .vmdk file to.
I even tried following the guide (at the link above) again to move the .vmdk file back to its original folder in the VirtualBox VMs folder on my hard drive. No difference—I still got the same error.
With the .vmdk file moved back onto my hard drive, the details and settings of my broken machine and new machine are completely identical, yet one works and one doesn't at all.
Thoughts?
It seems like I would be getting that error message if I forgot to add the .vmdk file to my SAS/SATA controller, but I definitely followed all of the steps in that guide.
If additional info for troubleshooting is needed, ask away. Thanks!