Chapter 5. Managing Multipath I/O for Devices / 5.9. Configuring Multipath I/O for an Existing Software RAID
	5.8. Configuring Multipath I/O for the Root Device		5.10. Scanning for New Devices without Rebooting

Configuring Multipath I/O for an Existing Software RAID

Ideally, you should configure multipathing for devices before you use them as components of a software RAID device. If you add multipathing after creating any software RAID devices, the DM-MP service might be starting after the multipath service on reboot, which makes multipathing appear not to be available for RAIDs. You can use the procedure in this section to get multipathing running for a previously existing software RAID.

For example, you might need to configure multipathing for devices in a software RAID under the following circumstances:

If you create a new software RAID as part of the Partitioning settings during a new install or upgrade.
If you did not configure the devices for multipathing before using them in the software RAID as a member device or spare.
If you grow your system by adding new HBA adapters to the server or expanding the storage subsystem in your SAN.

	Note
The following instructions assume the software RAID device is `/dev/mapper/mpath0`, which is its device name as recognized by the kernel. Make sure to modify the instructions for the device name of your software RAID.

Open a terminal console, then log in as the root user or equivalent.
Except where otherwise directed, use this console to enter the commands in the following steps.
If any software RAID devices are currently mounted or running, enter the following commands for each device to dismount the device and stop it.
```
umount /dev/mapper/mpath0
```
```
mdadm --misc --stop /dev/mapper/mpath0
```
Stop the boot.md service by entering
```
/etc/init.d/boot.md stop
```
Start the boot.multipath and multipathd services by entering the following commands:
```
/etc/init.d/boot.multipath start
```
```
/etc/init.s/multipathd start
```
After the multipathing services are started, verify that the software RAID’s component devices are listed in the /dev/disk/by-id directory. Do one of the following:
- Devices Are Listed: The device names should now have symbolic links to their Device Mapper Multipath device names, such as /dev/dm-1.
- Devices Are Not Listed: Force the multipath service to recognize them by flushing and rediscovering the devices.
  To do this, enter the following commands:
```
multipath -F
```
```
multipath -v0
```
  The devices should now be listed in /dev/disk/by-id, and have symbolic links to their Device Mapper Multipath device names. For example:
```
lrwxrwxrwx 1 root root 10 Jun 15 09:36 scsi-mpath1 -> ../../dm-1
```
Restart the boot.md service and the RAID device by entering
```
/etc/init.d/boot.md start
```
Check the status of the software RAID by entering
```
mdadm --detail /dev/mapper/mpath0
```
The RAID’s component devices should match their Device Mapper Multipath device names that are listed as the symbolic links of devices in the /dev/disk/by-id directory.
Make a new initrd to ensure that the Device Mapper Multipath services are loaded before the RAID services on reboot. Enter
```
mkinitrd -f mpath
```
Reboot the server to apply these post-install configuration settings.
Verify that the software RAID array comes up properly on top of the multipathed devices by checking the RAID status. Enter
```
mdadm --detail /dev/mapper/mpath0
```
For example:
Number Major Minor RaidDevice State
0 253 0 0 active sync /dev/dm-0
1 253 1 1 active sync /dev/dm-1
2 253 2 2 active sync /dev/dm-2