https://bugzilla.novell.com/show_bug.cgi?id=814824 https://bugzilla.novell.com/show_bug.cgi?id=814824#c0 Summary: kernel update -> mkinitrd -> grub2-efi-install -> efibootmgr deletes boot entry, leaves system unbootable Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: ailin.nemui@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 I installed new kernels from Kernel:stable, of course I must be prepared for such hick-ups. In a range of 3.8.2, 3.8.4 and 3.8.6, Starting from kernel 3.8.4, the efibootmgr fails to create the linux boot menu entry, which in effect leaves the computer in a state that cannot boot. When a new kernel is installed, the initrds are generated, and also the boot manager config is updated, which also reinstalls grub2. This is an issue I think, because it is not necessary to reinstall grub2, which would have avoided the critical broken system. If grub2 needs to be reinstalled then at least the call to efibootmgr could be skipped, then it would not delete the existing entry and fail to re-add a new entry. One issue here is with efibootmgr, where there is no error reporting. I only found out what's going on with "strace" and notice the ENOSPC error message in the efibootmgr run. This seems to be an issue with Linux kernel, because now efibootmgr cannot write to efivars, only delete from it. I wonder if it might be related to the Samsung UEFI breakage hot fix? I think one approach would be to make sure we can write to efivars *first* before deleting and rewriting the bootmanager entry. Reproducible: Always Steps to Reproduce: 1. boot with 3.8.4 or newer kernel 2. install kernel update or anything else that will (indirectly) trigger efibootmgr run 3. be unable to boot into your system next time because bootmgr entry got deleted Actual Results: broken system that cannot boot, not obvious to fix Expected Results: kernel update shouldn't break grub install or uefi bootmanager I use lenovo thinkpad T430s to test it. Here are the relevant bugs from other distros I could find: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=922275 https://bugzilla.redhat.com/show_bug.cgi?id=947142 Ubuntu https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1167567 Thanks! -- 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.