[Bug 618286] New: RAID1 installation makes multiboot system completely unbootable (active flag removed with standard MBR code)
http://bugzilla.novell.com/show_bug.cgi?id=618286 http://bugzilla.novell.com/show_bug.cgi?id=618286#c0 Summary: RAID1 installation makes multiboot system completely unbootable (active flag removed with standard MBR code) Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain@novell.com ReportedBy: mrmazda@earthlink.net QAContact: jsrain@novell.com Found By: --- Blocker: --- Created an attachment (id=372494) --> (http://bugzilla.novell.com/attachment.cgi?id=372494) y2logs to reproduce: 1-partition multiboot and suitably format partitions 2-install standard MBR code 3-install DOS and/or Windows and/or OS/2 to standard primary partition(s) 4-install other distros to md devices comprised exclusively of logical partitions 5-configure a bootloader on some primary partition 6-set a primary partition active 7-test that every installed OS will boot 8-install RC1 to an md device comprised exclusively of logical partitions, specifying via the checkbox custom partition in (grub) bootloader configuration and leaving active flag checkbox checked actual behavior: 1-system will not boot anything from any HD 2-active flags are missing from all primary partitions expected behavior: 1-active flags remain as they were prior to installation 2-all previously bootable operating systems remain bootable as before 3-RC1 can be booted via chainload and/or configfile from pre-existing Grub on custom boot partition Notes: On installations to non-primary partitions there should never be any reason to touch active flags on existing primary partitions, particularly when YaST is not called upon to alter any partition tables (make no changes to _any_ partitions). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=618286
http://bugzilla.novell.com/show_bug.cgi?id=618286#c1
Jiri Srain
http://bugzilla.novell.com/show_bug.cgi?id=618286
http://bugzilla.novell.com/show_bug.cgi?id=618286#c2
Felix Miata
You said that you left the active flag checked, which means that you agreed to set the active flag to a partition relevant for your linux system. You should have set it unchecked, this would fulfill your first point of expected behavior.
In Bug 581652 I deselected the boot flag box and wound up unbootable because no active flag was set on any primary partition following installation, even though one was when installation began. There must be broken logic in what YaST is doing as a consequence of the state of the active flag checkbox. Active flag never has relevance to any but a primary partition. Therefore, as long as openSUSE installation is to a / or /boot that is a logical partition, the state of the active flag checkbox should be disgregarded - no action taken in regard to boot flags. Or better yet, a boot flag checkbox should not even be shown if the installation target is a logical. At the very least, the help for the grub settings page should clearly explain the consequences of setting the boot flag box or not.
(or tell me how I can detect that the other bootloader on the system is working and can chainload me, because it may as easily be a non-working relic of some previous installation).
Questions could be asked, such as: 1-Do you wish this installation to be/control your primary bootloader 2-Was your system bootable when you began installation 3-Will your current bootloader be chainloading this installation 4-Will your current bootloader be using this installation's Grub configfile 5-Would you like a grub stanza to paste into your current bootloader for booting this openSUSE installation Note that with standard MBR code, there must always be an active flag set on some primary in order for the system to boot a HD. Steps should be taken when standard MBR code is in place and the installation target is a logical that only affirmative direction to remove a boot flag from a primary should result in there being none set when installation has completed.
Novell - cannot support all of these scenarios; if you provide patches, they will be weocome).
I don't know how to access the source, or program. Nevertheless, if help is really needed because keeping a boot flag set on some primary when standard boot code is in place on the MBR is really so complicated, with help, I might be able to provide some. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=618286
http://bugzilla.novell.com/show_bug.cgi?id=618286#c3
Jiri Srain
http://bugzilla.novell.com/show_bug.cgi?id=618286
http://bugzilla.novell.com/show_bug.cgi?id=618286#c4
--- Comment #4 from Felix Miata
Active flag can be selected also for an extended partition - and I'm aware that some BIOSes can boot this way (generic code in MBR, extended partition set as active and holding GRUB).
As long as an x86 PC HD is not GPT partitioned, in which case primary/logical nomenclature is inapplicable, every partition defined in the end of its very first sector is a primary partition. Thus an extended partition entry in this location is a primary partition entry. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=618286
http://bugzilla.novell.com/show_bug.cgi?id=618286#c
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=618286
https://bugzilla.novell.com/show_bug.cgi?id=618286#c
Jozef Uhliarik
https://bugzilla.novell.com/show_bug.cgi?id=618286
https://bugzilla.novell.com/show_bug.cgi?id=618286#c5
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=618286
https://bugzilla.novell.com/show_bug.cgi?id=618286#c
Josef Reidinger
https://bugzilla.novell.com/show_bug.cgi?id=618286
https://bugzilla.novell.com/show_bug.cgi?id=618286#c6
--- Comment #6 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=618286
https://bugzilla.novell.com/show_bug.cgi?id=618286#c
Ihno Krumreich
https://bugzilla.novell.com/show_bug.cgi?id=618286
https://bugzilla.novell.com/show_bug.cgi?id=618286#c8
Steffen Winterfeldt
participants (1)
-
bugzilla_noreply@novell.com