Bug 727688 - Anaconda crash when adding a BIOS boot partition on non EFI BIOS
Summary: Anaconda crash when adding a BIOS boot partition on non EFI BIOS
Status: CLOSED DUPLICATE of bug 722963
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 16
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-02 21:18 UTC by Othman Madjoudj
Modified: 2011-08-03 02:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-08-03 02:23:51 UTC

Attachments (Terms of Use)
anaconda log (13.43 KB, text/x-log)
2011-08-02 21:19 UTC, Othman Madjoudj
no flags Details
anaconda yum log (367 bytes, application/octet-stream)
2011-08-02 21:21 UTC, Othman Madjoudj
no flags Details
anaconda traceback (236.03 KB, text/plain)
2011-08-02 21:22 UTC, Othman Madjoudj
no flags Details
screen shot (64.88 KB, image/png)
2011-08-02 21:23 UTC, Othman Madjoudj
no flags Details

Description Othman Madjoudj 2011-08-02 21:18:48 UTC
Description of problem:

Anaconda used in Fedora 16 Alpha TC1 is forcing GPT in non EFI BIOS (KVM guest with 18G disk space), in order to be able to boot I needed to add a BIOS boot partition but Anaconda crash 

Steps to Reproduce:
1. Start Fedora Installer in KVM guest (virt-install / pxeboot)
2. Try to create partition scheme manually: /boot (ext4), SWAP, / (ext4), BIOS boot

Additional info:
Attached required logs and screenshot

Comment 1 Othman Madjoudj 2011-08-02 21:19:38 UTC
Created attachment 516395 [details]
anaconda log

Comment 2 Othman Madjoudj 2011-08-02 21:21:09 UTC
Created attachment 516396 [details]
anaconda yum log

Comment 3 Othman Madjoudj 2011-08-02 21:22:52 UTC
Created attachment 516397 [details]
anaconda traceback

Comment 4 Othman Madjoudj 2011-08-02 21:23:53 UTC
Created attachment 516398 [details]
screen shot

Comment 5 David Lehman 2011-08-03 02:23:51 UTC
BIOS boot partitions should be of size 1MB. If you choose this size you will not hit this error, which will be fixed soon.

*** This bug has been marked as a duplicate of bug 722963 ***

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