On Fri, Mar 30, 2018 at 2:58 PM, Peter Suetterlin <pit@astro.su.se> wrote:
Andrei Borzenkov wrote:
On Fri, Mar 30, 2018 at 2:24 PM, Peter Suetterlin <pit@astro.su.se> wrote:
Hi list,
I have a computer that I upgraded 42.2->42.3 a month ago (without issues). It was powered off since then. Today I rebooted it (again, without issues).
I ran a 'zypper up', and rebooted - and now it throws me at grub-rescue with the mentioned error symbol "grub_tmp_measure" not found. grub has been updated during this run.
This means grub2 core.img (the binary loaded by firmware) was not updated during install and does not match content of /boot/grub2. Usual cause us mismatch between bootloader location configured in openSUSE and BIOS boot device.
Hmm, not sure if it is using UEFI/secureboot. It's the only option.
Not sure I understand this sentence. Are you using EFI? In this case show output of "efibootmgr -v".
Should that missmatch have produced an error during update?
No. Update simply installs bootloader where configuration tells it; it has no way to know what BIOS actually tries to load. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org