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.
Bug 1926108 - Anaconda only shows one biosboot-partition
Summary: Anaconda only shows one biosboot-partition
Keywords:
Status: CLOSED DUPLICATE of bug 1913035
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-08 09:13 UTC by moritz
Modified: 2021-05-04 06:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-04 06:34:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Result of creating two biosboot-partitions (78.00 KB, image/png)
2021-02-08 09:13 UTC, moritz 		no flags Details
View All

Description moritz 2021-02-08 09:13:00 UTC 
Created attachment 1755664 [details]
Result of creating two biosboot-partitions

Description of problem:
The Anaconda-installer only shows one biosboot-partition at a time even if the user creates multiple ones.

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

Steps to Reproduce:

1) Start the installation on a BIOS-System with multiple drives and inst.gpt on the kernel commandline.
2) Select multiple drives during the installation, LVM partitioning scheme and custom storage configuration.
3) Select the "+", "biosboot" from the Mount Point drop-down menu and "1 MiB" as capacity. Click "Add mount point".
4) Select "Modify" under devices and select only the first drive. Click "Update Settings". See screenshot biosboot1 for the result.
5) Create a biosboot-partition using the exact same method but select only the second drive. See screenshot biosboot2 for the result.

Actual results:
The partition manager will only show the second partition (biosboot2.png), not the one that has been created on the first drive. If we delete the second partition, the first one will be visible again.
Both partitions will be created.

Expected results:
The partition manager shows the two different biosboot-partitions on their individual drives instead of showing only one partition.

Additional information:
The goal is to have a biosboot-partition with GRUB on each drive. The system is supposed to run on RAID 1 for the case that one of the drives fails so that the system can boot from the other one. The installation of GRUB on the second drive will be done manually.
Comment 1 Jan Stodola 2021-05-04 06:34:38 UTC 
Thanks for the bug report.
This problem is already reported as bug 1913035, so I'm closing it as a duplicate.

*** This bug has been marked as a duplicate of bug 1913035 ***
Note You need to log in before you can comment on or make changes to this bug.