[HELP] Failed unmounting run-install-repo.mount during reboot after installation

[Azurea]

Firstly, English is not my first language. Sorry if there is any strange grammar in the mix.
Since yesterday I have been trying to install Qubes-R4.2.2-x86_64 on an SSD connected via SATA, but after installation I cannot boot successfully.
After the installation was finished, I checked the UEFI and saw Qubes OS and UEFI OS in the Boot device. However, when I select it and try to boot, nothing happens. After changing the priority and rebooting, the Qubes OS disappears and only the UEFI OS appears. This is very strange.
I checked UEFI troubleshooting and tried all the contents, but finally could not boot.
Finally, I confirmed that the error with the content of the topic title(Failed unmounting run-install-repo.mount) appears only momentarily during the reboot.
Does anyone have any insight into this problem? I would like some help.

Device
SSD: THNSNF128GCSS
CPU: Intel Core i7-12700K
MotherBoard: TUF GAMING Z790

[apparatus]

@Azurea

However, when I select it and try to boot, nothing happens.

Can you describe it in more details?
When you try to boot the UEFI entry then the GRUB menu doesn’t appear?

[Azurea]

Thank you for your reply.

@apparatus

When you try to boot the UEFI entry then the GRUB menu doesn’t appear?

Yes, the GRUB menu does not appear.
The Qubes OS is correctly displayed in the Boot Option section, as shown in the image.

However, when I try to boot with Boot Override, the screen only flashes for a moment and does not boot.
Also, rebooting in this state will not boot anything and will return to UEFI.

[Azurea]

I don’t know if this is relevant, but this image is the Failed that is displayed before rebooting after installation.

[apparatus]

Do you have Secure Boot disabled in BIOS?
And how did you partition your disk in the Qubes OS installer?

[Azurea]

I have confirmed that BOOT->Secure Boot->OS Type is set to Other OS. Secure Boot should now be disabled.
All partitions were removed from the SSD beforehand and installed with Strage Configuration set to Automatic.

[apparatus]

Did you use the whole SSD for Qubes OS installation?

There seems to be some 64 GB partition on this disk:

@Azurea

Can you boot from some other Linux OS (e.g. from some Live USB like gparted) and check the partition table of this disk?
Or you can boot the Qubes OS installer and switch to the console in another TTY using Ctrl+Alt+F2 and check the output of this command:

fdisk -l

Check that EFI System partition is present and check its content.

[Azurea]

@apparatus

Did you use the whole SSD for Qubes OS installation?
There seems to be some 64 GB partition on this disk:

Sorry, that 64GB disk is the Qubes OS installer USB, it shows up there because I did not unplug it before going to UEFI.
After installation the disk will be the one labeled THNSNF128GCSS.

I will add a picture of it later running fdisk -l

[imboxm]

Hello, I think it will be good …more exchange( on Forum) …about the hardware …which works good with QUBES ( diffrent versions).imboxm
ps:follow my experience …several installation on external ( SSD, NVMe ) not work.Until I use only on internal drive …which I exchange to test versions.Thanks for attention.

[apparatus]

The disk is partitioned correctly.
Check the content of the EFI System partition in the Qubes OS installer console using these commands:

mkdir /tmp/mnt
mount /dev/sda1 /tmp/mnt
ls -l /tmp/mnt/EFI/*

[Azurea]

@imboxm

ps:follow my experience …several installation on external ( SSD, NVMe ) not work.Until I use only on internal drive …which I exchange to test versions.Thanks for attention.

Thank you for your reply.
My SSD is connected via SATA, so I guess it falls under internal drives.

[Azurea]

Here is the result of the command execution.

Also, I have attached a video of the phenomenon that only the UEFI OS remains in the Boot Option and does not boot even if it is selected, only flashing for a moment.

UEFI

[apparatus]

The files in EFI System partition are also correct.
I guess there is a problem with UEFI configuration, but I don’t know what could cause this.
Try to add the EFI boot entry manually and point to the grubx64.efi file in the Qubes OS EFI System partition. Then try to boot this entry.
You should be able to do this in the “Boot configuration” here:

@Azurea

Maybe you can also try to disable “Intel Rapid Storage Technology”, change the SATA Storage mode from RAID to AHCI and disable Intel Volume Management Device (VMD) in UEFI.

[Azurea]

Sorry for the late reply.

@apparatus

Try to add the EFI boot entry manually and point to the grubx64.efi file in the Qubes OS EFI System partition. Then try to boot this entry.
You should be able to do this in the “Boot configuration” here:

I could not find such a setting in the Boot configuration of the UEFI. Is it possible to do this from Installer? I would like to get more information.

@apparatus

Maybe you can also try to disable “Intel Rapid Storage Technology”, change the SATA Storage mode from RAID to AHCI and disable Intel Volume Management Device (VMD) in UEFI.

From the Youtube video you can see that Intel Rapid Storage Technology is marked Off and it is in AHCI mode, I also checked the VMD and it was set to Disable.

[apparatus]

@Azurea

I could not find such a setting in the Boot configuration of the UEFI. Is it possible to do this from Installer? I would like to get more information.

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

[Azurea]

Apparently my hardware may not be compatible. I will purchase another hardware. Thanks for your enthusiastic support.