http://bugzilla.novell.com/show_bug.cgi?id=618286 http://bugzilla.novell.com/show_bug.cgi?id=618286#c1 Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Jiri Srain 2010-06-30 14:04:11 UTC --- 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. I hope you agree that typical unexperienced Linux user has at most one additional operation system and there is a primary partition available. When you have a different bootloader, you need to assure yourself that it won't be broken by the configuration (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). Sorry, in your scenario, YaST provides you options to make it behave as you want to. What it does by default is best effort to make its installation of openSUSE boot (and, in some scenarios, I agree that it fails; however, we - Novell - cannot support all of these scenarios; if you provide patches, they will be weocome). -- 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 changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@novell.com AssignedTo|jsrain@novell.com |juhliarik@novell.com --- Comment #3 from Jiri Srain 2010-07-01 07:01:42 UTC --- 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). However, this is not what we are committed to support (see the wiki page at http://en.opensuse.org/Bootloader/Scenarios). What is missing is the check box description explicitly stating which partition will be activated (in your cases, the extended partition) I don't think that the default installation should ask too many question - OTOH, having an easy way to switch a bootloader profile (having "standalone boot" by default, "chainloaded by another" as optional, maybe others). If you want to contribute, I suggest you should have a look at http://en.opensuse.org/Svn.opensuse.org and at the yast-devel@opensuse.org mailing list. It's probably not about being complicated, but about handling issues bothering larger audience. Jozef, please, have a look at better description of the widgets. -- 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 changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|RAID1 installation makes |make clear action action to |multiboot system completely |be taken resulting from |unbootable (active flag |"set active flag" checked |removed with standard MBR |or not |code) | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=618286 https://bugzilla.novell.com/show_bug.cgi?id=618286#c5 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|REOPENED |ASSIGNED --- Comment #5 from Josef Reidinger 2010-10-01 07:38:17 UTC --- Hi, I am now maiintaining yast2-bootloader, so my view: in general I think it is bug if no partition is selected as active and yast2-bootloader should check it and report problem if there is no active-flag. Also please consider that bootloader module is "expert" one and common users doesn't need it, so it is expected to have at least minimum booting knowledge and responsibility for actions. Your expectation that system can be boot via chainload or config file is possible if you choose boot from logical partition, which warn you and works ( I hope, if not please report it). So I add check if there is set active flag. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=618286 https://bugzilla.novell.com/show_bug.cgi?id=618286#c6 --- Comment #6 from Felix Miata 2010-12-18 16:01:13 UTC --- Created an attachment (id=405509) --> (http://bugzilla.novell.com/attachment.cgi?id=405509) y2logs This happened again, but on system with no md devices. IIRC, in summary section I did not touch the links regarding boot loader location, waiting until in boot loader installation to select options. I left set active flag checked, selected / as location, and the installer moved the flag from where it was (sda3, which contained Grub, and menu.lst with a chainloader stanza pointing to the current installation's / target), and needed to remain, to the extended (sda4). The meaning of "Custom Boot Partition lets you choose a partition to boot from" in Help remains unclear as to whether menu.lst and Grub would be put there, or whatever is already there might be altered by the current installation process. Help still does not explain the significance of the set active flag checkbox, or whether selecting "Write generic Boot Code to MBR" will write regardless or leave it alone if generic code is already present there. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=618286 https://bugzilla.novell.com/show_bug.cgi?id=618286#c8 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #8 from Steffen Winterfeldt 2014-08-15 11:28:16 CEST --- hope this works with grub2 now -- 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.