Red Hat Bugzilla – Bug 609651
Anaconda picks non-raid device for default boot loader
Last modified: 2010-06-30 16:20:31 EDT
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.
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.
"Install boot loader on /dev/sdb" was displayed
"Install boot loader on /dev/md0"
This was done with a kickstart install but we had the storage section blank so we could do that manually.
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
Nope, looks like what I thought would work does in fact not work. The behavior it's showing seems to be correct.