Filter
Top Products
SCSI Sense Data Format: Errors that are logged with the following labels have SCSI
sense data in the detail data field in the error log:
DISK_ERR1 SSA_DISK_ERR2
DISK_ERR4 SSA_DISK_ERR3
SSA_DISK_ERR1 SSA_DISK_ERR4
SCSI sense data consists of 32 bytes of data. See “Error Log Analysis” on page 229 to
find out how this data is used.
SSA Error Code Format: Errors that are logged with the following labels have SSA
error code data in the detail data field in the error log:
SSA_ARRAY_ERROR SSA_HDW_ERROR
SSA_CACHE_BATTERY SSA_HDW_RECOVERED
SSA_CACHE_ERROR SSA_LINK_ERROR
SSA_DEGRADED_ERROR SSA_LINK_OPEN
SSA_DETECTED_ERROR SSA_LOGGING_ERROR
SSA_DEVICE_ERROR SSA_REMOTE_ERROR
SSA_ENCL_ERR1 SSA_SETUP_ERROR
SSA_ENCL_ERR2 SSA_SOFTWARE_ERROR
The SSA Error code data format consists of three bytes of error code followed by up to
153 bytes of debug data. See “Error Log Analysis” on page 229 to find out how this
data is used.
run_ssa_healthcheck cron
The run_ssa_healthcheck program checks for SSA subsystem problems that do not
cause I/O errors, but cause some loss or redundancy or functionality. It reports such
errors each hour until the problem is solved. During SSA device driver installation, the
following entry is added to the cron table:
0****/usr/lpp/diagnostics/bin/run_ssa_healthcheck 1>/dev/null 2>/dev/null
This run_ssa_healthcheck program sends a command to the adapter. The command
causes the adapter to write a new error log entry for any problems that it can detect,
although those problems might not be causing any failure in the user’s applications.
Such problems include:
v Adapter hardware faults
v Adapter configuration problems
v RAID array problems
v Fast-write cache problems
v Open serial link conditions
v Link configuration faults
v Disk drives that are returning Check status to an inquiry command
226 User’s Guide and Maintenance Information
::
::