USB installer did not use existing EFI system partition on NVME drives
jay...@gmail.com
Issue observed while installing in UEFI mode. BIOS was set to use AHCI (otherwise, the "nvme disk" is not reported to the installer or the live usb I used to look at the disk contents).
Manual partitioning does not appear to recognize an existing EFI partition on an "nvme disk" (1) as an EFI partition (error message "No valid bootloader target device found..." (2)).
Installing anyway results in no Qubes boot option on reboot. (3)
Running efibootmgr -v from a live usb reports a Qubes entry at VenHw (instead of a HD).
The laptop I used also had a non-nvme disk, and accepting automatic partitioning put a new esp on that disk instead. The install completed successfully with automatic partitioning. I have observed no issues with the installed Qubes system so far.
(1) the disk is reported as nvme0n1 during the manual parition process.
(2) "No valid bootloader target device found. See below for details. For a UEFI installation, you must include an EFI system partition on a GPT-formatted disk, mounted at /boot/efi"
(3) I am unsure if this is relevant, but the installation process does write a "qubes" folder to the ESP partition on the nvme disk. On my first installation attempt, the write was corrupted, and trying to read the files through a live usb reported "fat_get_cluster: invalid cluster chain (i_pos 0)". Later attempts did not result in such an error, though no attempt resulted in a working Qubes boot option.
jay...@gmail.com
I attempted installing the same Qubes image again using an nvme partition for /boot/efi. Though the installed system did not work initially, I was able to create a working entry for /boot/efi/xen.efi with efibootmgr.