Bug 894629

Summary: Unable to install FC18-RC4: Error checking storage configuration
Product: [Fedora] Fedora Reporter: adam@omega.org.uk <adam.bishop>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-21 17:12:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Photo Bundle
none
Log Bundle none

Description adam@omega.org.uk 2013-01-12 18:49:02 UTC 
Description of problem:
I am trying to install FC18-RC4 x86_64 on a UEFI system, but have run into another issue.

The partitioner seems unable to proceed, despite a valid partition layout being provided for it to use.

This issue seems to completely block me from installing FC18.

Version-Release number of selected component (if applicable):
18.37.11

How reproducible:
Always

Steps to Reproduce:
Attempt to install FC18. Partition/Free Space layout, number of drives, type of drives doesn't seem to affect anything.
  
Actual results:
Unable to install FC18

Expected results:
Should be able to install FC18

Additional info:
See log and photo bundles.
Comment 1 adam@omega.org.uk 2013-01-12 18:51:35 UTC 
Created attachment 677461 [details]
Photo Bundle
Comment 2 adam@omega.org.uk 2013-01-12 18:52:56 UTC 
Created attachment 677462 [details]
Log Bundle
Comment 3 Chris Lumens 2013-01-14 14:47:04 UTC 
*** Bug 894628 has been marked as a duplicate of this bug. ***
Comment 4 Chris Lumens 2013-01-14 15:21:00 UTC 
Do you have any device of type biosboot on one of your target hard drives?  That's what the error message in 4.jpg is telling you to do.  It's not enough to have a /boot.