[Bug 939453] New: Installation sets legacy_boot flag on 2 partitions - system cannot boot
http://bugzilla.opensuse.org/show_bug.cgi?id=939453 Bug ID: 939453 Summary: Installation sets legacy_boot flag on 2 partitions - system cannot boot Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: Larry.Finger@lwfinger.net QA Contact: jsrain@suse.com Found By: --- Blocker: --- After installation of openSUSE 42.1-RC1 to a second partition on my system with the legacy BIOS bootable option set, I ended up with two partitions having the "boot" and "boot_legacy" flags set. Of course, the BIOS refused to boot. To work around this situation, I needed to boot a rescue system and use parted to toggle the legacy_boot flag off for one of the two partitions. This bug is identical to that of Bug 848609, which was "fixed" in 13.1. Obviously, it has crept back in with the SLE code. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939453
http://bugzilla.opensuse.org/show_bug.cgi?id=939453#c1
Chris Murphy
http://bugzilla.opensuse.org/show_bug.cgi?id=939453
http://bugzilla.opensuse.org/show_bug.cgi?id=939453#c2
Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=939453
http://bugzilla.opensuse.org/show_bug.cgi?id=939453#c9
--- Comment #9 from Chris Murphy
The problem is that not all users like the idea to write grub/grub2 to LBA0.
Then they should opt out and use extlinux instead of GRUB 2. The current openSUSE behavior and recommendation is incongruent with GRUB upstream. http://lists.gnu.org/archive/html/grub-devel/2015-08/msg00093.html Basically what you have in openSUSE now is something that's a.) inconsistent with GRUB upstream b.) inconsistent with all other distros c.) not documented anywhere a user could find it d.) not a self-describing or easily followed boot process, e.) installing GRUB core.img into the Btrfs 64KiB bootloader pad while supported is considered suboptimal by GRUB upstream they prefer it going either in the MBR gap or BIOS Boot where there's more room for a larger core.img. This makes it difficult to troubleshoot, the user has to get this esoteric information from not just the openSUSE community since no one else does it this way, but a narrow slice within the openSUSE community because it's such esoteric (and unexpected) behavior. If GRUB by default, then only support their recommended methods. Optionally provide UI for the user to opt out of overwriting LBA 0, which then uses extlinux, which is explicitly meant for this use case. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=939453
http://bugzilla.opensuse.org/show_bug.cgi?id=939453#c10
--- Comment #10 from Michael Chang
http://bugzilla.opensuse.org/show_bug.cgi?id=939453
http://bugzilla.opensuse.org/show_bug.cgi?id=939453#c11
--- Comment #11 from Michael Chang
(In reply to Michael Chang from comment #2)
The problem is that not all users like the idea to write grub/grub2 to LBA0.
If GRUB by default, then only support their recommended methods. Optionally provide UI for the user to opt out of overwriting LBA 0, which then uses extlinux, which is explicitly meant for this use case.
The UI is already there, we just have to change default proposal to mbr. We don't want to bring yet another loader (extlinux) to mess up maintenance work and we can't simply disable or remove that option from yast installer also because any feature change should go through FATE process to evaluate impact and I believe some people or running setup would still stay to prefer it. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com