Yeah, it's a RAID controller... I'm running XP and XP 64-bit off the
same RAID 0 array that FC5 test 2 is currently installed on but not
running. And yeah, it's test 2. I looked in the mkinitrd which was what
was patched to allow initialization of dmraid in FC4, and it looks like
theres some code that deals with dmraid, but for some reason the initrd
can't find any partitions after grub boots it and it goes through a
bunch of hardware initialization. I can try to find a bootup log using
my FC4 installation if you give me a hint where to look for it.
Peter Jones wrote:
On Fri, 2006-02-10 at 17:14 -0500, Dan wrote:
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.
Does the BIOS actually have the controller listed as a "RAID"
controller, rather than an IDE controller? Usually this type of failure
means it was set up as a raid, and then the "raid" functionality was
turned off without removing the metadata.
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.
You're sure that was test 2, not some newer rawhide snapshot? (the last
couple of days have been somewhat broken for installing on dmraid;
today's is as well, but tomorrow's should work ok for most people...)
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list