[Bug 1200717] New: Recent updates (grub2, kernel) created invalid grub configuration
http://bugzilla.opensuse.org/show_bug.cgi?id=1200717 Bug ID: 1200717 Summary: Recent updates (grub2, kernel) created invalid grub configuration Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs@suse.de Reporter: Ulrich.Windl@rz.uni-regensburg.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 859705 --> http://bugzilla.opensuse.org/attachment.cgi?id=859705&action=edit Recent lines from /var/log/pbl.log After updating the system, the next boot failed. I had to use the rescue system and chroot method to run 'grub2-mkconfig -o /boot/grub2/grub.cfg'. Then the next boot worked again. Recent updates were: openSUSE-signkey-cert-20220613-lp153.2.3.1.x86_64 Mon 20 Jun 2022 10:59:13 AM CEST typelib-1_0-WebKit2-4_0-2.36.3-150200.35.1.x86_64 Mon 20 Jun 2022 10:59:12 AM CEST libwebkit2gtk3-lang-2.36.3-150200.35.1.noarch Mon 20 Jun 2022 10:59:12 AM CEST gimp-lang-2.10.12-150300.9.3.1.noarch Mon 20 Jun 2022 10:59:12 AM CEST gimp-2.10.12-150300.9.3.1.x86_64 Mon 20 Jun 2022 10:59:11 AM CEST binutils-devel-2.37-150100.7.34.1.x86_64 Mon 20 Jun 2022 10:59:09 AM CEST kernel-default-devel-5.3.18-150300.59.71.2.x86_64 Mon 20 Jun 2022 10:59:08 AM CEST kernel-default-optional-5.3.18-150300.59.71.2.x86_64 Mon 20 Jun 2022 10:59:02 AM CEST webkit2gtk-4_0-injected-bundles-2.36.3-150200.35.1.x86_64 Mon 20 Jun 2022 10:59:01 AM CEST libwebkit2gtk-4_0-37-2.36.3-150200.35.1.x86_64 Mon 20 Jun 2022 10:59:01 AM CEST typelib-1_0-JavaScriptCore-4_0-2.36.3-150200.35.1.x86_64 Mon 20 Jun 2022 10:59:00 AM CEST libgimpui-2_0-0-2.10.12-150300.9.3.1.x86_64 Mon 20 Jun 2022 10:59:00 AM CEST binutils-2.37-150100.7.34.1.x86_64 Mon 20 Jun 2022 10:58:59 AM CEST libctf0-2.37-150100.7.34.1.x86_64 Mon 20 Jun 2022 10:58:58 AM CEST kernel-devel-5.3.18-150300.59.71.2.noarch Mon 20 Jun 2022 10:58:58 AM CEST kernel-default-extra-5.3.18-150300.59.71.2.x86_64 Mon 20 Jun 2022 10:58:49 AM CEST yast2-network-4.3.82-150300.3.28.1.noarch Mon 20 Jun 2022 10:58:48 AM CEST grub2-x86_64-efi-2.04-150300.22.20.2.noarch Mon 20 Jun 2022 10:58:48 AM CEST grub2-systemd-sleep-plugin-2.04-150300.22.20.2.noarch Mon 20 Jun 2022 10:58:48 AM CEST grub2-snapper-plugin-2.04-150300.22.20.2.noarch Mon 20 Jun 2022 10:58:48 AM CEST xen-libs-4.14.5_02-150300.3.29.1.x86_64 Mon 20 Jun 2022 10:58:47 AM CEST vim-data-8.2.5038-150000.5.21.1.noarch Mon 20 Jun 2022 10:58:47 AM CEST vim-8.2.5038-150000.5.21.1.x86_64 Mon 20 Jun 2022 10:58:47 AM CEST vim-data-common-8.2.5038-150000.5.21.1.noarch Mon 20 Jun 2022 10:58:46 AM CEST libjavascriptcoregtk-4_0-18-2.36.3-150200.35.1.x86_64 Mon 20 Jun 2022 10:58:46 AM CEST libgimp-2_0-0-2.10.12-150300.9.3.1.x86_64 Mon 20 Jun 2022 10:58:45 AM CEST libctf-nobfd0-2.37-150100.7.34.1.x86_64 Mon 20 Jun 2022 10:58:44 AM CEST kernel-macros-5.3.18-150300.59.71.2.noarch Mon 20 Jun 2022 10:58:44 AM CEST kernel-docs-5.3.18-150300.59.71.2.noarch Mon 20 Jun 2022 10:58:44 AM CEST kernel-default-5.3.18-150300.59.71.2.x86_64 Mon 20 Jun 2022 10:58:14 AM CEST grub2-i386-pc-2.04-150300.22.20.2.noarch Mon 20 Jun 2022 10:58:11 AM CEST grub2-2.04-150300.22.20.2.x86_64 Mon 20 Jun 2022 10:58:10 AM CEST geronimo-stax-1_0-api-1.2-150200.15.2.1.noarch Mon 20 Jun 2022 10:58:10 AM CEST Last reboot was beginning of the month. I could not find an obvious error in pbl.log, however -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200717 http://bugzilla.opensuse.org/show_bug.cgi?id=1200717#c1 --- Comment #1 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Created attachment 859707 --> http://bugzilla.opensuse.org/attachment.cgi?id=859707&action=edit Screen message when boot had failed -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200717 http://bugzilla.opensuse.org/show_bug.cgi?id=1200717#c3 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) | --- Comment #3 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (In reply to Michael Chang from comment #2)
Is it possible for you to try again
update-bootloader --reinit
Reboot to see if the problem reproducible ? Would it be possible to attach the grub.cfg when you see the problem ? Thanks.
I kind of simplified the procedure: 1) Save the current grub.cfg under a different name 2) run "update-bootloader --reinit" 3) diff old and new files As there were no differences, I guess booting will succeed, unless there are some other effects. So I skipped trying boot. The only thing that is special in my configuration is that the disk is encrypted and rootfs is on LV, thus: ryptomount -u ebdc168af0f1481bb6a54c5cdbafed95 set root='lvmid/W0LKbn-AyLt-ErrA-sH5I-AEX3-Vhl4-qf2oMD/OcYEfE-eE8f-nmcq-Ivvp-KMa2-DvVM-G3Mi5U' -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200717 http://bugzilla.opensuse.org/show_bug.cgi?id=1200717#c4 --- Comment #4 from Michael Chang <mchang@suse.com> --- If (In reply to Ulrich Windl from comment #3)
(In reply to Michael Chang from comment #2)
Is it possible for you to try again
update-bootloader --reinit
Reboot to see if the problem reproducible ? Would it be possible to attach the grub.cfg when you see the problem ? Thanks.
I kind of simplified the procedure: 1) Save the current grub.cfg under a different name 2) run "update-bootloader --reinit" 3) diff old and new files
As there were no differences, I guess booting will succeed, unless there are some other effects. So I skipped trying boot.
The same update-bootloader call is used in rpm's %posttrans to update grub2. If it cannot be reproduced again from console, then something fishy is in the update environment to break the grub.cfg. I also have setup 15.3 for test but couldn't reproduce as well.
The only thing that is special in my configuration is that the disk is encrypted and rootfs is on LV, thus: ryptomount -u ebdc168af0f1481bb6a54c5cdbafed95 set root='lvmid/W0LKbn-AyLt-ErrA-sH5I-AEX3-Vhl4-qf2oMD/OcYEfE-eE8f-nmcq-Ivvp- KMa2-DvVM-G3Mi5U'
This is supported and should work. I'd suggest to test a few more updates and come back with the broken grub.cfg attached if that happens again. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com