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 1956573 - anaconda can not install biosboot to multiple disks
Summary: anaconda can not install biosboot to multiple disks
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: beta
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 00:09 UTC by tbsky
Modified: 2023-01-31 08:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-11 17:50:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description tbsky 2021-05-04 00:09:12 UTC 
Description of problem:

with multiple 4TB disks, I want to make software raid and install biosboot to all the disks. anaconda want to do it but forget to make biosboot partition.

Version-Release number of selected component (if applicable):
rhel 8.3 and rhel 8.4 beta1


How reproducible:
everytime


Steps to Reproduce:
1. use rhel 8.3 or 8.4 beta1 to install and select manual partition
2. create biosboot partition to multiple disks (this is default when you create bios biosboot partition)
3. anacoda said it will create biosboot to all disks, but when you click "done", you will see anaconda only make biosboot partition for only one disk.

Actual results:
anaconda make biosboot partition for only one disk


Expected results:
anaconda should make biosboot partition for every disk 


Additional info:
the bug is clone from https://bugzilla.redhat.com/show_bug.cgi?id=1458688
Comment 1 Jan Stodola 2021-05-04 06:32:46 UTC 
(In reply to tbsky from comment #0)

> 2. create biosboot partition to multiple disks (this is default when you
> create bios biosboot partition)
> 3. anacoda said it will create biosboot to all disks, but when you click
> "done", you will see anaconda only make biosboot partition for only one disk.

If a BIOS Boot partition is created, it's created only once (on one disk). The partition name is displayed below the "BIOS Boot" label on the left side of the screen (for example vda1).
If you select the BIOS Boot partition, you can see on what devices it could be created - and this could be confusing, since anaconda says for example:

Device(s):
0x1af4 (vda) and 3 others

But this means the partition could be placed on any of the device, not that the partition will be created on all of them. You can click the "Modify..." button and explicitly specify the disk you want anaconda to use for the partition.

To have BIOS Boot partition on all 4 disks, you have to repeat the following steps:
1. Add new "biosboot" mount point with desired capacity
2. Select the created mount point and click "Modify..."
3. Select only one of the disks and click "Select"
4. Go to 1. and repeat the steps for all the disks and biosboot partitions.

Be aware that anaconda displays only one BIOS Boot partition - the last one created. But if you repeat the steps from above, all 4 BIOS Boot partitions will be created. The problem with hiding BIOS Boot partitions is reported as bug 1926108.

Please let us know if it helps. If not, please attach the installation logs, which are located in /tmp/ in the installation environment.
Comment 2 tbsky 2021-05-04 06:57:49 UTC 
your work arround is what I do these years. it is annoy when there are many disks. 
so why not just fix it and let the result the same as anaconda screen: "0x1af4 (vda) and 3 others". if user just want to install it at only one disk, he can select the disk as usual.
Comment 3 tbsky 2022-01-17 08:30:42 UTC 
test centos-stream9 2022 iso, and the problem is the same.
hope this can be fixed at RHEL 10, or maybe there will no more bios boot machines.
Comment 4 Jiri Konecny 2022-01-21 11:08:44 UTC 
Hi Vojta, could you please check if this issue is in Anaconda or Blivet?
Comment 6 Jan Stodola 2022-03-11 17:50:08 UTC 
The proposal in comment 2 would change the current behavior for other mount points/partitions, which is not desirable.

The problem with showing just one biosboot partition doesn't make the user experience any better in cases like described in this bug, but it will be addressed in a separate bug 1913035.
I've also reported bug 2063288 to clarify that only one disk will be used even if multiple disks are selected in the window with available disks.

I'm closing this bug, as we do not plan to change the behavior.
Thank you for understanding.
Note You need to log in before you can comment on or make changes to this bug.