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:

I've seen this behaviour for a long time, but a recent thread plus a failed disk in an array last week made me check for a bug, which I didn't find. This might also be better assigned to grub, I'll leave that to the maintainers to decide.

If you create a RAID 1 array backing /boot, the MBR will only be installed on the first drive in the array. This means that, should that disk fail, the user is left with an unbootable system. The fix is relatively simple, boot from rescue/live DVD, run grub, do 'root (hdX,Y) - setup (hdX)' and the system will boot again, but it requires the knowledge to do so, an optical drive (or PXE server) and the appropriate media. Non-trivial for some admins.

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

mdadm-3.2.2-9.el6.x86_64
grub-0.97-75.el6.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Create a RAID 1 array for /boot
2. Fail the first drive (ie: /dev/sda)
3. Reboot
  
Actual results:

System fails to boot, no MBR on RAID member

Expected results:

Bootable /boot partition.

Additional info:

This behavious goes back, at least, to RHEL 4 (which I know is EOL).

Anaconda is the package responsible for installing grub on both hard drives during installation.  This issue has been fixed in the past (in Fedora), but I don't know when and it's possible the fix happened after the rhel6 anaconda was forked from Fedora.

Thanks for reassigning this. It does not seem to have been addressed in RHEL 6 yet, but I will be happy to test next week when I return to my office to confirm.

Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Alright, we're going to need more data to figure out what's happening here.  Please post the various logs from anaconda.  Additionally, if you could zero the MBR's, do a raid 1 install with /boot on the raid, and then dd the first 512 bytes of each disk and attach them, that would be quite helpful.

Moving to CLOSED INSUFFICIENT_DATA.  If you can provide the information requested in the previous comment, reopen the bug and we will pick up on the investigation of the issue.