[Bug 1125669] New: Installation of boot loader failed with Build 414.1
http://bugzilla.opensuse.org/show_bug.cgi?id=1125669 Bug ID: 1125669 Summary: Installation of boot loader failed with Build 414.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: Larry.Finger@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- When installing from openSUSE-Leap-15.1-DVD-x86_64-Build414.1-Media.iso, something happened in the installation of the boot loader. If it logged an error, I failed to note the failure. Yhe installation log is attached. My setup has multiple partitions that can be booted. The MBR contains generic boot code. Installation into one of those partitions should write the boot loader into the partition containing /boot, and set the boot flag on that partition. Due to the installation failure, the boot loader had not been changed. I recovered by booting into TW, using chroot to access the new files, and running YaST from there to update the boot loader. The installer's complaints about not updating the MBR were annoying. If it had an option to update the MBR with generic boot code the way that YaST does, that would quiet the nag. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1125669 http://bugzilla.opensuse.org/show_bug.cgi?id=1125669#c1 Neil Rickert <nwr10cst-oslnx@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx@yahoo.com --- Comment #1 from Neil Rickert <nwr10cst-oslnx@yahoo.com> --- My system booted okay, but I did not like the way that the installer handled that. The initial proposal was to install boot into the MBR. I did not want that, so I set it to install to a partition. I was surprised to notice that it: did not set the option to make the partition active; did not set the option to install generic boot code in the MBR; Those are not a problem for me. I prefer it that way, but I thought that it made poor choices that would cause problems for many users. After exiting from the booting section of install, the summary page indicated that it would boot from "/dev/sda4". This surprised me, because that is not actually the boot partition. Rather, it is the extended partition. So I had to go back into the booting section and directly specify that it should use "/dev/sda5" (the actual boot partition). Yes, I understand why it used the extended partition. But the description it gave in the booting section seemed misleading. I should note that it booted the way that I wanted -- chain loading from another linux (from Leap 15.0). -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com