From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/125.2 (KHTML, like Gecko) Safari/125.7 Description of problem: When creating a set of RAID 1 partitions during installation of Fedora Core 2 Anaconda almost always picks the wrong md# for the boot partition. The only solution I have found is to go back to the Disk Druid step and renumber the RAID partitions so that /boot happens to be the md# that anaconda demands. There doesn't seem to be any logic to which md# anaconda selects either. However it doesn't change within a given installation session. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. install Fedora Core 2 on a machine with two identical SATA drives 2. during the installation use the Disk Druid option to create identical Software RAID partitions on each drive. Use these to create RAID 1 partitions for /boot, /, /swap, /var and /home. 3.In the next anaconda screen after creating the RAID partitions, you will be presented with the md# that anaconda wants to use for the boot partition. Actual Results: The md# partition presented by anaconda for the boot partition is almost always NOT the one which has the /boot mount point. Expected Results: I expected anaconda to be bright enough to look for the /boot mount point when picking the md# partition for the boot partition. Additional info: The only workaround I have found is back up to the Disk Druid step in the anaconda installation and edit the software RAID partitions to have the expected md# that anaconda is demanding for the boot partition.
Investigating.
Commited a fix for this issue to HEAD