From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
Anaconda tends to put the disks for the /boot md device in the wrong order 
in /etc/raidtab.  Grub is then installed on raid-disk 0 (not /dev/hda, in 
some cases) & the machine can't boot.

How reproducible:
Sometimes

Steps to Reproduce:
1. Place /boot on an md device, RAID1	

Actual Results:  System is sometimes unbootable.  Suppose /dev/md2 
contains /boot.  Anaconda tends to generate this (apparently bad) entry 
in /etc/raidtab:

raiddev             /dev/md2
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hde1
    raid-disk     0
    device          /dev/hda1
    raid-disk     1

Grub is subsequently installed on (hd1,0)

Expected Results:  /etc/raidtab should probably always list /dev/hda as 
raid-disk 0:

raiddev             /dev/md2
raid-level                  1
nr-raid-disks               2
chunk-size                  64k
persistent-superblock       1
nr-spare-disks              0
    device          /dev/hda1
    raid-disk     0
    device          /dev/hde1
    raid-disk     1

Additional info:

This happened twice, on two seperate roswell installs.  Generally it 
happened when I started with no partition tables, but I have no recipe to 
reproduce this one.

It happened 50% of the time for me (2 out of 4).  Linux (grub, really) was 
subsequently unbootable.