Troubleshooting SLES Multipathing (MPIO) problems
This document (3231766) is provided subject to the disclaimer at the end of this document.
Ensure that the multipath-tools package is installed:
Hotplug (SLES 9 only)
Verify that HOTPLUG_USE_SUBFS is changed from yes tonoin /etc/sysconfig/hotplug.
(Note: This change requires a reboot)
Make sure that the driver for the HBA is added to INITRD_MODULES in /etc/sysconfig/kernel. In most cases this is qla2xxx or qla2400. When this setting is made, rebuild the ramdisk by executing mkinitrd.
As an example, a server with a SmartArray disk controller, a Reiserfs root filesystem, and a Qlogic HBA might have: INITRD_MODULES="cciss reiserfs qla2xxx"
(Note: After running mkinitrd the system must be reboot)
Ensure that boot.multipath and multipathd are set to start on boot:
The services can be started immediately with:
Using Multipathed Devices
When using a MPIO device, always use the devices listed under /dev/disk/by-name/. These devices will never change when a path is failed over. Strange behavior will occur if a traditional SCSI device node (e.g., /dev/sdc) is used.
As an example, a proper device node is /dev/disk/by-name/3600601607cf30e00184589a37a31d911. If this device has a partition on it the first partition is /dev/disk/by-name/3600601607cf30e00184589a37a31d911p1. The identifier comes from the WWID of the device.
Partitioning a MPIO device is described in Chapter 5.4.2 and 5.11 of the Storage Administration guide at:
On SLES 10 SP2, please follow the steps below:
Create a partition table for the device by entering
Add a /dev/dm-* link for the new partition by entering
/sbin/kpartx -a -p -part /dev/dm-8
Verify that the link was created by entering
ls -lrt /dev/dm-*
LUNs are not seen by the driver
lsscsican be used to check whether the SCSI devices are seen correctly by the OS. When the LUNs are not seen by the HBA driver, check the zoning setup of the SAN. In particular, check whether LUN masking is active and whether the LUNs are correctly assigned to the server.
LUNs are seen by the driver, but there are no corresponding block devices
When LUNs are seen by the HBA driver, but not as block devices, additional kernel parameters are needed to change the SCSI device scanning behavior, e.g. to indicate that LUNs are not numbered consecutively. Refer to TID 3955167, Troubleshooting SCSI (LUN) scanning issues for details.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:3231766
- Creation Date: 02-Apr-2008
- Modified Date:10-Mar-2021
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com