Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1979053 - Missing option to disable marking GPT with pmbr_boot flag
Summary: Missing option to disable marking GPT with pmbr_boot flag
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 35
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 1972377
TreeView+ depends on / blocked
Reported: 2021-07-04 14:59 UTC by Neal Gompa
Modified: 2022-12-13 15:25 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-12-13 15:25:59 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
TianoCore 3474 0 None None None 2021-07-04 15:01:31 UTC

Description Neal Gompa 2021-07-04 14:59:58 UTC
Description of problem:
When installing as hybrid BIOS+UEFI on GPT, Anaconda sets the pmbr_boot flag by default on the volume, which makes it unbootable with OVMF-based UEFI environments (which is nearly all of them).

To solve this, it'd be great to have a flag for "clearpart" that makes it possible to tell Anaconda to tell Blivet to not set the pmbr_boot flag on the disk.

As a suggestion, something like "--no-gpt-pmbr-boot-flag" for clearpart would do the trick.

Version-Release number of selected component (if applicable):

Additional info:
See corresponding ML post about this:

Comment 1 Ben Cotton 2021-08-10 13:10:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Comment 2 Ben Cotton 2022-11-29 16:59:28 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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 EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-12-13 15:25:59 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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.