Missing entries in the grub-menu after upgrade (zypper dup)

norrin · July 19, 2026, 1:17pm

Hi!
This year i went from microsoft to 100% opensuse.
No more dual boot anymore.

Took and still takes a long time to configure everything and find alternatives for ervery task but a am really glad i did it. A lot of software works BETTER than the stuff i used on windows 11.
Feels so minimalistic and clean and there are only a few gaps i still have to close.

Unfortunately i did not yet install something like “timeshift” and my last upgrade (zypper dup) seems to went bad.

After reboot i only have one grub-menu-entry: UEFI firmware.
The opensuse-entry disappeared.

I tried hours with the help of ai to get it work again, but it seems that i need human help.

What i did/tried:
Using the rescue-system, i tried to install grub again with
grub2-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=opensuse
and
grub2-mkconfig -o /boot/grub2/grub.cfg
No errors but the grub menu did not change at all.

In my UEFI i have opensuse-secureboot as an option, but it only brings me to the grub-menu with the one UEFI-firmware-entry.

Any ideas how to get my openSUSE back to life?

nrickert · July 19, 2026, 1:34pm

It is not at all clear what you actually did.

If you are using the install media, there is an option to boot a linux system. If you use that, instead of the rescue system, you might actually be able to get into your system. And then try repairing the grub menu from there.

malcolmlewis · July 19, 2026, 1:37pm

One question, when did you perform the Tumbleweed install as the default now is systemd-boot?

You didn’t delete any files in the /boot/efi directory?

norrin · July 19, 2026, 1:40pm

Yes, i tried this but it said: “No bootable system found”, so i went with the exhausting* rescue system

*I mean the mounts and binds of the directories before using chroot

norrin · July 19, 2026, 1:42pm

The upgrade was finished except the grub-stuff because the boot-partition is only 100MB and was full.
So i deleted the oldest kernel (6.XXX) and kept the 2 newer ones (both 7.XXX).
That’s all.

Forget to answer the first question:
I installed opensuse tumbleweed in january (2026).

malcolmlewis · July 19, 2026, 1:56pm

@norrin But no kernels exist in /boot/efi do you have a separate /boot partition?

And you are using UEFI boot, not legacy boot?

Can you boot from a Tumbleweed Rescue USB (it runs XFCE) and paste the output from lsblk -f

norrin · July 19, 2026, 2:15pm

There is a live-cd?
Should have read the download parts carefully.
You are right:
https://en.opensuse.org/openSUSE:Tumbleweed_installation#LiveCDs/Rescue_CD
That’s great. I will configure internet and write and paste from there.
One moment please

norrin · July 19, 2026, 2:43pm

So yes, it is a boot partition of 100MB
I use a modern mini pc from bosgame.
I guess it is an uefi, but i am not sure how to verify. There are only a few options. Could not find something like legacy.

In the boot-menu of the UEFI are points like UEFI: opensuse-secureboot and still the UEFI: windows-bootmanager (although the windows is gone).

linux@localhost:~> sudo lsblk -f
NAME FSTYPE FSVER LABEL                         UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
     squash 4.0                                                                            0   100% /run/overlay/rootfsbase
                                                                                                    /run/overlay/squashfs_container
sda  iso966 Jolie openSUSE_Tumbleweed_Rescue_CD 2026-06-03-08-13-53-00                              
├─sda1
│    iso966 Jolie openSUSE_Tumbleweed_Rescue_CD 2026-06-03-08-13-53-00                     0   100% /run/overlay/live
├─sda2
│    vfat   FAT16 BOOT                          4BCB-48F3                                           
└─sda3
     ext4   1.0   cow                           3d9959db-9800-4a98-b081-df15c58a664e    5.8G     4% /run/overlay/overlayfs
nvme0n1
│                                                                                                   
├─nvme0n1p1
│    vfat   FAT32 SYSTEM                        B6F2-0FCD                                           
├─nvme0n1p2
│    btrfs                                      3e917c96-d733-4375-9b39-11890b14152f    1.3T    29% /run/media/linux/3e917c96-d733-4375-9b39-11890b14152f
└─nvme0n1p3
     swap   1                                   50a7ce19-65c2-410b-9c9d-e470f6420e70                
linux@localhost:~>

malcolmlewis · July 19, 2026, 3:07pm

So if you mount the partition, mount /dev/nvme0n1p1 /mnt then ls -R /mnt and show the output.

norrin · July 19, 2026, 3:10pm

linux@localhost:~> ls -R /mnt/boot
/mnt/boot:
dev  loader               proc  sys
EFI  opensuse-tumbleweed  run   System Volume Information

/mnt/boot/dev:

/mnt/boot/EFI:
Boot  Microsoft  opensuse

/mnt/boot/EFI/Boot:
BOOTX64.EFI  fallback.efi  MokManager.efi

/mnt/boot/EFI/Microsoft:
Boot  Recovery

/mnt/boot/EFI/Microsoft/Boot:
BCD           es-MX           kd_02_1969.dll       qps-ploc
BCD.LOG       et-EE           kd_02_19a2.dll       qps-plocm
BCD.LOG1      fi-FI           kd_02_1af4.dll       Resources
BCD.LOG2      Fonts           kd_02_8086.dll       ro-RO
bg-BG         fr-CA           kd_07_1415.dll       ru-RU
bootmgfw.efi  fr-FR           kd_0C_8086.dll       SecureBootRecovery.efi
bootmgr.efi   hr-HR           kdnet_uart16550.dll  sk-SK
BOOTSTAT.DAT  hu-HU           kdstub.dll           sl-SI
boot.stl      it-IT           ko-KR                sr-Latn-RS
CIPolicies    ja-JP           lt-LT                sv-SE
cs-CZ         kd_02_10df.dll  lv-LV                tr-TR
da-DK         kd_02_10ec.dll  memtest.efi          uk-UA
de-DE         kd_02_1137.dll  nb-NO                winsipolicy.p7b
el-GR         kd_02_1414.dll  nl-NL                zh-CN
en-GB         kd_02_14e4.dll  pl-PL                zh-TW
en-US         kd_02_15ad.dll  pt-BR
es-ES         kd_02_15b3.dll  pt-PT

/mnt/boot/EFI/Microsoft/Boot/bg-BG:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/CIPolicies:
Active

/mnt/boot/EFI/Microsoft/Boot/CIPolicies/Active:
{5DAC656C-21AD-4A02-AB49-649917162E70}.cip
{82443e1e-8a39-4b4a-96a8-f40ddc00b9f3}.cip
{CDD5CB55-DB68-4D71-AA38-3DF2B6473A52}.cip

/mnt/boot/EFI/Microsoft/Boot/cs-CZ:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/da-DK:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/de-DE:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/el-GR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/en-GB:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/en-US:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/es-ES:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/es-MX:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/et-EE:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/fi-FI:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/Fonts:
chs_boot.ttf  malgun_boot.ttf   msjh_boot.ttf   segmono_boot.ttf
cht_boot.ttf  malgunn_boot.ttf  msjhn_boot.ttf  segoen_slboot.ttf
jpn_boot.ttf  meiryo_boot.ttf   msyh_boot.ttf   segoe_slboot.ttf
kor_boot.ttf  meiryon_boot.ttf  msyhn_boot.ttf  wgl4_boot.ttf

/mnt/boot/EFI/Microsoft/Boot/fr-CA:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/fr-FR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/hr-HR:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/hu-HU:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/it-IT:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/ja-JP:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/ko-KR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/lt-LT:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/lv-LV:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/nb-NO:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/nl-NL:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/pl-PL:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/pt-BR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/pt-PT:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/qps-ploc:
memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/qps-plocm:
memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/Resources:
bootres.dll  en-US  fr-FR  ja-JP  pt-PT  zh-CN
de-DE        es-ES  it-IT  ko-KR  ru-RU

/mnt/boot/EFI/Microsoft/Boot/Resources/de-DE:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/Resources/en-US:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/Resources/es-ES:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/Resources/fr-FR:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/Resources/it-IT:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/Resources/ja-JP:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/Resources/ko-KR:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/Resources/pt-PT:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/Resources/ru-RU:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/Resources/zh-CN:
bootres.dll.mui

/mnt/boot/EFI/Microsoft/Boot/ro-RO:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/ru-RU:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/sk-SK:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/sl-SI:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/sr-Latn-RS:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/sv-SE:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/tr-TR:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/uk-UA:
bootmgfw.efi.mui  bootmgr.efi.mui

/mnt/boot/EFI/Microsoft/Boot/zh-CN:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Boot/zh-TW:
bootmgfw.efi.mui  bootmgr.efi.mui  memtest.efi.mui

/mnt/boot/EFI/Microsoft/Recovery:
BCD  BCD.LOG  BCD.LOG1  BCD.LOG2

/mnt/boot/EFI/opensuse:
boot.csv  grubenv      installed_by_sdbootutil  shim.efi
grub.efi  grubx64.efi  MokManager.efi

/mnt/boot/loader:
entries  loader.conf  random-seed

/mnt/boot/loader/entries:

/mnt/boot/opensuse-tumbleweed:
6.18.5-1-default  6.19.2-1-default  7.0.7-1-default  7.1.3-1-default
6.18.6-1-default  7.0.12-1-default  7.1.2-1-default

/mnt/boot/opensuse-tumbleweed/6.18.5-1-default:

/mnt/boot/opensuse-tumbleweed/6.18.6-1-default:

/mnt/boot/opensuse-tumbleweed/6.19.2-1-default:

/mnt/boot/opensuse-tumbleweed/7.0.12-1-default:

/mnt/boot/opensuse-tumbleweed/7.0.7-1-default:

/mnt/boot/opensuse-tumbleweed/7.1.2-1-default:

/mnt/boot/opensuse-tumbleweed/7.1.3-1-default:

/mnt/boot/proc:

/mnt/boot/run:

/mnt/boot/sys:

/mnt/boot/System Volume Information:
linux@localhost:~>

nrickert · July 19, 2026, 3:14pm

That’s too small.

I’m using 500M, but I get warnings that it is running low on space.

Can you give us the output from:

efibootmgr -v

(you can run that command as root on the live tumbleweed rescue cd).

norrin · July 19, 2026, 3:18pm

I know i have to increase it, but before i do that i have to do a backup of my opensuse tw…

linux@localhost:~> sudo efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0002,0000,0003
Boot0000* opensuse-secureboot	HD(1,GPT,83cbdae3-6771-4694-8f43-b2abcaf24850,0x800,0x32000)/File(\EFI\opensuse\shim.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 e3 da cb 83 71 67 94 46 8f 43 b2 ab ca f2 48 50 02 02 / 04 04 32 00 5c 00 45 00 46 00 49 00 5c 00 6f 00 70 00 65 00 6e 00 73 00 75 00 73 00 65 00 5c 00 73 00 68 00 69 00 6d 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0002* Windows Boot Manager	HD(1,GPT,83cbdae3-6771-4694-8f43-b2abcaf24850,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000007050100000010000000040000007fff0400
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 e3 da cb 83 71 67 94 46 8f 43 b2 ab ca f2 48 50 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 07 05 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0003  UEFI: USB Hard Drive, Partition 2	PciRoot(0x0)/Pci(0x8,0x3)/Pci(0x0,0x0)/USB(1,0)/HD(2,GPT,36323032-3630-4330-b032-303831333533,0x18fed4,0xa000)0000424f
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 03 08 / 01 01 06 00 00 00 / 03 05 06 00 01 00 / 04 01 2a 00 02 00 00 00 d4 fe 18 00 00 00 00 00 00 a0 00 00 00 00 00 00 32 30 32 36 30 36 30 43 b0 32 30 38 31 33 35 33 02 02 / 7f ff 04 00
    data: 00 00 42 4f
linux@localhost:~>

malcolmlewis · July 19, 2026, 3:20pm

If your not using MS and it’s deleted, then can delete all that information and NVRAM entries. Also you have switched to systemd-boot, not grub2-efi… And set the default to boot order for “0000” to be first…

You can fix the situation with https://news.opensuse.org/2026/07/07/xbootldr/

Edit: Clarification;

/mnt/boot/EFI/opensuse:
==> installed_by_sdbootutil  <==

norrin · July 19, 2026, 3:39pm

Hmmm,
there is a lot to learn for me.

a) MS is completely deleted and . So what exactly can i delete in /boot/efi?

b) I am pretty sure that my system used grub. There is still the grub-menu coming ()version 2.14).
I guess i did some “sdbootutil install” while chroot - suggested by the AI.

c) Where do you mean i have to “set the default to boot order for “0000” to be first…”?

d) Where should i go now? Repair the grub or migrate to systemd-boot (with the xbootldr)?

Thanks for your support. Human support feels so much better than AI…

malcolmlewis · July 19, 2026, 3:54pm

@norrin Based on your output;

cd /mnt/boot/EFI
pwd
<check your in /mnt/boot/EFI>
ls
rm -rf Microsoft

Remove NVRAM MS boot entry;

efibootmgr -b 2 -B 2

It should show Boot0000* opensuse-secureboot as first in BootOrder output and no “Windows Boot Manager” entry.

Fixing things up… well I would suggest staying with systemd-boot, but I’m not a boot loader expert, so there are openSUSE SDB’s or perhaps @nrickert can offer advice about switching back…

gogalthorp · July 19, 2026, 6:25pm

Just removing a OS does not magically update the BIOS boot entries they must be removed manually as per malcolmlewis’s post

norrin · July 19, 2026, 8:17pm

It did not really disturb me.
Grub only showed the openSUSE and the UEFI-entry, so i had no idea that there is something i have to clean up.

It is kind of funny, because i also decided against dualboot because of possible bootloader problems and now here i am…

Sure I will clean the MS-stuff butunfortunately this will not solve my problem of not being able to boot openSUSE tw.

Don’t know what do do now…

malcolmlewis · July 19, 2026, 8:24pm

@norrin So what does the boot entry say after selecting openSUSE, as in which kernel does it say it’s loading?

malcolmlewis · July 19, 2026, 10:02pm

@norrin Here is a hint, but from the chroot environment you likely need to run update-bootloader --show to see what loader is in use…

https://forums.opensuse.org/t/grub2-reinstallation-from-rescue-system/165648/2

norrin · July 20, 2026, 9:38am

update-bootloader --show
grub2-bls

So this question seems to be solved.