Mailinglist Archive: opensuse-bugs (4691 mails)

< Previous Next >
[Bug 581652] installer should never unset boot flags on otherwise untouched primary partitions
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 25 Feb 2010 16:52:47 +0000
  • Message-id: <20100225165247.D28B4CC7CD@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=581652

http://bugzilla.novell.com/show_bug.cgi?id=581652#c4


Jozef Uhliarik <juhliarik@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution| |INVALID

--- Comment #4 from Jozef Uhliarik <juhliarik@xxxxxxxxxx> 2010-02-25 16:52:47
UTC ---
I try to explain it.
"Set active Flag in Partition Table for Boot Partition" means set boot flag. It
is the fact that it is not important if you write GRUB to MBR but there exist
BIOS-es that doesn't support boot from device if there missing boot flag. It is
reason why activating devices is set to true by default.

You can uncheck checkbox and boot flag for device is not set (skip activating).

Your problem is not (un)checked checkbox "Set active Flag in Partition Table
for Boot Partition" but wrong configuration of GRUB settings.

You are using MD RAID and it is software raid. In this case GRUB doesn't know
to boot directly from MD RAID devices and configuration is written to real
devices /dev/sda and /dev/sdb.

yast2-bootloader propose correct configuration and it is to write GRUB to MBR.
Your changes "Boot from Root Partition broken booting.

Boot from MBR means write GRUB to MBR but Boot from Root Partition means write
GRUB to "/" partition. If you deselect "Boot from MBR" your MBR is not updated
and it can include random data or previous boot code which can point to other
device.

Finally it means your machine tried to boot but your MBR is not updated and it
leads to known result.

I am sorry but you haven't a lot of options for configuration of GRUB if your
boot or "/" partition is on MD RAID.

There could be also combination write generic boot code to MBR and set boot
flag but ... it is really complicated settings if your boot or "/" partition is
logical partition and it doesn't work if there is used MD RAID.

I am sorry the problem is broken GRUB configuration by user. Configuration is
valid but it is not bootable ;-)

BTW your root is on /dev/md2 (/dev/sdb9 & /dev/sda9) and finally GRUB was
written to your "/" partition

setup --stage2=/boot/grub/stage2 --force-lba (hd0,8) (hd0,8)

as I wrote before it is written to real devices because GRUB doesn't know to
boot from software MD RAID.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References