Bug 727688

Summary: Anaconda crash when adding a BIOS boot partition on non EFI BIOS
Product: [Fedora] Fedora Reporter: Othman Madjoudj <athmanem>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, jonathan, 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: 2011-08-03 02:23:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
anaconda log
none
anaconda yum log
none
anaconda traceback
none
screen shot none

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 ***