[Bug 1042131] New: bootloader grub2-efi not useable after upgarde from 13.2 -> 42.2
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131 Bug ID: 1042131 Summary: bootloader grub2-efi not useable after upgarde from 13.2 -> 42.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: wharms@bfs.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- The system (HP Compaq 6200 Pro MT PC) was running with OS 13.2 and a working grub bootloader. I did an upgrade to 42.2 via DVD. The upgrade failed when installing the bootloader with an shim error ("EFI Partition not found" ? - not sure). I was able too boot the system via DVD and did an update to the latest versions. This did not fix the problem neither changing the bootloader to non-efi grub. After various attempts i realized that there was no /boot/efi/... what so ever. Coping that from DVD made the system bootable again. A good indicator was that grub2-mkconfig showed an error (missing /boot/efi/..) in the XEN part. I ignored that in the beginning as i do not use XEN. Suggestion: * a more descriptive error for shim ("Partition" let me search with fdisk) * double check that /boot/efi/.. and friends really, really exists * Give clueless user a hint what to do when yast fails to install a bootloader (like "use DVD to recover" ... ) * on error: offer to remove all traces from efi (like the opensuse entry) in the vain hope that an other bootloader may be more successful when not confused with leftovers -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131#c1
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131#c2
a b
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131#c3
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131#c4
--- Comment #4 from Josef Reidinger
Given the error messages speak about uEFI, I would guess that uEFI was the boot method chosen.
Josef, do we have any handling of this inconsistency - original system installed with different boot architecture than the one enforced by update?
no, we do not have it. We simply propose it from scratch when unsupported bootloade found. No mapping of old one to new ones is not done. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131#c5
--- Comment #5 from a b
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131
http://bugzilla.opensuse.org/show_bug.cgi?id=1042131#c6
--- Comment #6 from Jiri Srain
IMHO is it important to understand how could it happen that the directory /boot/efi/ was totaly missing ?
It is very easy: The system was initially installed with legacy bootloader, therefore it was not needed at all. (In reply to Josef Reidinger from comment #4)
(In reply to Jiri Srain from comment #3)
Given the error messages speak about uEFI, I would guess that uEFI was the boot method chosen.
Josef, do we have any handling of this inconsistency - original system installed with different boot architecture than the one enforced by update?
no, we do not have it. We simply propose it from scratch when unsupported bootloade found. No mapping of old one to new ones is not done.
Well, but then we try proposing bootloader configuration, which is not possible given the disk partitioning. a b: IMO you need to stick to a single boot architecture (in this case legacy) when upgrading your system, as different boot architectures may require different partitions. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com