Bug 734548
Summary: | Label not created for biosboot partition | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andrew McNabb <amcnabb> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | 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-30 20:09:50 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrew McNabb
2011-08-30 18:07:19 UTC
BIOS boot partitions cannot have labels. A label is a feature of a filesystem and there is no filesystem on a bios boot partition. The only way to identify a BIOS boot partition is to check for the bios_grub flag using parted or some other partitioning utility. If you have a bios boot partition on your disk anaconda should not complain that you didn't mention it in your kickstart. (In reply to comment #1) > > If you have a bios boot partition on your disk anaconda should not complain > that you didn't mention it in your kickstart. That's really good to know. I'll update documentation to share this critical information. (In reply to comment #2) > (In reply to comment #1) > > > > If you have a bios boot partition on your disk anaconda should not complain > > that you didn't mention it in your kickstart. > > That's really good to know. I'll update documentation to share this critical > information. Your zeal is appreciated, but take it easy. This information belongs in the install guide, so wherever you added it may be somewhere it does not belong. (In reply to comment #3) > > Your zeal is appreciated, but take it easy. This information belongs in the > install guide, so wherever you added it may be somewhere it does not belong. I hope I didn't put it in a bad place, but it's better for it to be _somewhere_ than nowhere. As you can tell, I've struggled with the GPT change because of the complete lack of any documentation or communication about the issue. It still doesn't have a feature page, and I haven't seen any sign of release notes. I'm not against the change from MBR to GPT, but it really is a significant change. |