NEC Storage M100 Series User Manual page 295

User Guide
Problem
When the OS is started, the message
"Path Not Found" is displayed and
accessing the SPS device fails.
SPS cannot be started when a
certain RPM is updated.
Release 6.0
Cause and Solution
Check the disk array unit is recognized by the OS.
Refer to the file "/proc/scsi/scsi" and check if "Vendor: NEC"
and "Model: DISK ARRAY" are shown. If the disk array unit
is not recognized, they are not shown. When they are not
shown, check the FC cables are connected correctly.
The SPS recognizes the path information at its first startup,
and creates and retains the information in a status setting
file. If correct connection to the disk array unit fails to be
configured in the first OS startup after installation of SPS, it
can cause incorrect path information to be recorded. In this
case, delete the setting file recorded in the SPS, and then
restart the OS.
If the problem persists even after checking and performing
above mentioned, please contact the Support Service.
Updating initscripts or iscsi-initiator-utils in a RHEL
environment may disable the settings of automatic startup
for SPS, and SPS may not be started automatically when
the OS is started.
Check /etc/rc.d/rc.sysinit to see the settings of automatic
startup for SPS are configured. Run the following command
and if there is no output, it indicates the settings of
automatic startup for SPS are not configured.
# grep mkdd /etc/rc.d/rc.sysinit
If the settings of automatic startup for SPS have not been
configured, configure them again and restart the OS. See
the followings for setting automatic startup for SPS.
# cd /etc/rc.d
<Red Hat Enterprise Linux 5 (FC connection)>
# patch -b -p0 <
/opt/nec/sps/patch/rc.sysinit.rhel5.diff
<Red Hat Enterprise Linux 5 (iSCSI connection)>
# patch -b -p0 <
/opt/nec/sps/patch/iscsi.rhel5.diff
When you run the patch command but an error message is
shown, it indicates the patch file is not applied correctly. In
this case, add the line with "+" shown on the first row of the
patch file to /etc/rc.d/rc.sysinit or /etc/rc.d/init.d/iscsi.
If the problem persists even after checking and performing
above mentioned, please contact the Support Service.
295
Chapter 10 Troubleshooting