[Bug 1174788] New: Recent update broke booting
http://bugzilla.opensuse.org/show_bug.cgi?id=1174788 Bug ID: 1174788 Summary: Recent update broke booting Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs@suse.de Reporter: pointedstick@zoho.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 840272 --> http://bugzilla.opensuse.org/attachment.cgi?id=840272&action=edit Scary error screen I saw After yesterday's Tumbleweed update, my laptop was rendered unbootable. It displayed a scary Windows-style blue error screen saying that the system was broken. There is no Windows partition on this machine, so it must be some kind of backup EFI error screen or something. I was able to boot into the EFI shell of a recovery USB flash disk I had lying around and then boot into my openSUSE TW OS by doing the following in the EFI shell fs0: cd EFI cd opensuse grubX64.efi And then I saw the normal openSUSE kernel chooser boot manager and was able to boot normally. So this bootloader works just fine. However for some reason this bootloader is no longer automatically used anymore after the update. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174788 http://bugzilla.opensuse.org/show_bug.cgi?id=1174788#c1 --- Comment #1 from Nathaniel Graham <pointedstick@zoho.com> --- Created attachment 840273 --> http://bugzilla.opensuse.org/attachment.cgi?id=840273&action=edit What I did to boot it manually -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174788 http://bugzilla.opensuse.org/show_bug.cgi?id=1174788#c2 --- Comment #2 from Nathaniel Graham <pointedstick@zoho.com> --- Created attachment 840274 --> http://bugzilla.opensuse.org/attachment.cgi?id=840274&action=edit `efibootmgr` output (annotated for clarity) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174788 http://bugzilla.opensuse.org/show_bug.cgi?id=1174788#c3 Ahmad Samir <a.samirh78@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.samirh78@gmail.com --- Comment #3 from Ahmad Samir <a.samirh78@gmail.com> --- It might be that something removed the opensuse boot entry. To add it back (from the recovery usb or from a booted TW): efibootmgr --create --disk /dev/sda --label opensuse --part 1 --loader '\EFI\opensuse\grubx64.efi' --disk /dev/sda replace /dev/sda with the actual device node (probably nvme0 or something like that). --part 1 the EFI partition, usually the first partition on the disk (in my case /dev/sda1), this is the partition containing the loader (grubx64.efi) --loader '\EFI\opensuse\grubx64.efi' must be like that, with the backslashes and the single quotes (I can't remember if double quotes work or not, so). See efibootmgr --help for more details.
From the screenshot I noticed that the fw dir has been modified recently, it could well be that a firmware updated caused the opensuse entry to get removed (I've had that happen before; also sometimes when I reset the firmware to defaults using the button/jumper on my PC motherboard).
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174788 http://bugzilla.opensuse.org/show_bug.cgi?id=1174788#c4 --- Comment #4 from Ahmad Samir <a.samirh78@gmail.com> --- Or after you boot your TW installation, you could try running (IIRC that worked too, but since I can't find any documentation for this command, the use AT YOUR OWN RISK disclaimer is in effect here :)): /sbin/update-bootloader --reinit FWIW, this command is use in the post install rpm scriptlets for the grub2-x86_64-efi package; `rpm -q --scripts grub2-x86_64-efi` to see the whole storyboard. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174788 http://bugzilla.opensuse.org/show_bug.cgi?id=1174788#c5 --- Comment #5 from Nathaniel Graham <pointedstick@zoho.com> --- Many thanks, visiting the YaST bootloader page and closing it again re-added the correct EFI entry. There was indeed a firmware upgrade recently, so maybe that caused it? In which case, whose fault would that be? The firmware vendor? fwupd itself? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174788 http://bugzilla.opensuse.org/show_bug.cgi?id=1174788#c6 --- Comment #6 from Ahmad Samir <a.samirh78@gmail.com> --- My "guess" would be the firmware vendor; but I am not an expert on laptop firmware updates or fwupd. :) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174788 http://bugzilla.opensuse.org/show_bug.cgi?id=1174788#c7 --- Comment #7 from Nathaniel Graham <pointedstick@zoho.com> --- This just happened again after another system update, but there was no firmware update involved. So I think we can rule that out. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1174788 Alex Debus <postix@posteo.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |postix@posteo.eu -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com