Table of Contents
Advertisement
10.4 Volumes on EVMS Devices Do Not Appear
When Using iSCSI
If you have installed and configured an iSCSI SAN, and have created and configured EVMS disks
or volumes on that iSCSI SAN, your EVMS volumes might not be visible or accessible after reboot.
This problem is caused by EVMS starting before the iSCSI service. iSCSI must be started and
running before any disks or volumes on the iSCSI SAN can be accessed.
To resolve this problem, use the
that is part of your iSCSI SAN to correct the order that iSCSI and EVMS are started.
1 At a terminal console prompt, enter
chkconfig boot.evms on
This ensures that EVMS and iSCSI start in the proper order each time your servers reboot.
10.5 Device Nodes Are Not Automatically Re-
Created on Restart
Effective in SUSE
automatically re-created on boot. It is no longer necessary to modify the
script to delete the device nodes on system reboot as was required for previous versions of SUSE
Linux.
The following procedure is provided for users who might encounter this issue for SUSE Linux
Enterprise Server 9 and earlier:
1 Open the
2 Add the following lines to the Stop section:
mount -n -o remount,rw /
echo -en "\nDeleting devices nodes"
rm -rf /dev/evms
mount -n -o remount,ro /
For example, the Stop section looks like this after the edit:
stop)
echo -n "Stopping EVMS"
mount -n -o remount,rw /
echo -en "\nDeleting devices nodes"
rm -rf /dev/evms
mount -n -o remount,ro /
rc_status -v
;;
3 Save the file.
4 Continue with
126 SLES 10 SP3: Storage Administration Guide
chkconfig
®
Linux Enterprise 10, the
/etc/init.d/boot.evms
"Restart the Server" on page
command at the Linux server console of every server
directory is on
/dev
tmpfs
script in a text editor.
22.
and the device nodes are
/etc/init.d/boot.evms
Advertisement
Table of Contents
Troubleshooting
