[Bug 887066] New: UEFI Boot Entry Disappeared After Updates
https://bugzilla.novell.com/show_bug.cgi?id=887066 https://bugzilla.novell.com/show_bug.cgi?id=887066#c0 Summary: UEFI Boot Entry Disappeared After Updates Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: Espionage724@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Relevant thread: https://forums.opensuse.org/showthread.php/494374-UEFI-Boot-Entry-Disappeare... With a fresh instal of openSUSE 13.1 in UEFI, the boot entry for opensuse exists, and all is well. After doing updates (not sure which one in particular is responsible), the UEFI boot entry is removed, and thus, leaves you unable to reboot the system. This has happened as early as January that I've seen, and was reproducible on 3 different computers (two being desktops, one having an ASRock 970 Extreme3 motherboard, one having an ASRock Fatal1ty H97 Killer motherboard, one being an Acer Aspire V3-551G-X419 laptop). Running "update-bootloader --reinit" before rebooting puts the opensuse boot entry back, and rebooting is fine afterward. "efibootmgr -c -d /dev/sda -p 1 -L opensuse-secure -l '\EFI\opensuse\grubx64.efi.efi'" (not 100% sure on the exact command) seems to also re-add the boot entry and allow for successful reboots. Reproducible: Always Steps to Reproduce: 1. Install openSUSE 13.1 in UEFI-mode with SecureBoot disabled 2. Check "efibootmgr -v" and see the opensuse entry 3. Install all available updates from default repositories (about 600MB+ worth of them at the time of writing) without rebooting Actual Results: "efibootmgr -v" right after installing the updates should show no opensuse entry anymore, and rebooting should result in being unable to boot into openSUSE due to the lack-of a boot entry. Expected Results: "efibootmgr -v" should show the opensuse boot entry, and rebooting after updates should boot back into openSUSE without problem due to the existence of the opensuse boot entry. This has happened since January 2014 from what I noted, and still occurs as of July. SecureBoot was disabled throughout the entire process. Unsure if this is reproducible with SecureBoot being enabled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887066 https://bugzilla.novell.com/show_bug.cgi?id=887066#c1 --- Comment #1 from Sean Rhone <Espionage724@gmail.com> 2014-07-14 06:01:35 UTC --- Created an attachment (id=598402) --> (http://bugzilla.novell.com/attachment.cgi?id=598402) log I was told to upload, might be of use Was told to upload the log on the relevant thread: https://forums.opensuse.org/showthread.php/494374-UEFI-Boot-Entry-Disappeare... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887066 https://bugzilla.novell.com/show_bug.cgi?id=887066#c2 Andrey Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #2 from Andrey Borzenkov <arvidjaar@gmail.com> 2014-07-14 18:39:20 UTC --- (In reply to comment #1)
Was told to upload the log
You need to upload result of save_y2logs execution, not script itself. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887066 https://bugzilla.novell.com/show_bug.cgi?id=887066#c3 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |Espionage724@gmail.com --- Comment #3 from Jiri Srain <jsrain@suse.com> 2014-07-15 12:57:03 UTC --- Re-setting NEEDINFO, the logs are needed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887066 https://bugzilla.novell.com/show_bug.cgi?id=887066#c4 Sean Rhone <Espionage724@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #598402|0 |1 is obsolete| | --- Comment #4 from Sean Rhone <Espionage724@gmail.com> 2014-07-24 03:50:02 UTC --- (From update of attachment 598402) Wrong thing -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887066 https://bugzilla.novell.com/show_bug.cgi?id=887066#c5 Sean Rhone <Espionage724@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|Espionage724@gmail.com | --- Comment #5 from Sean Rhone <Espionage724@gmail.com> 2014-07-24 03:56:12 UTC --- Created an attachment (id=599687) --> (http://bugzilla.novell.com/attachment.cgi?id=599687) y2logs after updates y2logs outputted by running save_y2logs after running zypper up on fresh 13.1 install. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887066 https://bugzilla.novell.com/show_bug.cgi?id=887066#c6 Jiri Srain <jsrain@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mchang@suse.com --- Comment #6 from Jiri Srain <jsrain@suse.com> 2014-07-24 12:21:44 UTC --- I could not find anything suspicious in the logs; Michael, do you have any idea who and why fiddles with the EFI menu during package update? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=887066 https://bugzilla.novell.com/show_bug.cgi?id=887066#c7 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang@suse.com InfoProvider|mchang@suse.com |Espionage724@gmail.com --- Comment #7 from Michael Chang <mchang@suse.com> 2014-07-25 04:47:31 UTC --- Hi Sean, I did not find too much clue for the log. Probably during update some utility which would manipulate the efi boot entries got called and delete boot entry accidentally. These commands could happen in package update and would you please to check by running them. efibootmgr -v update-bootloader --refresh efibootmgr -v efibootmgr -v test -x /usr/sbin/shim-install && /usr/sbin/shim-install --clean efibootmgr -v -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com