Unwanted grub menu bypass

misam · October 20, 2025, 9:56am

I once plugged the disk with my endeavouros/xubuntu to my computer after I have pressed the turn on button. Now, each time I turn on the computer, the grub is bypassed and ubuntu is booted automatically. I can access grub menu by spamming shift key and then I can choose the system. I have installed my grub along with endeavouros. I already checked the grub config file, ran grub-mkconfig and dracut-rebuild, but the situation is still the same. I don’t know much how to work it out myself.

This is the output of efibootmgr -v:

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0004,2001,2002,2003
Boot0000* ubuntu	HD(1,GPT,f854bdb3-1b8c-4dfd-9498-e741563ae941,0x800,0x113000)/\EFI\ubuntu\shimx64.efiRC
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 30 11 00 00 00 00 00 b3 bd 54 f8 8c 1b fd 4d 94 98 e7 41 56 3a e9 41 02 02 / 04 04 34 00 5c 00 45 00 46 00 49 00 5c 00 75 00 62 00 75 00 6e 00 74 00 75 00 5c 00 73 00 68 00 69 00 6d 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 52 43
Boot0004* Windows Boot Manager	HD(1,GPT,8d060131-9319-4f02-ae7f-87f6848d170d,0x800,0x82000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000066000100000010000000040000007fff0400
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 08 00 00 00 00 00 31 01 06 8d 19 93 02 4f ae 7f 87 f6 84 8d 17 0d 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 66 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot2001* EFI USB Device	RC
      dp: 7f ff 04 00
    data: 52 43
Boot2002* EFI DVD/CDROM	RC
      dp: 7f ff 04 00
    data: 52 43
Boot2003* EFI Network	RC
      dp: 7f ff 04 00
    data: 52 43

and lsblk:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0 931.5G  0 disk 
├─sda1        8:1    0   550M  0 part /boot/efi
├─sda2        8:2    0  39.1G  0 part 
├─sda3        8:3    0 410.2G  0 part 
├─sda4        8:4    0  39.1G  0 part /
├─sda5        8:5    0 410.2G  0 part /home
├─sda6        8:6    0  15.6G  0 part [SWAP]
└─sda7        8:7    0  15.6G  0 part 
sdb           8:16   1   239G  0 disk 
└─sdb1        8:17   1   239G  0 part 
nvme0n1     259:0    0 953.9G  0 disk 
├─nvme0n1p1 259:1    0   260M  0 part 
├─nvme0n1p2 259:2    0    16M  0 part 
├─nvme0n1p3 259:3    0 951.6G  0 part 
└─nvme0n1p4 259:4    0     2G  0 part

Thanks for any help

cactux · October 20, 2025, 10:59am

Can you still boot into your EOS?

I don’t see any boot entry for endeavours in the output of efibootmgr.

Where is your EOS installed? What partitions, ESP and /? What filesystem?

misam · October 20, 2025, 11:22am

Yeah, with Shift I can access the grub menu and then it works like it would typically would, just the Shift key has to be pressed.

I am not 100% sure that it is not somehow hidden under the ubuntu boot entry. This is my first triple boot with EOS and Xubuntu on separate drive from Windows. I first installed Xubuntu without grub and then I installed EOS with grub. After that i reordered the boot entry in bios and (as I said I am not 100% sure), it was named ubuntu T7. And everything worked perfectly. But today it broke.

The partition are:

sda1 … /boot/efi (fat32)

sda2 … root for Xubuntu (ext4 - all following)

sda3 … home for Xubuntu

sda4 … root for EOS

sda5 … home for EOS

sda6 … swap for Xubuntu

sda7 … swap for EOS

cactux · October 20, 2025, 11:37am

I propose this, from inside your EOS:

sudo grub-install --efi-directory=/boot/efi --bootloader-id=endeavouros

Then inside /etc/default/grub make sure you have this line:

GRUB_DISABLE_OS_PROBER=false

After that:

sudo grub-mkconfig -o /boot/grub/grub.cfg

Most probably, you have the package grub (whatever the name is in Ubuntu) still installed in the system even though you didn’t installed the bootloader.

My experience from a dualboot with Ubuntu is that when the package grub was updated in the system, it used to put its boot entry in BIOS on top.

It seems that similar thing may have happened in your system. What happened to your EOS’ boot entry, I don’t know.

misam · October 20, 2025, 2:35pm

I have followed your instructions and it is working seamlessly now. Huge thanks!

cactux · October 20, 2025, 3:27pm

The fact that you had an EFI boot entry in BIOS made me think that despite installing Xubuntu without Grub bootloader, the base installation still contains Grub packages that once updated will run the grub-install command through a hook or post-install script. That is most probably why you have:

This could happen again in a future update to the package grub in Xubuntu. I suggest you look into removing the relevan packages. Do some research in that direction.

misam · October 20, 2025, 4:56pm

Time will tell. I’ll keep an eye on that. This time the issue wasn’t caused by updating Xubuntu packages. In fact I haven’t booted Xubuntu in a week or so and been using EOS daily.

Yesterday it worked fine and today in the morning I turned on my laptop and in a fraction of a second I remembered I haven’t plugged in the drive with EOS/Xubuntu. I did so as fast as possible. Anyway it booted defaultl windows (as expected, because it jumped up as the new first boot entry). I then restarted the laptop, opened bios, choosed the ubuntu T7 option as first, saved, exited and it booted Xubuntu without grub menu.

I really don’t want you to bother with trying to work out the root cause, but you seemed you were thinking about it even after I marked your answer as solution, so I am giving you some info…

I will now remember not to forget plugging my drive before booting Early mornings are hell

system · October 22, 2025, 4:57pm

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.