https://bugzilla.novell.com/show_bug.cgi?id=450963 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450963#c2 --- Comment #2 from Stephan Kulow <coolo@novell.com> 2008-12-02 12:55:48 MST --- rather #450137 -- 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=450963 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450963#c4 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from Jiri Srain <jsrain@novell.com> 2008-12-03 02:33:14 MST --- The attached tarball does not contain YaST logs or any other useful information. Anyway, - if you install bootloader to a logical partition, it cannot be loaded out of the box from principle. You need to configure other system's loader to chainload it to boot and of course ensure that other system's loader is not affected - YaST (but for some exceptions, e.g. Vista or ThinkPads) always writes generic bootloader code to MBR by default, which probably happened to you (if there is some mess there, system cannot boot otherwise). If you want to keep MBR in other situations, you need to ensure it is not affected (but then your system may not boot out of the box), there is a check box to enable/disable writing generic code to MBR. According to the scenarios document, your scenario (GRUB to a logical partition) is not supported and is not supposed to work out of the box. -- 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=450963 User jdsn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450963#c6 J. Daniel Schmidt <jdsn@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #257327|0 |1 is obsolete| | --- Comment #6 from J. Daniel Schmidt <jdsn@novell.com> 2008-12-03 06:45:11 MST --- Created an attachment (id=257704) --> (https://bugzilla.novell.com/attachment.cgi?id=257704) y2logs of this issue Sorry for the wrong logs, I don't know how they mixed up. These are the logs documenting this issue. And to clarify it: The MBR already has a grub installed and chainloaded all other 9 distributions correctly. This worked fine for all Beta versions of openSUSE 11.1 (and previous version and SLE products :) ) I always selected to install grub to the root partition, and the MBR was _never_ touched, but with RC2 it was - thats what I wanted to report.

YaST always writes generic bootloader code to MBR by default, which probably happened to you (if there is some mess there, system cannot boot otherwise)

Even if I select not to do it, as I wanted to keep my MBR?

If you want to keep MBR in other situations, you need to ensure it is not affected

How? In the installation I selected to write grub to the root partition and not to the MBR. This was sufficient for all previous releases. How to it now?

(but then your system may not boot out of the box)

Well, it did, because I know the current MBR is correct (thats why I wanted to keep it). And after I replayed the "backup_mbr" it works again.

there is a check box to enable/disable writing generic code to MBR

According to the scenarios document, your scenario (GRUB to a logical partition) is not supported and is not supposed to work out of the box.

I am not complaining that it does not work out of the box. I wanted to point out that the MBR was changed even though I selected _not_ to do it. I did another test with RC2 to see if it is reproducable - it is! So I reopen this bug. -- 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=450963 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450963#c8 Jiri Srain <jsrain@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |jdsn@novell.com --- Comment #8 from Jiri Srain <jsrain@novell.com> 2008-12-03 08:14:45 MST --- Did you uncheck the "Write generic boot code to MBR" check box in the "Boot loader options"? Yes, we changed the behavior to write generic code to MBR in more cases than we did in the past duting Beta phase, because some systems failed to boot. Anyway, if there was GRUB found, it was always written by default. Saying to install GRUB to boot sector of any partition is not sufficient to be sure MBR keeps untouched (and never was). If installer sees GRUB in MBR, it cannot know whether you have sufficient environment to boot the system or this is a relic of some previous installation. -- 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.