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.

Created attachment 691082 [details]
failed boot w/ rdshell rdinitdebug rdudevinfo

Description of problem:
dracut is unable to boot from a degraded raid1 array unless it is run one time by hand. after that it can boot fine from a degraded array.

Version-Release number of selected component (if applicable):
dracut-004-284.el6_3.1.noarch

How reproducible:
always

Steps to Reproduce:
1.) setup 3x raid1 of 2 discs, md0:/boot md1:swap md2:/
2.) install system
3.) unplug sdb and power on the system
4.) add rdshell to grub cmd
5.) drop in the rdshell, all md devices are inactive
6.) run mdadm --run /dev/md0, mdadm --run /dev/md1, mdadm --run /dev/md2
7.) now all md devices are active and degraded
8.) exit -> can not find root device
9.) exit -> boots fine
10.) after the system boots up, login and reboot again
11.) works now without rdshell
  
Actual results:
all raid devices are inactive on rdshell

Expected results:
active all raid devices as degraded and boot the system

Additional info:
it only works if the raid ist assembled and run one time from hand. wherever you do that. in the rdshell or with a live cd. for me it looks like mdraid_start.sh ist never run.

Created attachment 691083 [details]
successfully boot w/ rdshell rdinitdebug rdudevinfo

after assemble and run the array one time by hand, all works fine again

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Created attachment 696037 [details]
Patch in upcoming dracut in RHEL-6.4

dracut for RHEL-6.4 will have the follwing patch, which should resolve the issue.

my 65-md-incremental-imsm.rules looks already like this. if i try to apply this patch:

  patching file modules.d/90mdraid/65-md-incremental-imsm.rules
  Reversed (or previously applied) patch detected!  Assume -R? [n]

# rpm -q dracut
dracut-004-284.el6_3.1.noarch

"rpm -V dracut" is silent.

Oh.. what is your kernel command line?

Looks like you set "root=/dev/md2", which explains why dracut stops assembling, as soon, as /dev/md2 is available (although not accessible).

You really should set "root=LABEL=<fslabel>" or "root=UUID=<fsuuid>".

ok, works fine now. i've tested both LABEL= and UUID=

thanks and sorry for the noise