Getting grub menu to work on dual boot Ubuntu 22.04 Windows 11. Currently boots in a loop

Question

My Situation is the following:
I want to install Ubuntu jammy jellyfish 22.04 LTS instead of manjaro on my laptop. The laptop already had a working dual boot and so I thought replacing one Linux-system with another should not be a big problem.
While the Installation of jammy jellyfish seemed to succed, after restarting the laptop it ends up in a loop.
First it shows the normal screen it always shows before grub menu. It is a screen with some hardwaredata and the reminder to press F1 for a Bios menu.
Then it shows one mostly black screen and a message that disapers too fast to read.
After that there is another message saying "Reset system". Then it goes back to the first screen.

I can enter a menu in which there is the possiblity to choose bootmanager. If I choose "Windows 11" windows 11 starts normally. If I choose the other option begining with SAMSUNG (disk is SAMSUNG MZVLB256HBHQ-000L7(nvme)) I end up in the loop again.

Laptop: Lenovo Thinkpad T495
Earlier Installations: dual boot with Windows 11 and Manjaro KDE
Secure Boot: diabled
Istallation via: USB
Partition Table: gpt
Model SAMSUNG MZVLB256HBHQ-000L7(nvme)

I did enter sudo efibootmgr -c -g -w -L "ubuntu" -l "\EFI\ubuntu\shimx64.efi" -d /dev/nvme0n1 -p 1 while in "try Ubuntu"-mode.
The result was the following:
BootCurrent: 001B
Timeout: 0 seconds
BootOrder: 0001, 0016, 001B, 0017, 0018, 0019, 001A, 0000, 001C
Boot0000* Windows Boot Manager
Boot0010 Setup
Boot0011 Boot Menu
Boot0012 Diagnostic Splash Screen
Boot0013 Lenevo Diagnostics
Boot0014 Startup Interrupt Menu
Boot0015 Rescue and Recovery
Boot0016* USB CD
Boot0017* USB FDD
Boot0018* NVMe0
Boot0019* NVMe1
Boot001A* ATA HDD0
Boot001B* USB HDD
Boot001C* PCI LAN
Boot001D Regulatory Information
Boot001E* Boot Next Boot Option
Boot0001* ubuntu

In "Thinkpad setup -> Startup" (I think that is UEFI settings, I reached it by pressing f1 before booting) I get the following:
1 USB CD
2 USB HDD
3 USB FDD
4 NVMe0 SAMSUNG MZVL...
5 NVMe1
6 ATA HDD0
7 Windows Boot Manager
8 PCI LAN
there is no "ubuntu" entry

I tried to solve the problem by:

Installing with third party programs download enabled
Using the boot-repair tool: the tool ran for a long time, but there was no progress recognizable (even when I started it in debug mode)
You can find the report under https://paste.ubuntu.com/p/pWmbMzN959 (Also because of some other attempts to get the dual boot to work, nvme0n1p5 now is called nvme0n1p6)
Current report: https://paste.ubuntu.com/p/Wj6MJFSvbD
I let boot-repair tool run again, but it still didn't do anything.

Any help with this would be greatly appreciated.

You should have an Ubuntu entry. And the drive entry is a fallback boot entry using /EFI/Boot/bootx64.efi similar to live installer's boot. But bootx64.efi may be the Windows boot file, the manjaro boot file, or grub/shimx64.efi from ubuntu's install. But it looks like Ubuntu's grub never correctly installed. Can you run report from Boot-Repair? If not you can try to chroot into system & reinstall grub or make other repairs.UEFI chroot, must include ESP - efi system partition http://askubuntu.com/questions/53578/can-i-install-in-uefi-mode-with-the-alternate-installer/57380#57380 — oldfred, Apr 24 '22 at 14:42
I got an URL from boot-repair: https://paste.ubuntu.com/p/pWmbMzN959 is this helpful? — BranAndSceolan, Apr 24 '22 at 15:09
Not sure what hidden ESP is? Do you have a setting in UEFI that locks ESP? Some Lenovo have this: The Device Guard BIOS setting locks down the boot order to internal HDD/SSD only. You show /EFI/ubuntu from a grub install, but no UEFI boot entry in UEFI. Have you updated UEFI & SSD firmware? Many Lenovo need UEFI update. Does this give any error messages: sudo efibootmgr -c -g -w -L "ubuntu" -l "\EFI\ubuntu\shimx64.efi" -d /dev/nvme0n1 -p 1 — oldfred, Apr 24 '22 at 17:04
I don't know much about all the UEFI at all, so I dont know what's going on there. If there is a setting that locks ESP, wouldn't it already be disabled because there was a successful manjaro installation before? I don't know how to Update my firmware. — BranAndSceolan, Apr 24 '22 at 18:03
@oldfred The result of the command you gave me does not seem to be a error or warning, but I am going to add the result to the question — BranAndSceolan, Apr 24 '22 at 18:05
You now have boot entry 0001 as default. On a reboot can you choose that? — oldfred, Apr 24 '22 at 19:07
@oldfred I do not know how to choose it on a reboot. By pressing f12 I end up in a boot menu but he boot menu shows only Windows and SAMSUNG MZVB... and PCI LAN as Options. — BranAndSceolan, Apr 25 '22 at 07:03
Some systems require you to change boot order in UEFI settings, not UEFI boot menu. Or enable trust on the Ubuntu setting with Secure boot on and/or UEFI password. If you have to set UEFI password never lose it, or reset to blank when done. Does booting the Samsung drive boot? — oldfred, Apr 25 '22 at 12:51
Booting the SAMSUNG drive leads to the loop. If I do nothing (press no f1 or f12) I end up there. — BranAndSceolan, Apr 25 '22 at 13:07
@oldfred So you think I should turn on secure boot, did I get that right? — BranAndSceolan, Apr 25 '22 at 13:11
In "Thinkpad setup" (I think that is UEFI settings) I get the following 1 USB CD 2 USB HDD 3 USB FDD 4 NVMe0 SAMSUNG MZVL... 5 NVMe1 6 ATA HDD0 7 Windows Boot Manager 8 PCI LAN there is no "ubuntu" entry. — BranAndSceolan, Apr 25 '22 at 13:13
If you have UEFI Secure Boot on, you have to install or upgrade Ubuntu to have signed grub & kernel. And you have to manually sign any proprietary drivers like nVidia (if you have that) as Ubuntu cannot sign proprietary drivers. Often easier with signed off. I do not understand why Boot-Repair is taking so long. While it can take a couple of minutes on my system with two drives and multiple installs, it should not take that long. — oldfred, Apr 25 '22 at 15:00
@oldfred I have found a solution now. Thank you very much for trying to find one. — BranAndSceolan, Apr 25 '22 at 19:23

Nipuna · Answer 1 · 2023-10-06T10:50:19.367

6

Ubuntu 22.04 comes with Grub 2.06 and on this version, the OS Prober is set to 'disable' by default which means you won't find the other OSes such as Windows on the Grub prompt as before. So here's a workaround.

Open grub config file,

sudo gedit /etc/default/grub

Then add this line

GRUB_DISABLE_OS_PROBER=false

Save the file and then run the following command:

sudo update-grub

Finally, reboot the system. You'll see the rest of the OSes on the Grub prompt.

Source: OMG! Ubuntu!

Edit

If this still didn't fix your issue, try to fix the Grub using boot-repair on a live session.

sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update

then

sudo apt-get install -y boot-repair && boot-repair

edited Oct 06 '23 at 10:50

answered Apr 24 '22 at 14:25

Nipuna

193
8

I just tried this. It didn't change the situation. My problem isn't that I don't see the windows os. I don't even get to the grub prompt. It just starts looping. – BranAndSceolan Apr 24 '22 at 14:59
1

Have you tried to fix the Grub using boot-repair on a live session?
sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update then sudo apt-get install -y boot-repair && boot-repair
– Nipuna Apr 25 '22 at 09:05
Yes, I did that. It is how I got the reports. It ran a while, but didn't show any progress in the debug messages. – BranAndSceolan Apr 25 '22 at 09:26
@Nipuna You gave the correct answer. But it cannot be repaired within the OS itself. You have to boot with the ISO on live CD, install the boot-repair program and fix the problem – acgbox Apr 26 '22 at 14:40
1

@acgbox Hey thanks. Yeah, that's what I meant by "on a live session". As per the OP's own answer, it appears he/she had a different issue with the BIOS settings, which is completely irrelevant to the Grub. – Nipuna Apr 27 '22 at 08:02

BranAndSceolan · Accepted Answer · 2022-04-26T05:28:52.753

2

Turns out there is an option called "Boot Order Lock" in the Thinkpad Setup on the tap "Startup". Disabling it solved the problem.

The Startup menu. Option "Boot Order Look" is chosen and set to "disabled":

edited Apr 26 '22 at 05:28

answered Apr 25 '22 at 19:21

BranAndSceolan

51

score 0 · Answer 3 · answered Apr 25 '22 at 14:35

Try downloading the USB flash drive (or CD-R, if you have an optical drive) version of rEFInd. Write it to a USB flash drive (or CD-R) and try booting it. If it boots, it will probably show at least two Ubuntu options, one of which boots to GRUB and the other of which boots a Linux kernel directly. If either of them works, and if rEFInd's Windows option also works, you could try installing rEFInd to your hard disk, ideally via the Debian package or PPA. If this is successful, you'll boot via rEFInd, rather than GRUB, going forward.

The point of the above is to bypass GRUB, which seems to be misbehaving on your computer. Fixing GRUB is obviously another option, but I don't see any glaringly obvious configuration problems, so I have no suggestions for that approach.

I did follow the directions in rEFInd-README. Sadly I still did end up in the loop. I then tried finding rEFInd in the boot settings, and did not find it. My USB Stick appeared in the Boot Menu after pressing f12, but choosing it and pressing enter lead only to me reentering the boot menu. I am not sure what went wrong. — BranAndSceolan, Apr 25 '22 at 15:17

Getting grub menu to work on dual boot Ubuntu 22.04 Windows 11. Currently boots in a loop

3 Answers3

Edit

Linked