https://bugzilla.novell.com/show_bug.cgi?id=462574 User aorlovskyy@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462574#c1 Alexander Orlovskyy changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aorlovskyy@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |yast2-maintainers@suse.de --- Comment #1 from Alexander Orlovskyy 2009-01-09 07:20:38 MST --- Reassign to yast2-maintainers -- 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=462574 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462574#c3 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO Info Provider| |Winfrid.Tschiedel@fujitsu-s | |iemens.com --- Comment #3 from Jozef Uhliarik 2009-01-12 02:56:53 MST --- Winfrid, are you sure that you didn't change option "Boot from Extended Partition" to "Boot from Root Partition" please? IMO it is case of your problem. The yast2-bootloader proposed install generic boot code to MBR activate extended partition and install GRUB stage1 to extended partition and other parts to your logical partition /dev/sda9. If you did change "Boot from Extended Partition" -> "Boot from Root Partition" you created unbootable system. I understand why users change setting of installing bootloader but please take care also about options in tab "Boot Loader Installation" -> button "Boot Loader Options" and there are 2 important checkboxes like "Write Generic Boot Code to MBR" and "Set active Flag..." It is cause why your changes in yast2-bootloader was not enough and result was unbootable system. :( I know it is not userfriendly and UI for installing bootloader will change to next release. There is plan to have all options for installation in one tab. -- 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=462574 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462574#c5 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Winfrid.Tschiedel@fujitsu-s | |iemens.com --- Comment #5 from Jozef Uhliarik 2009-01-12 07:31:30 MST --- Winfrid, the main goal of bootloader proposal is propose settings of bootloader which will be able boot system (just installed) [there should be added also your old installed OS from SUSE]. Generally: yast2-bootloader always check your MBR during installation. if MBR includes GRUB stage1 or LILO or other bootloader instead of "generic boot code" it will propose rewrite MBR by "generic boot code". Only if your MBR include "generic boot code" only change "active flag". Your original settings from yast2-bootloader was valid: - write "generic boot code" to MBR - set active flag to your extended partition - install GRUB stage1 to extended - continue in your logical partition (your "/") What do you did: - change install GRUB from extended to "/" Result: - generic code is in MBR - active flag point to your extended and there is nothing and machine is unbootable -------------------------------------------------------- NEXT: after my comment# 3 - unselect checkboxes: "Write Generic Boot Code to MBR" and "Set active Flag..." - select "Boot from Root Partition" instead of "Boot from Extended Partition" Result: - your MBR still includes your old settings - GRUB is installed to your new "/" but you still boot old OS (if it is still valid) but there is not added new boot section for your new installed OS ;-) -------------------------------------------------------- What I propose: please let yast2-bootloader to propose settings for booting your new OS ;-) I am sure that it can do it correctly. I know that in some cases users want change settings of installing bootloader. Please let me know what exactly do you want to change in yast2-bootloader or why you tried to change proposed settings of yast2-bootloader. BTW. the change of UI -> It means better and more userfriendly UI could be in next release. -- 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=462574 User Winfrid.Tschiedel@fujitsu-siemens.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462574#c7 --- Comment #7 from Winfrid Tschiedel 2009-01-12 09:24:49 MST --- Hi Jozef, I forgot just one point - as you might have seen, I am working for Fujitsu Siemens. My computers are just test systems with more than one OS. When I get a new system, I start in the following way : allocate a small partition for boot ( which I do not use during the installation ) allocate a larger partition for my first distribution. Later I copy the content of the boot partition to the first partition, write a boot record to the second partition, and change the MBR to point to the first partition. the menu.lst of the first partition will be now used for chainloading of my linux distributions. If I have also a WINDOWS, I install first my WINDOWS and have at least 1 small linux partition on the first disk ( this partition must contain a boot record ), this boot record (512bytes) I copy to my Windows and now I can boot my linux distributions from WINDOWS (boot.ini) All following linux distribution I install using an own partition and write the boot record to the root partition and add just another entry in the menu.lst of partition 1. -- 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=462574 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462574#c9 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID --- Comment #9 from Jozef Uhliarik 2009-01-12 10:23:07 MST --- Winfrid, I know that it seems to be chaos and panic but it is result of a lot of settings and options. Please don't forget that original settings of yast2-bootloader was correct and without your changes system should be bootable. IMO: installation of openSUSE is simple: just click next, next, next... I am sorry you decided make changes ;-) -- 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.