UEFI boot: no Qubes OS option

simply add uefi entry menu by booting into your qubes os installation medium, rescue qubes os, wait and type 3 to skip shell, lsblk to examine your external ssd, if it’s /dev/sdc then run

efibootmgr -v -c -u -L "TheEnemy" -l /EFI/qubes/grubx64.efi -d /dev/sdc -p 1

-p 1 is stand for partition 1, as default in most os, partition 1 is your efi partition.

Thanks a lot, ill give it a go

This was the result

there is no sdc directory

the UEFI option disappears when I remove the SSD and plug it back in again
thanks again

sdc is just an example, you should change it to your actual drive.

^, then from your ss, your external SSD seems to be /dev/sda,

you should run
efibootmgr -v -c -u -L "TheEnemy" -l /EFI/qubes/grubx64.efi -d /dev/sda -p 1


A new UEFI option was created and after choosing it, it went through OS recovery and repair, it was trying to repair my windows and said no issue found obviously
this is so strange, why is this happening?
Do you mind video calling me or something, please? So I can fix this issue
I am prepared to pay for your time you spend in helping me
thanks a lot

boot like before, and make sure your external ssd is /dev/sda (it could change, run lsblk first, if it’s still /dev/sda then no need to change command below, if it was /dev/sdb or /dev/sdc, change the /dev/sda below to /dev/sdb or /dev/sdc).

mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/efi
cp /mnt/efi/EFI/qubes/grubx64.efi /mnt/efi/EFI/boot/bootx64.efi
cp /mnt/efi/EFI/qubes/grub.cfg /mnt/efi/EFI/boot/bootx64.cfg
efibootmgr -v -c -u -L "TheEnemy1" -l /EFI/boot/bootx64.efi -d /dev/sda -p 1

boot into your uefi settings, change the uefi order, TheEnemy is your first order, TheEnemy1 is second.


That did it
thanks a lot :smiley:

Please consider to flag the post as solution, for the sake of other users with the same issue, at least.

how do i do that please?

There should be an icon somewhere beside the “heart” icon, below @51lieal’ resolving post.

he’s not the thread starter, so can’t.

Oh I terribly apologize to both of you. I obviously overlooked who the OP was while focused on a solution itself.


Your replies have been very helpful so far.

efibootmgr -v -c -u -L “TheEnemy1” -l /EFI/boot/bootx64.efi -d /dev/sda -p 1

Unfortunately results in EFI variables are not supported on this system.
Any idea how to fix this? Thanks.

looks like you didn’t boot the recovery using uefi, check again.
or if you using debian based to recovery you need to load efivars modules.

Your commands have been very helpful, all tho I think they dont work for me, can you take a look at what commands I should do instead?

Photos: 425.8 KB folder on MEGA

When I was doing the installation I kept everyting on automatic and only put my passphrase.

I was stuck with it for a while, tried almost everything that people suggested. But none of them work.

Thanks to you for the method worked well, you are an incredible person. :fist_left:

Worked like a charm! Thanks for the help👍

I needed to create an account just to congratulate this one… Very nice. I was months trying to install qubes, this was my last attempt… Now I am logged in.


1 Like

This issue explains more about UEFI boot entries missing. There are also instructions there for fixing UEFI

  1. Mount the bootloader partition
  2. Copy the contents of /mnt/EFI/qubes/ to /mnt/EFI/BOOT/
  3. Rename grubx64.efi to bootx64.efi
  4. Rename grub.cfg to bootx64.cfg
  5. efibootmgr -v -c -u -L Qubes2 -l /EFI/BOOT/bootx64.efi -d /dev/sda -p 1

You can use such an option where you don’t have to copy grubx64.efi again every time after kernel update or changes in configuration files.

mount /dev/sda2 /mnt
mount /dev/sda1 /mnt/efi
cp /mnt/efi/EFI/qubes/grubx64.efi /mnt/efi/EFI/boot/bootx64.efi
efibootmgr -v -c -u -L "Default" -l /EFI/qubes/grubx64.efi -d /dev/sda -p 1
efibootmgr -v -c -u -L "Recovery" -l /EFI/boot/bootx64.efi -d /dev/sda -p 1
efibootmgr -o 0000 (instead of 0000, you must specify the number of the created boot record named Default so that it will be loaded first)