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:

Trying to install RHEL 7.0 on a machine with a six-disk system intended to use software RAID appears to be effectively impossible (or if possible, extremely difficult).

I've got a NAS system with 6x 3TB drives with gpt labels. It requires a BIOSBOOT partition, which can not be on a RAID array. There seems to be no way to setup biosboot on multiple disks, so in essence, /dev/sda becomes irreplaceable if it fails (or at least, the system will fail to boot).

In general, installing on a system with software RAID is extremely unintunitive... Having to create a mount point and then alter it, with no mention of this on screen, is hardly user friendly.

In the end, I had to give up and go back to EL6.


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

RHEL 7.0 install disk


How reproducible:

For me, 100%


Steps to Reproduce:
1. Setup a system with 2+ disks
2. Try to setup software RAID in such a way that either/any disk is bootable
3.

Actual results:


Expected results:


Additional info:

While Red Hat welcomes bug reports on Red Hat products here in our public
bugzilla database, please keep in mind that bugzilla is not a support tool or
means of accessing support.  If you would like technical support please visit
our support portal at access.redhat.com or call us for information on
subscription offerings to suit your needs.

I wasn't asking for support, for the record.

Hello Madison.

Yesterday I created a very similar anaconda usability report and I'll try to keep it alive a bit longer than this report was. The partitioning tool design is really hardly digestible for people who work with servers and storages on a daily basis and the new approach (going from mountpoints to partitions) is not very lucky decision.

Regards,
Jaromir.

Thanks, Jaromir.

I found it rather odd that this was closed as "notabug"... At least a mention of where to report usability problems would have been helpful. Do you have a link to your report? I would love to follow it.