Q4.2 Post Install hold until boot process finishes

[apparatus]

@Timotattyc0

He cannot get to the Qubes, with Xen hypervisor menu any more. It’s now in a reboot loop.

Maybe he’ll need this to fix the issue with missing UEFI boot entry:

BIOS Update That Will Break Boot

If you use uefi : get a qubes os media installation. boot to qubes os rescue mode. skip to shell. [shell] : efibootmgr -v -c -u -L "Qubes OS" -l /EFI/qubes/grubx64.efi -d /dev/nvme0n1 -p 1 reboot change -d <which drive?> and -p <which efi partition?>. if you want you can make sure first by issuing efibootmgr -v in dom0

@Timotattyc0

How do I mount the /boot and /boot/efi EFI System partitions in Rescue shell
It need to do a mount some type of sda1??? how do I figure that out?

First you’ll need to figure out the Qubes OS disk name.
You can use:

fdisk -l
lsblk
blkid

To figure out the available disks and partitions.
The Qubes OS disk by default should have these partitions on its disk:
part1 512 MB - EFI System - /boot/efi
part2 1024 MB - ext4 - /boot
part3 the rest of the disk size - encrypted LUKS partition with rootfs

When you know the disk name then mount the /boot and /boot/efi like this, e.g. Qubes OS disk is /dev/sda:

mkdir /mnt/boot
mount /dev/sda2 /mnt/boot
mount /dev/sda1 /mnt/boot/efi

The GRUB config should be in /mnt/boot/efi/EFI/qubes/grub.cfg or in /mnt/boot/grub2/grub.cfg.