Sense Data
AIX 5.3 and AIX 6.1
LL00 CCCC CCCC CCCC CCCC CCCC CCCC CCCC CCCC RRRR RRRR RRRR VVSS AARR DDDD KKDD
DDDD DDDD DDDD DDDD PPQQ DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD
DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD
DDDD
DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD
DDDD
DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD
DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD DDDD
DDDD
DDDD DDDD BBBB BBBB BBBB BBBB NNNN NNNN XXXX XXXX XXXX XXXX XXXX XXXX XXXX
XXXX
XXXX XXXX
LL - This is the length of the SCSI command that failed in the CC fields
CC - This denotes the bytes of the SCSI command that failed. The first two digits of the this field indicate the SCSI opcode.
VV - This is the status validity field. It has three possible values
Value | Meaning |
00 | This indicates no status validity was set by the adapter driver. |
01 | This indicates the SCSI status field (SS) is valid |
02 | This indicates the adapter status field (AA) is valid |
03 | This indicates driver status is valid. This is used for when the device driver detects special errors not directly related with hardware errors. |
SS - This is the SCSI status field it has the following possible values
Value | Meaning | What to do |
0x 02 | Device check condition | This is an end device problem, if the issue persists, contact the device vendor for hardware support. |
0x 08 | SCSI device is busy | The target device is busy, if the issue persists, contact AIX SAN support. |
0x 18 | SCSI device is reserved by another Host | This is a SAN configuration issue, if the issue persists, contact AIX SAN support. |
Value | Meaning | What to do |
0x01 | Host Bus Error | an error was detected with the host bus, if the issue persists, contact IOPE. |
0x02 | Transport Fault | This is usually a cable or some other fault in SAN path, if the issue persists, contact AIX SAN support. |
0x03 | Command Timeout | The end device is not responding, this is a SAN issue, if the issue persists, contact AIX SAN support. |
0x04 | No Device Response | The end device is not responding, this is a SAN issue, if the issue persists, contact AIX SAN support. |
0x06 | Software Detected problem | This indicates an AIX or an application issue. Contact AIX SAN support. |
0x07 | World Wide Name Change | This is a due to something changing in the SAN, Review resent SAN configuration changes, if the issue persists, contact AIX SAN support. |
0x09 | Transport reset | This is an informational message, if the issue persists, contact AIX SAN support. |
0x0a | Transport busy | The transport layer is busy, , if the issue persists, contact AIX SAN support. |
0x0b | Transport dead | The transport layer is inoperative, if the issue persists, contact AIX SAN support. |
Value | Meaning | What to do |
0x 01 | Error recovery prevented IO | This is an end device issue. , if the issue persists, contact the device vendor for hardware support. |
0x 02 | Device not ready | This is an end device issue , if the issue persists, contact the device vendor for hardware support. |
0x 03 | Media Error | This is an end device issue , if the issue persists, contact the device vendor for hardware support. |
0x 04 | Device hardware error | This is an end device issue, if the issue persists, contact the device vendor for hardware support. |
PP - This is actually part of the SCSI request sense data. It is the Additional Sense Code (ASC)
QQ - This is actually part of the SCSI request sense data. It is the Additional Sense Code Qualifier (ASCQ).
** NOTE: refer to http://www.t10.org/lists/asc-num.htm for decoding ASC and ASCQ.
SC_DISK_ERRs are logged by the SCSI disk protocol driver.
AIX 5.2 and above has add path info and a new template for MPIO support.
AIX 5.3 and AIX 6.1
Driver status 0x00
This indicates that the AIX FC device driver returned an error to the AIX
disk driver without setting status.
AIX 5.3 and AIX 6.1
LL00 CCCC CCCC CCCC CCCC CCCC CCCC CCCC CCCC RRRR RRRR RRRR VV00 0000 BBBB BBBB
DDDD DDDD EEXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX
XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX
XXXX
XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX
XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX
XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX
XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX XXXX
XXXX XXXX
LL00 CCCC CCCC CCCC CCCC CCCC CCCC CCCC CCCC RRRR RRRR RRRR VVAA0000 BBBB BBBBAIX 5.3 and AIX 6.1
Value | Description | What to do? |
When AA = 0x01 AND VV= 0x03 |
indicates mode data corruption This is reported a SC_DISK_ERR2 when the mode sense data is corrupted |
The device is unusable and will not be configured. Contact AIX SAN support |
MPIO pathing support
Changes to the SC_DISK_ERR template for MPIO, (AIX 5.2 and above)
The Path ID was added to the SC_DISK_ERR template for MPIO. The Path ID
logged is displayed just above the sense data and starts with 0.(see example below) A path ID of 0xffff indicates no path, If this occurs, contact AIX SAN support
A new error log (SC_DISK_ERR7) has been created to indicate that an MPIO
path has failed due to a predetermined number of IO errors. This will normally
be preceded by other related error messages in the AIX error log.
Example of new Template:
LABEL: SC_DISK_ERR2 IDENTIFIER: B6267342 Date/Time: Sun Aug 26 09:42:07 2007 Sequence Number: 9400 Machine Id: 000A7B8D4C00 Node Id: bdsrv2 Class: H Type: PERM Resource Name: hdisk151 Resource Class: disk Resource Type: 2105 Location: U0.1-P2-I1/Q1-W5005076300C3A3B7-L5500000000000000 VPD: Manufacturer................IBM Machine Type and Model......2105800 Serial Number...............50026143 EC Level.....................124 Device Specific.(Z0)........10 Device Specific.(Z1)........0004 Device Specific.(Z2)........0075 Device Specific.(Z3)........30803 Device Specific.(Z4)........05 Device Specific.(Z5)........00 Description DISK OPERATION ERROR Probable Causes DASD DEVICE Failure Causes DISK DRIVE DISK DRIVE ELECTRONICS Recommended Actions PERFORM PROBLEM DETERMINATION PROCEDURES Detail Data PATH ID 0 SENSE DATA 0600 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0108 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 000D 35C0 0000 0007 0000 0000 0000 0000 0000 0000 0000 0000 003C 001A .