Bug 894629 - Unable to install FC18-RC4: Error checking storage configuration
Summary: Unable to install FC18-RC4: Error checking storage configuration
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 894628 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-12 18:49 UTC by adam@omega.org.uk
Modified: 2013-08-21 17:12 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-21 17:12:45 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Photo Bundle (8.05 MB, application/zip)
2013-01-12 18:51 UTC, adam@omega.org.uk 		no flags Details
Log Bundle (104.38 KB, application/zip)
2013-01-12 18:52 UTC, adam@omega.org.uk 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.