No boot after Leap distribution upgrade to 15.6

[drawson1]

I have a desktop system which was running 15.5 with all updates. I did a “zypper dup” following the instructions in the wiki, and the system will now NOT boot from the grub menu. Any selection from the grub menu results in an instant black screen and no other activity (and the disk light never comes on).

I did compare the generated grub.cfg with the backup copy from 15.5, and (except for the kernel version strings) it is identical

If I boot from a Live USB (15.5), then select More → Boot Linux, the Live USB finds the 15.6 install, finds the 6.4.0 kernel and boots (apparently correctly

Any suggestions? What additional information would be useful to debug this?

Thanks!

Dan

[drawson1]

One error - I was booting from the 15.5 install image on a flash drive, not from a LIVE image.

[arvidjaar]

@drawson1

Any suggestions?

The usual first step - boot with plymouth.enable=0 and without quiet on kernel command line. It may output some more information.

[heitormoreira]

Well, an easy way to try to solve that could be downloading the ISO of Leap 15.6, booting from it and trying to upgrade from there.

[drawson1]

No luck with either of these techniques - changing the kernel command-line didn’t provide any data (still a black screen after hitting return) and doing a new “Update” install from the offline install image had the same problem.

However …

In the course of testing all the possibilities … Normally when I boot, the grub menu comes up in text mode. If I hit “c” to go to the grub command line, and then exit grub, the grub menu comes up in GUI mode!. If I hit “Return” on ANY of the available options in GUI mode, the computer starts correctly!!! A short examination shows that the command lines available are IDENTICAL from either the text-mode grub screen or the GUI-mode screen.

Now I’m even more puzzled … but I do have a way to boot the computer reliably

[heitormoreira]

Please, show the output of these three commands:

lsblk -f -o +partuuid
efibootmgr -v
cat /boot/grub2/grub.cfg

[hui]

When the computer starts correctly after your small procedure, enter YaST bootloader and make sure that the graphic grub mode is selected.

[nrickert]

@drawson1

Now I’m even more puzzled …

I’ll make a guess.

You are booting with UEFI, and the boot order selects something other than openSUSE to boot. When you exit grub, it tries the next in boot order which does happen to be openSUSE.

What’s the output from:

efibootmgr -v

[drawson1]

Ahhh … and there’s a new EFI file from my install date/time …

> sudo efibootmgr -v
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0005,0000,0002,0001
Boot0000* opensuse      HD(10,GPT,82987915-0302-450d-a03e-2cc825aaef09,0x1e20800,0x64000)/File(\EFI\OPENSUSE\GRUBX64.EFI)
Boot0001  Hard Drive    BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)..GO..NO..........W.D.C. .W.D.4.0.0.3.F.F.B.X.-.6.8.M.U.3.N.0...................\.,.@.r.d.=.X..........A...........................>..Gd-.;.A..MQ..L.3.V.L.G.8.4.F.9. . . . . . . . . . . . ........BO..NO..........W.D.C. .W.D.8.0.E.F.Z.Z.-.6.8.B.T.X.N.0...................\.,.@.r.d.=.X..........A...........................>..Gd-.;.A..MQ..L. . . . . . . . .W. .-.D.A.C.0.2.K.5.K.N........BO
Boot0002  CD/DVD Drive  BBS(CDROM,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0300)..GO..NO..........D.R.W.-.2.4.F.1.S.T. . . .d...................\.,.@.r.d.=.X..........A...........................>..Gd-.;.A..MQ..L.1.K.I.O.C.4.2.F.2.1. .6. . . . . . . . ........BO
Boot0005* UEFI OS       HD(10,GPT,82987915-0302-450d-a03e-2cc825aaef09,0x1e20800,0x64000)/File(\EFI\BOOT\BOOTX64.EFI)..BO

And:

( /boot/efi/EFI )
20-Aug-24 16:31 > find .
.
./BOOT
./BOOT/BOOTX64.EFI
./opensuse
./opensuse/grubx64.efi

The BOOTX64.EFI file dates from my Leap 15.5 install last year, and the grubx64.efi file is from a couple of days ago.

lsblk:

NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS PARTUUID
sda                                                                                     
├─sda1
│                                                                                       33290c91-0d93-4b13-9f01-5b9970e528ea
├─sda2
│    swap   1           9dbf8ae8-1b1d-4591-b49e-15edd1f5fc01                [SWAP]      e774717f-95ba-41af-9999-c63213bc1b98
├─sda3
│    ext4   1.0         e45d8ca7-cee9-44e5-9a02-3e05938bed12      1G    11% /boot       9582448d-ca99-4924-8418-43bead1fdc1d
├─sda4
│    crypto 1           460d5fe8-4f18-4df3-8766-9447f2898e98                            412e554a-4cae-4833-9ce6-c24bcd88145f
├─sda5
│    ext4   1.0         f113f887-4b97-41f4-b3d9-9487f21681ae  158.8G    13% /           5cd384ef-3632-4ca4-9f0e-c93c12f71fbe
├─sda6
│    ext4   1.0         a0778a59-595b-435e-9969-49c8f71d51b0  332.7G    52% /opt        0067d356-b293-4dda-8d96-0c473089909f
├─sda7
│    ext4   1.0         74786897-c65c-4d43-9375-6206015b5467   65.8G    73% /usr/local  e02a937c-c621-4b56-9212-8567bb1a620c
├─sda8
│    ext4   1.0         604533f6-d4cc-4e77-8279-ca362b24cb0a  444.3G    51% /usr/local/media
│                                                                                       9936d944-ef54-49c9-9755-6660d2ce3364
├─sda9
│    ext4   1.0         353fa2c1-1d43-4144-9add-5e6cd35e555f  927.8G    27% /home       2b1d38e7-7088-48d8-aaf0-af69cfb04ce2
└─sda10
     vfat   FAT16       2BCE-00C5                             199.5M     0% /boot/efi   82987915-0302-450d-a03e-2cc825aaef09
sdb                                                                                     
└─sdb1
     ext4   1.0         8823fad8-f417-4f78-ae29-aef27ca9840b    1.9T    68% /backup     3d87f2d1-9459-4100-a006-4fe5b29d9fbe

I’ve done some reading on-line, but if there’s a good reference somewhere for how the UEFI boot sequence works, I’d appreciate a pointer to that info - thanks.

Dan

[drawson1]

It is set to use the “Graphical console”

[heitormoreira]

If you have only Leap installed in this system, removing the Boot0005* UEFI OS entry might solve the problem. You can do it with: sudo efibootmgr -b 0005 -B
Before anything else, make sure you have a backup and have a bootable Leap flash drive, just in case.

[nrickert]

Normally, when you install opensuse that will be set first in boot order. But you have entry 0005 as first in boot order.

Check your BIOS. With some systems, the BIOS has its own preferred boot order and you have to set the boot order there.

[drawson1]

That turns out to be EXACTLY the issue … “efibootmgr -o …” did nothing;
once I re-set the order in the bios it worked as expected. It’s a 6-year-old
Shuttle motherboard, so I should just be glad it keeps working :-))

Thanks to everyone for the help/suggestions - this is SOLVED

Dan