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.
Description of problem: After installing the latest release the kernel module for multipath is not loaded.
Version-Release number of selected component (if applicable):
kernel 2.6.32-25.el6.x86_64
device-mapper-multipath-0.4.9-19.el6.x86_64
How reproducible: every install.
Steps to Reproduce:
1.
2.
3.
Actual results:
If you run any multipath command you get this error:
# multipath -ll
May 12 10:40:06 | DM multipath kernel driver not loaded
Expected results:
Additional info:
This is happening because anaconda doesn't create /etc/multipath.conf by default, and without it, the multipath modules isn't installed. You can create a multipath.conf file by running
# mpathconf --enable
Unfortunately, multipath doesn't tell you that there is no config file if the kernel module isn't loaded. Also, mpathconf --enable doesn't load the module (or chkconfig multipathd on and start the daemon). All these things need to happen. Then you will get a helpful error message telling you to run mpathconf, and when you do, multipath will be working correctly.
I just installed nfs --server=storage.bos.redhat.com --dir=/vol/engineering/devarchive/redhat/rel-eng/RHEL6.0-Snapshot-5/6.0/Server/x86_64/os
I still get the same error.
# multipath -ll
May 25 15:03:00 | DM multipath kernel driver not loaded
device-mapper-multipath-0.4.9-21.el6 changed the code around so that it will instruct you to run mpathconf. Running
# mpathconf --enable
will give you a default configuration file, if you don't have any, and it will load the module, and chkconfig multipathd on. If you do
# mpathconf --enable --with_multipathd
It will also start multipathd immediately. If you don't need to modify the default configuration file, this is the way to go. Otherwise, after running mpathconf, you should edit the file to your liking, and then run
# service multipathd start
Since this bug was opened against device-mapper-multipath, and the change for that has been committed, I've cloned a bug to be used for the anaconda fixes. The new bugzilla is #596804
Comment 12releng-rhel@redhat.com
2010-07-02 18:58:04 UTC
Red Hat Enterprise Linux Beta 2 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.