Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Verified with -84.el6. With this faked /etc/mdadm.conf:
# mdadm.conf written out by anaconda
MAILADDR root
AUTO +imsm +1.x -all
ARRAY /dev/md0 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md1 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md2 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md4 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md5 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md6 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md7 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md8 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md9 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md10 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md11 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md12 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md13 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md14 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md15 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md16 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md17 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md18 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md19 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md20 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md21 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md22 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md23 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md24 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md25 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md26 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md27 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md28 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md29 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md30 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md31 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
ARRAY /dev/md3 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4
I got a init of initrd for kdump kernel. With this snip code in the init:
if [ -f /etc/mdadm.conf ]
then
for i in `awk '/^ARRAY[[:space:]]/{print $2}' /etc/mdadm.conf`
do
MD_MIN=`echo $i | sed -e 's/^[^0-9]*\([0-9]\+\)$/\1/'`
mknod $i b 9 $MD_MIN
done
fi
I can get the correct MD_MIN.
Comment 5releng-rhel@redhat.com
2010-11-11 14:46:05 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Verified with -84.el6. With this faked /etc/mdadm.conf: # mdadm.conf written out by anaconda MAILADDR root AUTO +imsm +1.x -all ARRAY /dev/md0 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md1 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md2 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md4 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md5 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md6 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md7 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md8 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md9 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md10 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md11 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md12 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md13 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md14 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md15 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md16 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md17 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md18 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md19 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md20 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md21 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md22 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md23 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md24 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md25 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md26 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md27 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md28 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md29 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md30 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md31 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 ARRAY /dev/md3 level=raid5 num-devices=3 UUID=3ea5cf72:552f6677:231e2956:a010eee4 I got a init of initrd for kdump kernel. With this snip code in the init: if [ -f /etc/mdadm.conf ] then for i in `awk '/^ARRAY[[:space:]]/{print $2}' /etc/mdadm.conf` do MD_MIN=`echo $i | sed -e 's/^[^0-9]*\([0-9]\+\)$/\1/'` mknod $i b 9 $MD_MIN done fi I can get the correct MD_MIN.