Bug 960691

Summary: Re-word error message when BIOS boot partition is not created to reflect that GPT is no longer a Fedora default
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, g.kaviyarasu, jonathan, mkolman, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: python-blivet-0.13-1.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-15 17:28:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Williamson 2013-05-07 17:09:14 UTC 
So back in...F16? F17? something like that? we tried defaulting to GPT disk labels for BIOS installs.

It didn't work out very well, so in the next release, we went back to MS-DOS labels by default. But during the fun of that release, we wrote a nice error message that's displayed if you're doing a BIOS-on-GPT install but you didn't create a BIOS boot partition:

"Your BIOS-based system needs a special partition to boot with Fedora's new disk label format (GPT). To continue, please create a 1MB 'BIOS Boot' type partition."

When we went back to MS-DOS labels by default, we didn't change that message. It still reads exactly the same in F18, F19 etc. We should probably re-word it to reflect that GPT is no longer the default. Perhaps just:

"Your BIOS-based system needs a special partition to boot from a disk with the GPT disk label format. To continue, please create a 1MB 'BIOS Boot' type partition."

would be good enough. It's probably a rare error message to see, these days; I triggered it intentionally because I wanted to check whether this case just gives the generic 'stage1 bootloader' error or not.
Comment 1 Fedora Update System 2013-05-09 18:47:18 UTC 
python-blivet-0.13-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-blivet-0.13-1.fc19
Comment 2 Fedora Update System 2013-05-10 00:54:49 UTC 
anaconda-19.25-1.fc19, python-blivet-0.13-1.fc19, pykickstart-1.99.30-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/python-blivet-0.13-1.fc19,pykickstart-1.99.30-1.fc19,anaconda-19.25-1.fc19
Comment 3 Fedora Update System 2013-05-10 15:30:50 UTC 
Package anaconda-19.25-1.fc19, python-blivet-0.13-1.fc19, pykickstart-1.99.30-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-19.25-1.fc19 python-blivet-0.13-1.fc19 pykickstart-1.99.30-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-7834/python-blivet-0.13-1.fc19,pykickstart-1.99.30-1.fc19,anaconda-19.25-1.fc19
then log in and leave karma (feedback).
Comment 4 Fedora Update System 2013-05-15 17:28:37 UTC 
Package python-blivet-0.13-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python-blivet-0.13-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-7854/python-blivet-0.13-1.fc19
then log in and leave karma (feedback).