https://bugzilla.novell.com/show_bug.cgi?id=450137 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c1 Danny Kukawka changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Blocker Priority|P5 - None |P2 - High Flag| |SHIP_STOPPER? --- Comment #1 from Danny Kukawka 2008-11-28 12:50:29 MST --- Seen the same problem. -- 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=450137 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c3 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coolo@novell.com --- Comment #3 from Stephan Kulow 2008-11-28 13:17:28 MST --- danny, attach your logs too. -- 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=450137 User cstender@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c5 --- Comment #5 from Christopher Stender 2008-11-28 13:21:22 MST --- Created an attachment (id=256692) --> (https://bugzilla.novell.com/attachment.cgi?id=256692) /var/log (only stage1) -- 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=450137 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c6 --- Comment #6 from Danny Kukawka 2008-11-28 13:30:38 MST --- (In reply to comment #2 from Andreas Jaeger)

If you mark it as shipstopper, you have to put in the requestee as well

--> then bugzilla has a bug. it should either set it automatically to the responsible person of the product or it shouldn't allow to set the field without a person added to the responsible field.

This is Critical (data loss) according to http://en.opensuse.org/Bugs/Definitions

Why is it critical? Blocker fits perfectly for me. From http://en.opensuse.org/Bugs/Definitions#Blocker: * Prevents developers or testers from performing their jobs. Impacts the development process. * Example: Unable to login (in this case: unable to boot the system) -- 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=450137 User sorenson2743@amtelecom.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c8 Erik Sorenson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sorenson2743@amtelecom.net --- Comment #8 from Erik Sorenson 2008-11-29 14:10:49 MST --- I have a multi-boot configuration and installed (DVD/x86) 11.1 RC1 into a custom partition (dev/sda12), made sure install into root (/dev/dsa12) was only one ticked, confirmed when it returned to the installation selection summary. But it trashed my MBR. Much later, when rebooting the PC, it just went to a blinking cursor on a black screen after POST. Fortunately, I've been stung before by events like this so I had taken a backup of my MBR beforehand, and it was simple to restore and then use Bootpart to put the 11.0 entry into the NTloader boot.ini file on the C: (DOS, fat16) partition of the drive. If you want my SMolt, I'll give it. More detail, and my generally unfavourable experiences, are here: http://forums.opensuse.org/pre-release-beta/400708-things-annoying.html#post... -- 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=450137 User sorenson2743@amtelecom.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c10 --- Comment #10 from Erik Sorenson 2008-11-29 14:37:40 MST --- Created an attachment (id=256753) --> (https://bugzilla.novell.com/attachment.cgi?id=256753) Files re: trashed MBR -- 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=450137 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c12 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@novell.com |juhliarik@novell.com --- Comment #12 from Josef Reidinger 2008-12-01 04:00:38 MST --- jozo - grub doesn't call with (hd0) so it doesn't rewrite MBR. Also I find that examine mbr return Windows Vista, so you shouldn't rewrite MBR. If you are sure that you doesn't rewrite MBR, then please ask duwe if this is related to bug 450091 -- 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=450137 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c13 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #13 from Jozef Uhliarik 2008-12-01 10:39:16 MST --- it is not about rewriting MBR there is valid MBR from Vista. The proposal of yast2-bootloader is updated and installation will be write to extended partition and "/" on logical partition. The basic problem is that it is not supported scenario (primary /boot partition is missing and "/" is on logical partition) Please be carefull if you propose your partitions next time. Fix in yast2-bootloader 2.17.44 -- 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=450137 User cstender@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c15 --- Comment #15 from Christopher Stender 2008-12-01 14:02:43 MST --- Jozef, what do you mean with "Please be carefull if you propose your partitions next time."? What's the problem with writing the bootloader to "/" of a logical partition? -- 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=450137 User cstender@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c17 --- Comment #17 from Christopher Stender 2008-12-02 06:49:57 MST --- I guess all of us who run into this bug use a setup with two grubs where the first one (in a primary partition) chainloads the second one (in a logical partition). I'm still not sure why I have to be carefull when I create my partition setup. Can you please clarify this? Also I'm not sure what the fix below in yast2-bootloader has to do with this issue we see here because I've no vista code in my MBR (because no Vista is installed). - added fix for proposal if MBR include Vista code and "/" is on logical partition (bnc #450137) Sorry for the questions, but I would like to get the point where I made something wrong. I only expect that YaST installs grub into the partition I selected. -- 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=450137 User sorenson2743@amtelecom.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c19 --- Comment #19 from Erik Sorenson 2008-12-02 07:37:41 MST --- I do *not* have Vista, never have. If the "resolved" status only involves Vista being on a system, then it is *not* resolved. I have XP. The MBR pointer is to the first partition on my disk which is a primary partition, DOS/FAT16, and the only active (boot) partition defined. And I want it to stay that way when I instruct OS 11.1 to put it's Grub code in the extended partition ("/") into which the install is going. Standard stuff. Jozef, if you are saying your fix addresses this, fine. If not, then this problem log is *not* resolved, and its status should be changed. To clarify, upon booting the system goes to the NTloader code in this first partition. From there, via a prompt that comes from boot.ini, I select which OS I am going to use. If it is a Linux OS, then I get its Grub screen and I have to press "enter". Works fine, since W2K days and I ran DOS, multi-Linux (mix of Lilo and Grub installs too), XP, Win9x, no OS "owns" the bootloader. -- 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=450137 User cstender@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c21 Christopher Stender changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Blocker Status|RESOLVED |REOPENED Resolution|FIXED | Version|RC 1 |GMC --- Comment #21 from Christopher Stender 2008-12-05 10:50:22 MST --- This bug is not fixed. Same procedure as last time. I installed openSUSE 11.1 GMC (on /dev/sda9) and edited grub to store the bootloader into the root partition (nothing else was activated). After rebooting the system I got the "Non-System disk or error" message. System is a HP nx7300 notebook. Logs will follow. -- 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=450137 User cstender@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c23 --- Comment #23 from Christopher Stender 2008-12-05 11:09:29 MST --- Created an attachment (id=258349) --> (https://bugzilla.novell.com/attachment.cgi?id=258349) yast logs (openSUSE 11.1 GMC) -- 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=450137 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c25 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |cstender@novell.com --- Comment #25 from Stephan Kulow 2008-12-05 13:34:56 MST --- does sda9 have a bootloader or not? -- 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=450137 User pg.radadia@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c27 --- Comment #27 from pragnesh radadiya 2008-12-05 22:26:38 MST --- i have also experience problem with opensuse 11.1 GMC livecd -- 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=450137 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c29 --- Comment #29 from Jozef Uhliarik 2008-12-07 07:26:38 MST --- There was fate about supported scenarios for bootloader and one of the requests was that primary /boot or "/" partition have to exist. -> It is cause why I wrote be carefull if you haven't "/" on primary partition or your /boot partition doesn't exist. You play with unsupported scenario. Next if you install openSUSE or SLES to logical partition and /boot partition doesn't exist too. yast2-bootloader propose install "generic boot code" to MBR install stage1 to your extended partition (also activate it) and other parts of GRUB to your logical partition ("/"). It is only proposal please try to understand that it is not possible propose of GRUB installation perfect for all users. -- 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=450137 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c32 --- Comment #32 from Danny Kukawka 2008-12-07 10:38:14 MST --- And what was the meaning/goal of this change (which fate was it?)? Not only that it change the old/default behavior in a very late state of the release cycle. As it looks to me nobody expected this change of former default behavior. Is there no way to change yast2 if "Install to root partition" is selected (and nothing else) to check if there is a boot partition and if not to simply do what the user expect (don't touch the mbr or the boot flag, install grub to '/')? Or is there any case where this behavior is useful by default? IMO the current behavior is unexpected to the most users and it makes it much harder to install openSUSE/SLE. Is this change documented somewhere, so that it would be easy to see that the behavior changed to former products? -- 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=450137 User sorenson2743@amtelecom.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c34 --- Comment #34 from Erik Sorenson 2008-12-07 14:06:32 MST --- I certainly understand that everyone is under the gun to let 11.1 final ship, and I don't wish that impeded. But, if I'm fooled, then I think a lot of users (some of whom may be Windows converts), are going to be *really* surprised. I also believe that the #32 comment and suggestion re: logic is spot-on. IIRC, this is the way it operated before. I never remember having to go beyond specifying a root bootloader location before in OpenSuse. It's certainly the way that Fedora 10 installed on my system a few days ago, and Mandriva before that. And I don't recall having this problem implementing 11.0 or 10.3, the former being my production OS now. I believe it is *very* dangerous expecting that users will click through to an additional, non-obvious panel when they are lead to believe, as I was, that "install to root" means just that. -- 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=450137 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c36 --- Comment #36 from Danny Kukawka 2008-12-08 02:23:27 MST --- I expect two things: a) that such changes are not made that late in the release cycle. Especially without any big-fat-blinking-warn-dialog that the default behavior (the way former releases worked since the stone age) changed and that the user may need to check "this or that" dialog/checkbox to get the former behavior. b) that yast work the same way as in the past (that I can say: "write the bootloader to the root partition" and yast do what I want it to do, especially if I don't say: "write to mbr") The point is: this change is a surprise for IMO the most of the users. Without any warning, without documentation (sorry, I couldn't find any, maybe I've overseen it) and with no that much time to be tested. -- 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=450137 User cstender@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c38 --- Comment #38 from Christopher Stender 2008-12-08 02:58:14 MST --- Stanislav, please look at the attached logs. Maybe there is something which shows that the mbr is touched. JFYI: there are also two backup files (_dev_sda and _dev_sdaX) in /var/lib/YaST2/backup_boot_sectors. IMHO it's not consistent if you deselect "write grub to mbr" (because you want YaST to write grub to the root partition) and Yast automatically selects (hidden under bootloader options) "write generic grub to mbr". Anyway, we need a solution for openSUSE now. I can live with the current setup if it works and does not lead to the "no operating system found" message. -- 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=450137 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c40 --- Comment #40 from Stephan Kulow 2008-12-08 04:18:15 MST --- my install worked fine -- 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=450137 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c42 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Blocker |Major Priority|P1 - Urgent |P3 - Medium --- Comment #42 from Stephan Kulow 2008-12-08 04:52:16 MST --- the bug in its generic form is WORKSFORME. There may be different problems to different people, but the code works and the defaults did not change. -- 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=450137 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450137#c44 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|pg.radadia@gmail.com | Resolution| |WORKSFORME --- Comment #44 from Jozef Uhliarik 2008-12-08 06:17:09 MST --- Finally the bug #450137 was about missing analyse of MBR if user select install system to logical partition. It was bug in yast2-bootloader. It is fixed in yast2-bootloader 2.17.44. The problem was that yast2-bootloader didn't analyse content of MBR: - system "may not" boot It was possible change it manually: select tab "Boot Loader Installation" and select only checkbox "Boot from Master Boot Record" (if you want GRUB in MBR) or click to button "Boot Loader Options" and there you can select checkboxes "Set active Flag in Partion Tabel for Boot Partition" and "Write Generic Boot Code to MBR" (if you want install generic boot code to MBR) Last description is in proposal (yast2-bootloader 2.17.44) also check other situation at http://en.opensuse.org/YaST/Bootloader_MBR My basic goal is boot system to the second stage of installtion. If you want specific settings for bootloader you can change it manually in yast2-bootloader during installation or if it is not possible then it can be feature request. I am sorry yast2-bootloader doesn't support all settings and options for booting. To comment #32 It is possible write GRUB to "/" without touching MBR but it is not case of proposal you need to open yast2-bootloader and click on tab "Boot Loader Installation" (at least activated flag will be changed) - select only checkbox "Boot from Root Partition" after that click on button "Boot Loader Options" - deselect "Set active Flag in Partion Tabel for Boot Partition" - deselect "Write Generic Boot Code to MBR" You also need to be sure that your content of MBR is correct and after reboot the machine will continue in installation. It is cause why yast2-bootloader rewrites MBR if it is necessary. See FATE #304499 The bug is closed as WORKFORME and I am waiting to 3 new bugs from: Erik Sorenson, Christopher Stender and Danny Kukawka -- 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.