Booting fails after update restart. What to do next?

[Budgie2]

@arvidjaar

So it boots in EFI mode. What is output of “efibootmgr -v” when booting live? Also “ls -lR” from ESP would be certainly interesting.

Hi arvidjaar,
Sorry for the delay but this system takes more than 10 minutes to boot into rescue system.
Running the commands are OK but is there any way I can get them to you from the rescue system, otherwise the best way would be for me to take a picture!
The output of the first command above gives me the Boot order and list of the boot items. Will just swap to another computer and try and type in the last line.

Boot000E= grub-secureboot HD(1,GPT,5a62adf2-d3b4-45d5-abaa-1982f4195eaa,0x800,0x4e000)/File(\EFI\grub\shim.efi)

and ls -lR /dev/sda1 gives
brw-rw---- 1 root disk 8 1 Feb 20 15:59 /dev/sda1

[nrickert]

@Budgie2

Boot000E= grub-secureboot HD(1,GPT,5a62adf2-d3b4-45d5-abaa-1982f4195eaa,0x800,0x4e000)/File(\EFI\grub\shim.efi)

Interesting.

I seem to remember that there was a bug, several years ago, where it installed booting as “grub-secureboot” instead of “opensuse-secureboot”. Perhaps you have been booting that way for a long time, and it no longer works. That might also explain the “GNU GRUB version 2.02~beta2” which is a way out of date version.

Can you boot from rescue media. Then mount “/dev/sda1”

mount /dev/sda1 /mnt

and then:

cd /mnt/EFI
ls -l grub
ls -l opensuse

Based on what you have been describing, I expect the files in “grub” (the first of those “ls” commands) to be several years old. And I expect the files in “opensuse” (the second of those “ls” commands) to be recent (a few days old).

If that turns out to be correct, then run the following commands:

cd /mnt/EFI
mkdir oldgrub
cp -p grub/*.* oldgrub/.
cp -p opensuse/*.*  grub/.

and then try rebooting and see if you can get into your system.

[Budgie2]

@nrickert

Interesting.

I seem to remember that there was a bug, several years ago, where it installed booting as “grub-secureboot” instead of “opensuse-secureboot”. Perhaps you have been booting that way for a long time, and it no longer works. That might also explain the “GNU GRUB version 2.02~beta2” which is a way out of date version.

Can you boot from rescue media. Then mount “/dev/sda1”

mount /dev/sda1 /mnt

and then:

cd /mnt/EFI
ls -l grub
ls -l opensuse

OK I have all the grub entries at 2016
Of the opensuse entries one is fw at 2016
MokManager.efi
boot.csv
fwupdx64.efi
grub.cfg
grub.efi
shim.efi
are all dated 2017,
only grubx64.efi is Feb 20
Based on what you have been describing, I expect the files in “grub” (the first of those “ls” commands) to be several years old. And I expect the files in “opensuse” (the second of those “ls” commands) to be recent (a few days old).

If that turns out to be correct, then run the following commands:

cd /mnt/EFI
mkdir oldgrub
cp -p grub/*.* oldgrub/.
cp -p opensuse/*.*  grub/.

and then try rebooting and see if you can get into your system.

Seems plausible so I have done as you suggest and lo and behold my system is up and running again. A thousand thanks for find this and sorting it out. Will let it do the updates that are outstanding now and close thread tomorrow.

[nrickert]

@Budgie2

Will let it do the updates that are outstanding now and close thread tomorrow.

No, let’s not close this. Do your updates. But then let’s come back to this problem and try to get it straightened out, so that this does not happen again.

When you next post in this thread, please provide the output from:

efibootmgr -v

and use CODE tags for that output.