Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 947129 - Installation of F18 on dual-boot system with DH77KC motherboard fails at auto partition - incorrectly says no free space while 600GB is free
Summary: Installation of F18 on dual-boot system with DH77KC motherboard fails at auto...
Keywords:
Status: CLOSED DUPLICATE of bug 978065
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-01 17:42 UTC by davidwriter
Modified: 2013-08-28 17:38 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-28 17:38:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description davidwriter 2013-04-01 17:42:23 UTC 
Description of problem:
Trying  to install F18 on a brand-new system with DH77KC motherboard, i7 processor and 8GB RAM. The system has Win7-64 successfully installed and running. Used Win7 to repartition 2TB drive to leave 600 GB free. 

F18 install OK until reaches the partition phase, then despite it recognizing there is 600 GB free space (red box at bottom of screen), the auto-partition system says that there is 0GB free. Similarly, when trying to manually add a mount point, it thinks that there is no free space. 
 
Version-Release number of selected component (if applicable):


How reproducible:
100% on this system

Steps to Reproduce:
1. start install from verified F18 x_64 DVD
2.
3.
  
Actual results:
Paritioning (and thus installation) fails

Expected results:
Partioning and installation should succeed.

Additional info:
Suspect incompatible system configuration because F17 installation fails immediately - anaconda doesn't start - two line message and system freezes. Win7-64 seems to be working without any apparent problems, although I have done no system-specific tests.
Comment 1 Chris Lumens 2013-04-01 21:24:21 UTC 
Please attach /tmp/storage.log, /tmp/syslog, and /tmp/anaconda.log from when you hit this problem to this bug as individual, uncompressed attachments.  Thanks.
Comment 2 davidwriter 2013-04-18 18:32:46 UTC 
I have been unable to provide this logs from a DVD install - could you please point me to clear instructions on how I might obtain these logs so that I can send them to you?

This bug is related to bug 918390. In that case I formatted the free space as exFAT in Win 7 then tried to reclaim this space for the Fedora install resulting in a crash and the extensive logs that are shown there.

I am totally unable to load Fedora onto this machine and I have no idea why this is.
Comment 3 Russ Anderson 2013-06-25 22:02:04 UTC 
This might be the same issue as BZ 978065.
Comment 4 davidwriter 2013-06-28 20:19:23 UTC 
It is - I found elsewhere that loading anaconda onto a USB and modifying it would allow a work-around so that Fedora would install. The current situation with anaconda is not really satisfactory - it should tell you about the conflict between ms-dos and UEFI installs.
Comment 5 David Shea 2013-08-28 17:38:21 UTC 

*** This bug has been marked as a duplicate of bug 978065 ***
Note You need to log in before you can comment on or make changes to this bug.