Then I created a virtual machine under virt-manager, importing all four of the qcow2 drives. What I tried was to export each of the above partitions as a qcow2 image, with a command like this: $ qemu-img convert -f raw -O qcow2 /dev/nvme0n1p1 win10_part1.qcow2Īnd repeated for all four partitions. Since it was setup as UEFI, it seems there are some extra steps needed to virtualize, as libvirt doesn't appear to support UEFI out of the box. Number Start End Size File system Name Flagsġ 1049kB 524MB 523MB ntfs Basic data partition hidden, diagĢ 524MB 628MB 104MB fat32 EFI system partition boot, espģ 628MB 645MB 16.8MB Microsoft reserved partition msftresĤ 645MB 500GB 499GB ntfs Basic data partition msftdata Sector size (logical/physical): 512B/512B Here's what my Windows disk looks like: $ sudo parted /dev/nvme0n1 print The tricky part here seems to be that my Windows 10 install was done through UEFI (with GPT partition table), rather than legacy BIOS MBR. I'd like to get away from dual-booting, and run my Windows 10 installation virtualized under KVM+libvirt+qemu. There are a few things for which I still need Windows, and I am currently dual-booting, with Windows and Linux on separate physical disks. The firmware will restore all required entries after reboot.Īfter a reboot and restored default BIOS options legacy devices were now being shown and didn't need to plug in two USB drives.I am migrating my PC from Windows 10 to Linux. *SOLUTION* Was able to completely fix the issue by removing all entries in the EFI NVRAM buy using the "Deleting a Boot Option" command:Īssuming the configuration in Example #1, efibootmgr -b 4 -B could be called to delete entry 4 and remove it from the BootOrder.įirst run sudo efibootmgr to get a list of all UEFI entries, then run sudo efibootmgr -b X -B in succession replacing the X with each entry shown until no entries are left.ĭeleting only the offending entries was not sufficient, all needed to be deleted. Looked into UEFI / EFI commands and learned there's a method to remove stored entries in the EFI NVRAM via Ubuntu (used Mint Linux live USB in my case) - efibootmgr. Disabling UEFI in BIOS allowed legacy USB drives to boot and vice versa. My best guess was that the NUC's EFI NVRAM got corrupted somehow.Īfter reading the work-around here regarding plugging in 2 USB drives I was able to get the NUC to now at least boot from a USB drive again and could install an OS. Tried updating BIOS to the latest firmware, pulling battery, and holding down power button but didn't fix the issue. Also noticed no legacy boot options were showing in the NUC's Visual Bios regardless if legacy boot devices were attached. In any event, I noticed anytime I plugged in a USB boot stick now it would show up as a "UEFI : USB : UEFI : USB : USB Verbatim USB device." or similar (can't remember exactly) and wouldn't boot via the USB menu. Just before this occurred I also had wiped the NVME SSD partition using GPARTED via Mint and creating a new GPT partition. Issue started occurring after attempting to install Windows 7 via the SATA port (or possibly via a Clonezilla Debian USB image). Was having the exact same issue on a new NUC5i5RYK that I received recently. Can anyone steer me in a good direction on this? Thank you in advance. I have also done an F9 Bios reset to defaults without any success. I have also tried the USB sticks in every USB port on the Nuc. I have toggled just about every setting I can find in the bios that relates to booting or to USB. I can, however, boot from a Legacy USB CD-ROM drive without issue.Īlso, when in BIOS, no boot drives show under the legacy screen, even when one is plugged into the USB port. I have confirmed that all the thumb drives I have created will boot okay on another machine, so the drives appear to be okay. If I select that, I get about a half second black screen, then I'm returned to the F10 boot options screen to try again. The drive will appear as a UEFI device: "UEFI : USB : UEFI : USB : USB DISK 2.0 PMAP : PART 0 : OS Bootloader : PART 0". When I plug in a USB Thumb Drive to boot from (Linux, Acronis Backup, Spinrite, etc), I get NO legacy boot options on the F10 screen. In BIOS, both UEFI and Legacy boot are enabled Under boot conf, USB and OPTICAL Boot devices are checked secure boot is disabled. But booting from a USB stick is a different matter. Machine boots just fine from the SSD and operates normally. Specs: Nuc Box says NUC5i3RYK Bios says "Desktop Board NUC5i3RYB" Bios Version: RYBDWi35.86A.0369.2018.0305.1050 (latest) 8GB RAM M.2 SSD. I have searched and read just about every post I can find about problems booting from USB sticks, but I can't seem to solve the problem on my Nuc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |