Missing boot entry after shutdown

[Rnd3sB3g13rng]

Hello,
I need help urgently and would appreciate any tips.
I have two hard drives on my computer. One 250gb ssd and a 1tb ssd. On the smaller one I installed qubes for testing purposes and then switched to the 1tb for daily work.

Today my computer first froze and then shut down. It automatically tried to reboot and I got this error message:

After waiting for a while I shut down the computer again and on the next reboot it bootet into the 250gb ssd. Rebooting and looking into the boot menu gave me

So the boot entry is completely missing. When I try to boot from the 1tb ssd I get

I appreciate any help! I don’t really know what to do and I don’t want to accidentally delete my data (if it is still available…).

Thanks in advance!

[TheGardner]

Qubes created a new entry Qubes (M.2_1…250) and thats the one Qubes is using, regardless if there are some other entries, which point to SSD drives. I’m afraid you have to edit the grub configuration with a second entry called somewhat Windows (M.2_2 …) to get this available in a boot menu.

But I can’t tell you, how exactly this should be done. So please wait for some more repies here. Guess some other people can help you edit the boot configuration.

[fsflover]

Perhaps these could be helpful:

Cannot boot from SSD after installing a secondary Qubes to a USB disk

I’ve installed Qubes to a USB from a computer that already had Qubes on its SSD. Now I can no longer boot to the SSD because the boot option doesn’t show up. Inspecting the SSD all the files and partitions seem to be intact. I think it is probably just that the EFI partition or a file on it has been marked as not bootable? I’ve tried the Qubes rescue tools but they didn’t work. What’s the easiest way to make Qubes boot from the SSD again?

Cannot boot after fresh install

I proceeded all the way through the installation only for it to spit out this whenever I pushed reboot at the end. [IMG_20220303_033642155_HDR]

Installed Qubes on secondary SSD; boots into first drive

i one had a somewhat similar issue… -years a go an not exactly so… but the issue i had was a corrupt “broken” mbr which basically go ignored by the uefi/bios would work if “forced” but whenever there was another gpt drive th system will just automaticlly boot the gpt drive soled this by completly repartitioning and repairing the mbr was a bit of a pain in the ass for a number of reasons… ()first it was a pretty big drive and i had to backup everything -and well had other issues corruption d…

No Boot Device Found

After booting once into a Kali Live flash drive, I shut down and removed the flash drive. My Qubes install is not detected now. I changed absolutely nothing, BIOS or otherwise. My M.2 PCIe SSD is detected in BIOS, but the Qubes install on it is not. Any suggestions?

"No bootable device found" After completing qubes os install

After completing installation for qubes 4.1 beta, I am greeted with the “no bootable devices found” after reboot. I’ve had this problem when installing 4.0.4, and I think I got around it by doing another install; but this does not appear to be a viable solution in this case (6th install, same problem). I noticed docs in the UEFI Troubleshooting page mentioning this error, but I do not see these files, how I am supposed to accomplish those changes. I’ve tried using the troubleshooting part ava…

Booting Qubes from Internal SSD (ICYDOCK) on Multiple Devices No Longer Works

I have 4 identical PC’s on which I move my Qubes-installed SSD around between them. It has worked great until version 4.0.3. With 4.0.4 I can only run Qubes on the PC on which I had the SSD during installation. Does the latest version of Qubes for security reasons check a serialnumber in the motherboard or CPU? If so; can I deactivate that function?

[Rnd3sB3g13rng]

Thanks for the quick reply!
I booted into rescue mode from a qubes4.1 bootstick, entered the shell and typed

efibootmgr -v -c -u -L QubesOS -l /EFI/qubes/grubx64.efi -d /dev/nvmen1 -p 1

That did it!