[Bug 362898] New: boot config not written to empty MBR
https://bugzilla.novell.com/show_bug.cgi?id=362898 User mvidner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=362898#c357249 Summary: boot config not written to empty MBR Product: openSUSE 11.0 Version: Alpha 2 Platform: i586 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: juhliarik@novell.com ReportedBy: mvidner@novell.com QAContact: jsrain@novell.com Found By: --- +++ This bug was initially created as a clone of Bug #357249 +++ I install Alpha 2 in VirtualBox to an empty hard drive. Yet the boot code is proposed to be installed to the boot partition only, which will make the system unbootable. It must go to the master boot record. The logs are in attachment 195604. The MBR detection appears to work correctly: 2008-02-11 14:38:51 "MBR examining script returned 254, Definitely invalid" but other code apparently ignores it. -- 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=362898 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=362898#c1 Jozef Uhliarik <juhliarik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mvidner@novell.com --- Comment #1 from Jozef Uhliarik <juhliarik@novell.com> 2008-03-27 06:03:29 MST --- Martin, are you sure that you sent me completed yast logs? There are missing calling write functions from bootloader. :( BTW: there is some comments about 254 from examine_mbr.pl // examine_mbr.pl returns // - != 0 (errno, e.g. 2) for a read error: "cannot read 512 // bytes from <dev>" // - 254 for an "invalid MBR", i.e. without enough entropy to // contain boot code // - 0 for a "Generic MBR" (DOS MBR) // - 254 for a GRUB or lilo "stage 1" // - 0 for an unknown 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=362898 User mvidner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=362898#c2 Martin Vidner <mvidner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mvidner@novell.com | --- Comment #2 from Martin Vidner <mvidner@novell.com> 2008-03-28 08:52:33 MST --- Yes, the logs are incomplete, I took them right after the proposal. Well, that comment (from lilolike.ycp) is internally inconsistent. If some code follows its advice, no wonder that it does not work. Then there are some comments in examine_mbr.pl itself, which suggest that 0 means don't replace, 254 means replace, and anything else means error; which is then contradicted by the CODE of examine_mbr.pl which returns 1 for LILO. Oh what fun :-/ -- 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=362898 Stanislav Visnovsky <visnov@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |visnov@novell.com Component|Installation |Booting -- 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=362898 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=362898#c3 Jozef Uhliarik <juhliarik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from Jozef Uhliarik <juhliarik@novell.com> 2008-06-03 07:09:36 MDT --- OK after discussion with jsrain and analyse the code. The problem is only in returned code from examine_mbr.pl. There are same returned codes for different situations but handling of returned code is good (in your case). bootloader propose write generic MBR. see in logs: 2008-02-11 14:38:52 <1> linux(2530) [YCP] bootloader/grub/misc.ycp:864 (2) globals: $[ "activate":"true", "boot_boot":"true", "boot_extended":"false", "boot_mbr":"false", "boot_root":"false", "generic_mbr":"true" ] "generic_mbr" means rewrite your MBR with generic code. Changing returned codes from examine_mbr.pl should be in 11.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.
participants (1)
-
bugzilla_noreply＠novell.com