Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
*** Description of problem:
The UEFI spec requires the StartingCHS field in the protective MBR's
sole partition entry (with type 0xEE) to state cylinder=0, head=0,
sector=2. (Sectors in C/H/S notation are 1-based, not 0-based).
Parted currently sets sector=1 however, which does not conform to the
UEFI spec, and breaks some tools trying to validate the Protective MBR.
*** Version-Release number of selected component (if applicable):
parted-3.1-31.el7
*** How reproducible:
100%
*** Steps to Reproduce:
1. Install RHEL-7 to a UEFI system (including a UEFI virtual machine).
Anaconda will invoke parted for creating the GPT, plus a protective
MBR.
2. On the installed system, check the sector value in the Protective
MBR, with the following command:
# hexdump -C -n 512 /dev/sda
*** Actual results:
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001c0 01 00 ee fe ff ff 01 00 00 00 ff ff 7f 0c 00 00 |..îţ˙˙....˙˙....|
^^
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............UŞ|
00000200
The byte at offset 0x1c0 (marked with ^^) has value 1.
*** Expected results:
The byte at offset 0x1c0 should have value 2.
*** Additional info:
- This issue has been fixed in upstream GNU Parted, in:
http://git.savannah.gnu.org/cgit/parted.git/commit/?id=df6770d213b6
Please backport the patch to RHEL-7. (Fedora already has the fix,
starting with Fedora 27. RHEL-8 also has the fix.)
- The symptom (protective MBR validation failure) has been originally
reported by "Xu, Wei6" <wei6.xu>, at
<https://edk2.groups.io/g/devel/message/39486>. I'll ask the original
reporter to assist with testing the bugfix.
Thanks!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1186
*** Description of problem: The UEFI spec requires the StartingCHS field in the protective MBR's sole partition entry (with type 0xEE) to state cylinder=0, head=0, sector=2. (Sectors in C/H/S notation are 1-based, not 0-based). Parted currently sets sector=1 however, which does not conform to the UEFI spec, and breaks some tools trying to validate the Protective MBR. *** Version-Release number of selected component (if applicable): parted-3.1-31.el7 *** How reproducible: 100% *** Steps to Reproduce: 1. Install RHEL-7 to a UEFI system (including a UEFI virtual machine). Anaconda will invoke parted for creating the GPT, plus a protective MBR. 2. On the installed system, check the sector value in the Protective MBR, with the following command: # hexdump -C -n 512 /dev/sda *** Actual results: 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001c0 01 00 ee fe ff ff 01 00 00 00 ff ff 7f 0c 00 00 |..îţ˙˙....˙˙....| ^^ 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............UŞ| 00000200 The byte at offset 0x1c0 (marked with ^^) has value 1. *** Expected results: The byte at offset 0x1c0 should have value 2. *** Additional info: - This issue has been fixed in upstream GNU Parted, in: http://git.savannah.gnu.org/cgit/parted.git/commit/?id=df6770d213b6 Please backport the patch to RHEL-7. (Fedora already has the fix, starting with Fedora 27. RHEL-8 also has the fix.) - The symptom (protective MBR validation failure) has been originally reported by "Xu, Wei6" <wei6.xu>, at <https://edk2.groups.io/g/devel/message/39486>. I'll ask the original reporter to assist with testing the bugfix. Thanks!