Bug 429193 - RFE: anaconda should be more generous with boot sectors on RAID installations
RFE: anaconda should be more generous with boot sectors on RAID installations
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-01-17 15:43 EST by Michal Jaegermann
Modified: 2008-07-09 10:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-09 10:48:15 EDT
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 Michal Jaegermann 2008-01-17 15:43:22 EST
Description of problem:

When doing a new installation on a RAID array anaconda writes
a grub boot sector on _one_ of disks.  The problem is that this
quite often this is not that disk which later BIOS attempts
to use as a boot disk.  This is a pretty regular occurence.

With some experience it is pretty clear what happened and how
to fix things but in many real life situtations people were
stumped about what to do with "non-working installations".

It would be really desirable if anaconda would write boot sectors
on _all_ disks which could end up as boot devices, or at least
if there would be a way to request such thing.  Especially in
situations when RAID is used for mirroring it would be also really
good to be able to boot from a mirror disk without necessity
to go through extra hoops in order to make that feasible.  By
that time installation media may be not even around and not
everybody is "grub-wise" enough to prepare for that beforehand;
in particular when a new installation accidentally booted right
away without any hiccups.
Comment 1 Charles R. Anderson 2008-07-09 03:01:10 EDT
I believe this is working already in Fedora 9.  I just did a F9 install on a
RAID1 mirror and it looks like anaconda did install grub to the MBR of both
members of /dev/md0.  In my case grub got installed on /dev/sda and /dev/sdc
with each installation of grub referring to its own device for stage2 and grub.conf.
/boot is on /dev/md0 whose members are /dev/sda1 and /dev/sdc1.
Comment 2 Andy Lindeberg 2008-07-09 10:48:15 EDT
Closing this bug. If the behavior presents itself again, please reopen.

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