Disk setup pre-Anaconda: sda: boot drive, currently has 100MB ext3 and rest is LVM, but will get wiped during install and repartitioned md0 (RAID1): sdb sdc md1 (RAID1): sdd sde sdb, sdc, sdd, sde all have 1 partition (Software RAID) taking up their entire disk space. All RAID disks are the same size, 18GB. md0 and md1 were (in a previous install attempt) both members of the same LVM Volume Group. The idea was to simulate RAID 1+0 by using LVM to stripe the logical volumes across the RAID1 arrays. So they still have LVM data on the the disk, and this seems to be what confuses Anaconda. 1) Start anaconda 2) AutoPartition, choose _only_ sda, choose "erase all partitions on this system" 3) Hit next 4) Boom Peter said something about problems with finding LVs by name (since the existing LVM stuff on md0/md1 had the same name as what Anaconda tried to create on sda) and that got anaconda confused.
This report targets the FC3 or FC4 products, which have now been EOL'd. Could you please check that it still applies to a current Fedora release, and either update the target product or close it ? Thanks.
requested by Jams Antill
This should be fixed in a later release.