ATTO ExpressSAS Troubleshooting Guide for Linux
This document describes troubleshooting techniques that can be used to identify
and resolve issues associated with the ATTO ExpressSAS Raid Controller.
Some of these techniques may seem simplistic or overly obvious, but these are
the ones that are commonly overlooked and can take several hours of frustration
to find. It is important to only try one technique at a time. While changing
multiple variables may seem to be a time saver, it usually complicates the
troubleshooting process.
A.) Linux Operating Systems
Æ The controller driver was loaded properly and everything was working, but the
devices do not show up after the computer was rebooted.
On some Red Hat Linux
distributions, the driver may not automatically load when the system is booted.
To enable driver autoload in Red Hat Enterprise Linux 4 Add the following line to
/etc/modprobe.conf after installing the driver:
alias scsi_hostadapterX esasraid Where X is the next available #.
To enable driver autoload in Red Hat Enterprise Linux 3 Add the following line to
/etc/rc.modules after installing the driver:
modprobe esasraid
(Note: you may need to create /etc/rc.modules and make it executable with
'chmod +x /etc/rc.modules')
Æ On certain 64-bit platforms, the driver Makefile may be unable to detect the
correct CPU architecture. When compiling the driver, an error such as
“cc1 : error : CPU you selected does not support x86_64 instruction set”.
This can be resolved by specifying the correct architecture when running the
make command. For example: $make install ARCH=x86_64
Æ The connected SAS devices aren’t detected by the operating system.
Verify the driver is loaded by examining the output of the Ismod command for
“esasraid”.
Check /proc/scsi/scsi to see a list of devices that are known by the operating
system. This will only list the device at LUN 0 and it’s negotiated speed.
Verify the drives are mapped to the controller correctly. You may need to
execute the ‘automap’ command to remap the drives. This can be done in the
ATTO Configuration Tool or the controller utilities (CTRL-Z).
Page 1 of 7 ATTO Technology, Inc. June 6, 2007
Comments to this Manuals