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 19:22:33 +0000
  • Message-id: <20100225192233.39EB3CC7CE@xxxxxxxxxxxxxxxxxxxxxx>

--- Comment #7 from Felix Miata <mrmazda@xxxxxxxxxxxxx> 2010-02-25 19:22:32 UTC
(In reply to comment #4)
Your problem is not (un)checked checkbox "Set active Flag in Partition Table
for Boot Partition" but wrong configuration of GRUB settings.

Grub worked perfectly prior to beginning installation, so there was no reason
to change it.

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.

I disallowed writing to MBR, as writing to MBR was and is not necessary.

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

If yast2-bootloader cannot Grub to /dev/mdx, then it can proceed to tell me so.
That is no excuse to disrupt what already works.

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

My Grub was installed by me on /dev/sda1 precisely so it and I would control
boot as managed by me and only me for multiple distro installations. I do not
mount /dev/sda1 on /boot precisely so that no installation program will disrupt
it. Yet, the openSUSE installer did precisely that, by removing its boot flag,
and preventing the system from booting from the installed and working generic
MBR code.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >