Bug 178079

The first time, I changed (hd1) to point to the RAID array, but apparently it
still used (hd0). So, I then changed the grub.conf created by the installer to
point to (hd0) instead of (hd1) each time, and am now able to boot Windows.
However, booting FC5 results in a kernel panic.

I am not sure if dmraid is still part of the issue, I think it's mostly
anaconda, but it's a slightly different issue than I initially thought.

However, I am unsure why the grub prompt comes up on the first boot; it
obviously installed something or the bootloader would still be what I had
previously installed, but once I install grub manually it works fine (grub does,
not FC5).

Changing to ananconda, because it needs to prevent installation on RAID0 which
grub can't boot off.

I beg to differ, I had grub booting FC4 off RAID 0 just before I installed FC5
test 2. See my guide: http://www.fedorasolved.com/viewtopic.php?t=154 and the
guide I used: http://www.spinics.net/lists/ataraid/msg02310.html
Note this is NVRAID 0, not linux RAID 0.

Also, it should still be able to install on linux RAID 0, just not the /boot
partition, correct?

(In reply to comment #5)
> I beg to differ, I had grub booting FC4 off RAID 0 just before I installed FC5
> test 2. See my guide: http://www.fedorasolved.com/viewtopic.php?t=154 and the
> guide I used: http://www.spinics.net/lists/ataraid/msg02310.html
> Note this is NVRAID 0, not linux RAID 0.

+1, please implement booting from NVRAID, especially because it is known how to 
do. I've got the same configuration as bug reporter only I got kernel panic when 
booting right from the beginning (unable to mount root partition). Will try to 
rebuild initrd now and see if it helps.

Just curious if anyone is looking into making this work. Don't think it would be
too much work; I hope not.

I would like to point out that grub itself seems to be having no issues with
dmraid whatsoever (once it is manually installed), but the initrd doesn't seem
to initialize it; it can't find the partitions to mount, using either labels or
/dev/dm.

These bugs are being closed since a large number of updates have been released
after the FC5 test1 and test2 releases. Kindly update your system by running yum
update as root user or try out the third and final test version of FC5 being
released in a short while and verify if the bugs are still present on the system
.Reopen or file new bug reports as appropriate after confirming the presence of
this issue. Thanks

Test 3 didn't even get as far as Test 2; partially because my new video card
appears to not be supported by the default video driver (I restored my FC4
backup and still had problems, until I updated to the latest nvidia driver).
However, Grub didn't even install, and installing it manually apparently didn't
work; it's not initializing dmraid at all anymore, from what I can tell.
Thankfully, my FC4 backup system is still able to install a grub that loads
dmraid (as is FC5t2), and FC4 still loads flawlessly from it (though not from
FC5t2's grub oddly).

Can you try this on the final FC5 tree?  It works on my nvraid test box without
any failure whatsoever.

Installed with text install (had to temporarily unplug my backup IDE drives, or
it tried to install the bootloader on that MBR, don't know why, and couldn't
change it in text mode), and booted flawlessly! Thanks very very very much, I
did not expect this to be done for FC5's release. Now just the issue of my video
card and the nv driver...