FC5 on fakeraid

[Dan]

I already posted a bug about this ( 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178079 ), but just 
throwing it out there:
With FC5 test 2 (for x86_64 in my case), anaconda is able to install 
onto my NVRAID 0 array (one of many so-called "fakeraid" implementations 
of onboard RAID, handled by dmraid), and flawlessly too. Except, 
apparently, for grub, because booting after installation is complete 
sends me into a grub prompt. If I use that prompt to install grub and 
reboot, I can boot my Windows installations fine, but FC5 kernel panics 
because it can't find any labeled partitions (especially /). So it now 
seems like dmraid is working in grub, but not in the startup of Fedora.
I know it is possible for this to work, because I have had FC4 booting 
flawlessly for months previous to my attempt to install FC5. However, I 
had to go through several steps to get it to work; I followed a guide 
(intended for RHEL4 on Sil RAID 0) at 
http://www.spinics.net/lists/ataraid/msg02310.html and wrote my own at 
http://www.fedorasolved.com/viewtopic.php?t=154 . These steps involve 
installing the OS on a non-raid hard drive, creating partitions on the 
RAID hard drive using this installation's dmraid ability, copying each 
partition over, installing grub on the raid drive, applying a patch to 
/sbin/mkinitrd (and using it to make a initrd file), and making 
grub.conf and fstab point to the correct dmraid partitions. After doing 
this, FC4 booting flawlessly, and I only had issues when I had to 
interface with it in rescue mode because I would have to access dmraid 
in a non-raid installation before i could even see the raid partitions.
So again, just throwing it out there to people who know what they're 
doing in development.
-Dan