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.

Bug 626389

Summary: dracut fails to boot from dmraid sets on minimal installs
Product: Red Hat Enterprise Linux 6 Reporter: Harald Hoyer <harald>
Component: dracutAssignee: Harald Hoyer <harald>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: borgan, hdegoede, pknirsch
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
When booting an IMSM/ISW RAID with dmraid but without mdadm, the mdadm package must still be installed on the system in a kickstart minimal install with the "noiswmd" or rd_NO_MDIMSM" parameters specified.
Story Points: ---
Clone Of: 626201 Environment:
Last Closed: 2011-05-19 11:53:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 626201    
Bug Blocks:    

Comment 3 Harald Hoyer 2011-02-16 10:57:54 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When booting an IMSM/ISW RAID with dmraid but without mdadm, the mdadm package still needs to be installed on the system in a kickstart minimal install with the "noiswmd" or "rd_NO_MDIMSM" parameters specified.

Comment 5 Laura Bailey 2011-05-05 06:20:36 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When booting an IMSM/ISW RAID with dmraid but without mdadm, the mdadm package still needs to be installed on the system in a kickstart minimal install with the "noiswmd" or "rd_NO_MDIMSM" parameters specified.+When booting an IMSM/ISW RAID with dmraid but without mdadm, the mdadm package must still be installed on the system in a kickstart minimal install with the "noiswmd" or rd_NO_MDIMSM" parameters specified.

Comment 6 errata-xmlrpc 2011-05-19 11:53:44 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0523.html