Description of problem: When I tried installing Fedora 21 on a desktop computer with two HDD and one SSD, anaconda crashed. I dig in the logs and found out that Fedora thought that one of my HDD had a bad partition. The problem is that I did not intend to install Fedora on that HDD, but on the SSD which was fine. After I disconnected the two HDD then Fedora installed without issues. After I installed Fedora I connected the two HDDs back and Fedora was able to mount all partitions on those HDDs just fine. So I think Fedora incorrectly thought that one of the HDDs was bad. Also I installed Suse on the same computer and same SDD and it installed without issues. How reproducible: Try to install Fedora on a computer with at least two internal disks (at least one of the disks in a valid state and at least one disk in an invalid state). Actual results: Could not install Fedora on a valid disk when it detects that there is at least one other invalid disks present. Expected results: I expect Fedora to correctly assess the valid/invalid state of a disk. But even in the case where there is a bad disk, I expect Fedora to ignore that disk and allow me to install it on the valid disk if at least one valid disk is present. Additional info: Not sure if this is useful but the Fedora install was performed on existing traditional partitions on the SDD (no LVM, no swap, just "/" and "/home").
Please attach the logs from /tmp to this bug as individual, text/plain attachments.
Created attachment 969803 [details] anaconda.log
Created attachment 969804 [details] ifcfg.log
Created attachment 969805 [details] program.log
Created attachment 969806 [details] storage.log
Created attachment 969807 [details] sensitive-info.log
Is there a file in /tmp at the time of the crash named anaconda-tb-*? Please attach that file.
Created attachment 970368 [details] anaconda-tb-ahRiC0
Created attachment 970369 [details] anaconda-tb-U8rXlc
*** This bug has been marked as a duplicate of bug 1157657 ***