On Fri, 2007-07-06 at 12:27 -0400, Clyde E. Kunkel wrote: > Sean Bruno wrote: > > <snip> > > Third, and the most annoying, was that I couldn't install a plain s/w > > raid configuration with 2 drives connected. There was just no way to > > keep the system from assuming that I meant to use /dev/mapper/mapper0 > > even after I ensured that the superblock metadata was wiped out with a > > quick call to 'dmraid -Er /dev/sdX' to be sure that it was really gone. > <snip> > > Sean > > > > On my x86 box, I used the "nompath" parameter during install to prevent > /dev/mapper/mapper0 from being used and then could see all disks > properly, including pre-existing software raid arrays. Seems that even > if you are not using the bios raid capability of a SATA setup, anaconda > thinks you want to. Must be a way to check the bios to see if the setup > is for raid or not. That didn't work for me. I am still presented with the /dev/mapper/mapper0 device as my only install target. Sean -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
