I am unsure if this is primarily an issue with Qubes or the Anaconda installer.

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.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2101ef84-7a2a-4b4b-8cbd-75ed282e855b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to