This bug splits off the issue reported by jlaska in bug 643967 as its own report, for clarity. As Hans explained:
1) dmraid BIOS RAID installs are broken in the normal installation path, due to unexpected DM_UUID contents, dlehman has a patch
The patch is http://fpaste.org/S0GQ/ - we need James to test that patch. Boot a TC1 live image and then apply that patch and run the installer, James.
Hans explained there's a further issue here:
2) dmraid BIOS RAID installs are broken in the advanced storage path, because there partitions are being ignored even if the raid set is selected in the filter UI
but that doesn't constitute a blocker, and we don't have a proposed fix for it yet.
Proposing this as a blocker under the criterion "The installer must be able to create and install to any workable partition layout using any file system offered in a default installer configuration, LVM, software, hardware or BIOS RAID, or combination of the above", we should take dlehman's fix into F14 RC1 (assuming it works).
Fedora Bugzappers volunteer triage team
Those are two manifestations of the same problem. The only reason we even look to see if the dmraid partitions are in exclusiveDisks is that we cannot tell that they are partitions.
The patch I have proposed to fix the problem is here: http://fpaste.org/S0GQ/
anaconda-14.22-1.fc14 has been submitted as an update for Fedora 14.
anaconda-14.22-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update anaconda'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/anaconda-14.22-1.fc14
anaconda-14.22-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.