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:

If a software raid device is in degraded state at the time of the "rear mkrescue" creation (e.g. a device has been removed from a RAID1 array), the disk layout restoration will fail with following error seen in the log:

mdadm --create /dev/md127 --force --metadata=1.2 --level=raid1 --raid-devices=2 --uuid=a0fc5637:fdf5dafa:a345e010:83293548 --name=boot /dev/sdb1
+++ echo Y
mdadm: You haven't given enough devices (real or missing) to create this array


This is indeed due to the missing device (/dev/mapper/mpatha1)


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

rear-2.00-3.el7_4.x86_64


How reproducible:

ALWAYS


Steps to Reproduce:
1. Set up a software raid with 2 devices in RAID1
2. Remove one of the device (/dev/sda1)
3. Create rear rescue image
4. Try restoring the disk layout

Actual results:

initramfs's /var/lib/rear/layout/disklayout.conf will contain:

raid /dev/md127 metadata=1.2 level=raid1 raid-devices=2 uuid=a0fc5637:fdf5dafa:a345e010:83293548 name=boot devices=/dev/sdb1
...

leading to mdadm complaining and aborting.


Additional info:

Issue to be created in Upstream as well

1536023 merged upstream in 2.4/643d778e6a39a869bd9e5962436285fbb44fa71c

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-2018:3293