Note that my viBoot clearly states that this image is bootable. I have VirtualBox on one machine and viBoot has no problem creating a VM from a similar EFI/GPT image. Support forums post: ViBoot - No bootable drive detected Has anyone here encountered this? Maybe it's a bug, or maybe I'm missing something? I'd hate to have to restore a backup and have it fail due to an underlying issue, hence I'm eager to understand what is going on. I did post this on the Macrium forums, but no joy there so far.ĭespite the error, everything appears to be working fine but it is rather worrying. This happens with images on my second M.2 drive and external drives, so it doesn't seem to be drive specific. Strangely, if I click OK, it gives me the option to create the machine, I can change memory etc and it does boot. I'm using Macrium viBoot with VirtualBox, however when I try to use any of my backup images as a VM I get the error pop up "No bootable drive detected" as shown here: Lenovo_13_Disk_Restore Lenovo_13_Disk_Restore.jpg (89.93 KiB) Viewed 3851 times Lenovo_13_disk Lenovo_13_disk_2.jpg (74.I wasn't sure which thread to put this in, Backup or Virtualization? Since it's Macrium related, posting here seemed best, but please move it if need be. I found that TBOSDT copyp2v.tbs script video, I want to make sure that the correct partition is active first before removing drivers/changing HAL. *If I assumed correctly, how would I change the active partition within TBLauncher, is it one of the scripts in TeraByte OSD Tool? I assume that if the HAL or drivers were wrong I would get a BSOD instead of the current error about no bootable medium found.
The attached Lenovo_13_Disk_Restore shows Image for Windows, 5 partitions to restore, however it shows the system 100MiB being **active**, shouldn't the Windows 120759MiB be *active*? The attached Lenovo_disk shows the disk layout from Computer Management, it shows 4 partitions, 117GB partition being Boot. I did the restore, however when I attempt to boot it said "FATAL: No bootable medium found! System halted."
0 kommentar(er)
