[Bug 781376] New: grub2 can't be reinstalled (the generic boot code for MBR is not written)
https://bugzilla.novell.com/show_bug.cgi?id=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c0 Summary: grub2 can't be reinstalled (the generic boot code for MBR is not written) Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain@suse.com ReportedBy: psikodad@gmx.de QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 After installing windows or anything else which destroys the generic grub2 boot code in MBR, linux doesn't boot. After booting with e.g. sysrecuecd and do some chroot commands opensuse 12.2 is running. However, it's not possible to fix the MBR with yast's bootloader for grub2. Reproducible: Always Steps to Reproduce: 1. destroy MBR: dd if=/dev/zero of=/dev/sda bs=1 count=440 conv=notrunc 2. verify that MBR is gone: dd if=/dev/sda bs=1 count=440 |xxd 3. go into yast's bootloader and try to reinstall grub2 (the aim is to rewrite the generic boot code into MBR) 4. the MBR is still ZERO :-((( dd if=if=/dev/sda bs=1 count=440 |xxd 5. now install the legacy grub with yast and the MBR is written! (After this point you can switch again back to grub2 and everything is fine.) Actual Results: yast's bootloader for grub2 does not write the MBR. In opposite, with legacy grub the MBR is written. Expected Results: yast bootloader for grub2 should rewrite the MBR as it does for legacy grub. -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@suse.com |snwint@suse.com -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@suse.com AssignedTo|snwint@suse.com |mchang@suse.com -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c1 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #1 from Michael Chang <mchang@suse.com> 2012-09-21 10:35:22 UTC --- Hi Dominik, How did you re-install grub2 in yast2 .. Did you switch to other bootloader(eg none) and back? Thanks. -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c2 --- Comment #2 from Dominik Platz <psikodad@gmx.de> 2012-09-21 11:24:58 UTC --- if I just change some grub2 options (e.g change the 8 seconds time out to 5) then the MBR is *not* written. Although, the option "write generic bootcode into MBR" was set. if I change to grub as boot loader then the MBR is written. (=ok) if I change to NONE and then back to grub2 => MBR is written. (=ok) -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c3 --- Comment #3 from Michael Chang <mchang@suse.com> 2012-09-24 03:37:05 UTC --- Hi Dominik, Per your description, I think the behavior is correct. We don't write MBR each time you change settings via YaST, but only when a new install is proposed (eg, when you change to use that bootloader). This is to prevent MBR be written by our loader after it has been installed. People may install other loader and do anything we can't anticipate to the MBR so better don't touch it until user asks for a new installation .. Thanks, Michael -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c4 --- Comment #4 from Dominik Platz <psikodad@gmx.de> 2012-09-25 10:36:37 UTC --- Created an attachment (id=506946) --> (http://bugzilla.novell.com/attachment.cgi?id=506946) boot loader options for grub I understand. It makes sense to not write the MBR every time. But there is something which confuse me: Inside the Boot Loader Options the checkbox "Write generic Boot code to MBR" is set, however, the MBR is not written. That's not transparent for me. I would like to make a suggestion: - When choosing a new bootloader (lilo, grub, grub2,..) the checkbox is set. - When keeping the booloader and just changing some options, the checkbox is not set. - After pressing OK and so on, the MBR is written when the checkbox is set. Of course, many other solution proposals are also possible :-) -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c5 Torsten Duwe <duwe@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED CC| |duwe@suse.com Resolution| |INVALID --- Comment #5 from Torsten Duwe <duwe@suse.com> 2012-10-11 13:49:40 UTC --- The _installation_ writes the generic MBR code. This should be obvious. If you destroy it afterward, the system won't boot until you rescue it or reinstall. The MBR code must work for multiple OS installations. The boot loader installation happens at system install time or when its code gets updated. This is loosely correlated but not identical. -- 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=781376 https://bugzilla.novell.com/show_bug.cgi?id=781376#c6 --- Comment #6 from Dominik Platz <psikodad@gmx.de> 2012-10-11 19:34:36 UTC --- Yes, but my point (see #4) was, that this behavior should be more transparent for the user. (I'm not question the behavior itself). -- 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.
participants (1)
-
bugzilla_noreply＠novell.com