[SOLVED] Have to bring up GRUB menu after every boot- how to fix?

dudeguy1337 · 03-11-2022, 07:58 PM

SOLVED EDIT: I got systemd-boot working instead of GRUB by nuking Pop!_OS and following these (not very beginner-friendly) guides: Installing Pop!_OS Getting systemd-boot to work Unfortunately I cannot figure out how to mark this post as [SOLVED] because the option is not in "Thread Tools" for some reason :/
https://i.imgur.com/LrO0MED.jpg

The gist:
I'm having some unusual trouble with GRUB. Every time I boot my computer, it opens to the GRUB command line. I have to run the following commands:

Code:

set root=(hd0,msdos1)
set prefix=(hd0,msdos1)/boot/grub
insmod normal
normal

which brings me to a perfectly-formed GRUB menu, like this one, but with Windows on it:
https://i.imgur.com/ZiO2qxH.png
How can I make it so that it opens the GRUB menu automatically?

Details:
I am dual-booting Windows 10 and Pop!_OS. I originally had Linux Mint. But I replaced Linux Mint with Pop!_OS after I messed up my GRUB using Grub-customizer and boot-repair made it even worse.
I have tried using sudo update-grub and sudo grub-install but those didn't fix anything.
When I run efibootmgr -v I get:

Code:

BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0002,0004,0005,0003,0001,0000,2001,2002,2003
Boot0000* ubuntu	HD(1,GPT,94c134fa-a93c-490c-8d82-595be9e6f9a9,0x800,0x32000)/File(\EFI\ubuntu\grubx64.efi)
Boot0001* Unknown Device: 	HD(1,GPT,94c134fa-a93c-490c-8d82-595be9e6f9a9,0x800,0x32000)/File(\EFI\ubuntu\shimx64.efi)RC
Boot0002* pop	HD(4,GPT,7e403a8e-888c-4570-8cb9-7fe467967a79,0x1d7de800,0x1fffff)/File(\EFI\pop\grubx64.efi)
Boot0003* Windows Boot Manager	HD(1,GPT,94c134fa-a93c-490c-8d82-595be9e6f9a9,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...o................
Boot0004* Pop!_OS 21.10	HD(4,GPT,7e403a8e-888c-4570-8cb9-7fe467967a79,0x1d7de800,0x1fffff)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0005* HDD0: INTEL SSDPEKKW256G7	PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-00-00)/HD(4,GPT,7e403a8e-888c-4570-8cb9-7fe467967a79,0x1d7de800,0x1fffff)RC
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

I have tried moving these around in the UEFI boot manager to varying success. (I will upload a screenshot soon.)

Thanks in advance! I hope this is the right sub-forum

mrmazda · 03-12-2022, 04:44 PM

Try using efibootmgr to rearrange BootOrder to make Boot0004 first instead of Boot0002. man efibootmgr

If it works, use efibootmgr to remove the "ubuntu" and "pop" entries.

colorpurple21859 · 03-12-2022, 04:46 PM

open a terminal

Code:

sudo efibootmgr -n 0000

reboot, change to 0002 or 0004 if needed to see which one brings up the correct boot menu.
to change the boot order, something similar to this:

Code:

sudo efibootmgr -o 0004,0000,0005,0003,0001,0002,2001,2002,2003

computersavvy · 03-12-2022, 06:32 PM

Is windows installed as efi or mbr boot?
Is the drive partitioned as msdos or gpt?

Using the command the way you do

Code:

set root=(hd0,msdos1)
set prefix=(hd0,msdos1)/boot/grub

seems to indicate the drive is partitioned in msdos mode which would indicate that windows is doing an MBR boot and you should have installed Pop OS in mbr boot mode.

However, all the efibootmgr entries shown reflect GPT, so I am a bit confused why your command does not reflect gpt such as

Code:

set root=(hd0,gpt1)
set prefix=(hd0,gpt1)/boot/grub

With that said, you might reinstall the kernel with grub properly configured so the vmlinuz image properly reflects the boot mode and config. On fedora we have tools called grubby and dracut to handle the reconfig of the boot image and kernel parameters when changes occur. I am not familiar with pop os so cannot tell how to do similar for that OS.

After thinking a bit more, I wonder if windows is efi booting and you created an additional efi partition when you installed Pop OS. If so then there will be an issue with booting from one efi partition (the one shown as EFI System by fdisk -l) and the second one created by pop os.

dudeguy1337 · 03-12-2022, 07:18 PM

Sorry guys, this thread didn't show up for me for a long time, so I couldn't post any updates. Since I posted it I just nuked POP!_OS (it was a fresh install) and got systemd-boot working instead of GRUB using these guides:
Installing Pop!_OS
Getting systemd-boot to work

Unfortunately, neither of them are very beginner-friendly.
Thanks for all your help anyway!