Oracle Sun Fire X4470 Product Notes page 13

Diagnosing SAS Data Path Failures on Servers Using MegaRAID Disk Controllers
To classify a MegaRAID disk controller event, gather and parse the MegaRAID disk controller
event logs either by running the StorCLI command.
For example, manually gather and parse the controller event log by using the StorCLI
command. At the root prompt, type:
root# ./storcli64/c0 show events file=event.log
Controller=0
Status=Success
Use the existing name of the event log as the name for the disk controller event log. This
Note -
produces a MegaRAID controller event log with the given file name event.log.
To show drive and slot errors separately, at the root prompt, type:
root# /opt/MegaRAID/storcli/storcli64 /c0 /eall /sall show errorcounters
Controller=0
Status=Success
Description=Show Drive/Cable Error Counters Succeeded.
Error Counters:
Drive
/c0/e8/s0
/c0/e8/s1
/c0/e8/s2
/c0/e8/s3
/c0/e8/s4
/c0/e8/s5
/c0/e8/s12
/c0/e8/s13
These error counters reflect drive or slot errors separately.
The following SCSI sense key errors found in the event log in SAS data path failures indicate a
SAS data path fault:
B/4B/05 :SERIOUS: DATA OFFSET ERROR
B/4B/03 :SERIOUS: ACK/NAK TIMEOUT
B/47/01 :SERIOUS: DATA PHASE CRC ERROR DETECTED
B/4B/00 :SERIOUS: DATA PHASE ERROR
A communication fault between the disk and the host bus adapter causes these errors. The
presence of these errors, even on a single disk, means there is a data path issue. The RAID
Error Counter for Drive Error
0
0
0
0
0
0
0
0
Error Counter for Slot
0
0
0
0
0
0
0
0
Sun Fire X4470 Product Notes 13