Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 225550 - bootrecord always written to MBR, when dmraid is installed
bootrecord always written to MBR, when dmraid is installed
Status: CLOSED DUPLICATE of bug 225548
Product: Fedora
Classification: Fedora
Component: grub (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
Depends On:
  Show dependency treegraph
Reported: 2007-01-31 05:08 EST by Winfrid Tschiedel
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-02-04 10:33:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Winfrid Tschiedel 2007-01-31 05:08:40 EST
Description of problem:

Even if during installation write bootrecord to boot-section is selected,
an existing MBR is overwritten.

Version-Release number of selected component (if applicable):
fedora core6 installation dvd

How reproducible:
Always, same error was also seen on rhel 5.

Steps to Reproduce:
1. Install fedora core 6 on a system with SATA Raid.
2. Install a second fedora core 6 on the same system and select
   write bootrecord to bootsection.
3. reboot
Actual results:
   The second fedora installation will be bootet.

Expected results:

   Boot of the first fedora Installation.
    To get access to 2. installation, you should
    only insert 3 lines in /boot/grub/menu.lst of the 1. installation

title Fedora (2. Installation)
    root (hd0,x)
    chainloader +1 

Additional info:
    similar problems occur on openSUSE 10.2
Comment 1 Johan Kok 2007-02-04 10:33:16 EST
Thank you for reporting this issue. It appears your issue was stored three times in our bug tracker. I'm 
closing this one as a duplicate of bug #225548

*** This bug has been marked as a duplicate of 225548 ***

Note You need to log in before you can comment on or make changes to this bug.