Bug 609651 - Anaconda picks non-raid device for default boot loader
Summary: Anaconda picks non-raid device for default boot loader
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-30 18:44 UTC by Mike McGrath
Modified: 2010-06-30 20:20 UTC (History)
0 users

Clone Of:
Last Closed: 2010-06-30 20:20:31 UTC

Attachments (Terms of Use)

Description Mike McGrath 2010-06-30 18:44:03 UTC
Description of problem:

I've got a /dev/sd[a-c].  In that I have a partition on sdb and sdc which are raided as /dev/md0 and mounted on my /boot.  Anaconda was attempting to install the boot loader on /dev/sdb instead of /dev/md0

Version-Release number of selected component (if applicable):

Whatever version comes with the RHEL6 beta 2 that launched today.

How reproducible:

Only tested once so far.

Steps to Reproduce:
1.  Create /dev/sdb1 and /dev/sdc1
2.  Software raid them (raid1) at /boot ext4
3.  click next to the boot loader screen.
Actual results:

"Install boot loader on /dev/sdb" was displayed

Expected results:

"Install boot loader on /dev/md0"

Additional info:

This was done with a kickstart install but we had the storage section blank so we could do that manually.

Comment 2 RHEL Product and Program Management 2010-06-30 19:03:19 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 3 Mike McGrath 2010-06-30 20:20:31 UTC
Nope, looks like what I thought would work does in fact not work.  The behavior it's showing seems to be correct.

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