Bug 756298 - Unable to allocate boot partition
Summary: Unable to allocate boot partition
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-23 07:44 UTC by Philip Sherman
Modified: 2013-02-13 08:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 08:41:39 UTC
Type: ---


Attachments (Terms of Use)

Description Philip Sherman 2011-11-23 07:44:49 UTC
Description of problem:
Graphical installation requires using gpt disk labeling/partitioning on 750g disk drive with existing mbr partitions.

Version-Release number of selected component (if applicable):
Installation disk: Fedora-16-x86_64-DVD.iso

How reproducible: Fails every time, using any install option


Steps to Reproduce:
1. Boot system from DVD
2. Select to install on free space or custom partitioning, or update existing
3. gpt error when exiting disk partitioning
  
Actual results:
Unable to continue with install

Expected results:
Install continues, using defined mount points.

Additional info:
System is Lenovo Z570 with 750g HDD. System had three primary and one extended partition allocated across entire disk. 500g+ available in extended partition. Desired partitioning is 250m boot partition  with LVM using the rest of the extended partition. Separate logical volumes for /, /tmp, /home, swap.

Install from live CD using "install in free space" option successfully installed with grub2 as primary boot. Windows accessible after adding boot option for (hd0,1), the regular Win 7 boot device.

Comment 1 Jesse Keating 2012-07-19 21:32:20 UTC
Can you re-test with F17?  If it still fails, we need the logs from /tmp/*log (individual attachments).

Comment 2 Philip Sherman 2012-07-22 00:10:59 UTC
I won't be able to download the F17 disks for at least 10 days. I'll do that and post the results of an install using F17. It may be three weeks until I can get to the computer that had the problem to try a new install.

Comment 3 Fedora End Of Life 2013-01-16 10:12:11 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-13 08:41:54 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.