Table of Contents
Advertisement
Troubleshooting Storage Issues
1 0
This section describes how to work around known issues for EVMS devices, software RAIDs,
multipath I/O, and volumes.
Section 10.1, "Is DM-MPIO Available for the Boot Partition?," on page 107
Section 10.2, "Rescue System Cannot Find Devices That Are Managed by EVMS," on
page 107
Section 10.3, "Volumes on EVMS Devices Do Not Appear After Reboot," on page 107
Section 10.4, "Volumes on EVMS Devices Do Not Appear When Using iSCSI," on page 108
Section 10.5, "Device Nodes Are Not Automatically Re-Created on Restart," on page 108
10.1 Is DM-MPIO Available for the Boot
Partition?
In the initial release of SUSE
partition, because the boot loader cannot handle multipath I/O. Therefore, we recommend you set up
a separate boot (/boot) partition when using multipathing. This issue has been resolved in Support
Pack 1 and later.
10.2 Rescue System Cannot Find Devices That
Are Managed by EVMS
The Linux rescue system does not automatically activate volume manager support for LVM or
EVMS. For example, if you are using EVMS as the volume manager for your system device, you
might not be able to see the device in order to mount it under the rescue system.
You must manually activate EVMS in order for the Linux rescue system to detect system devices
that are managed by EVMS.
1 At the terminal console prompt, enter the following as the root user:
evms_activate
10.3 Volumes on EVMS Devices Do Not Appear
After Reboot
If you create volumes on EVMS devices and they cannot be found after you reboot the server, run
chkconfig to make sure that evms_activate runs before FSTAB.
1 At a terminal console prompt, enter either
chkconfig evms on
or
chkconfig boot.evms on
This ensures that evms_activate runs before FSTAB each time your servers reboot.
®
Linux Enterprise Server 10, DM-MPIO is not available for the boot
10
Troubleshooting Storage Issues
107
Advertisement
Chapters
Table of Contents
Troubleshooting
