Go to main content

Sun Server X3-2 (formerly Sun Fire X4170 M3) Product Notes

Exit Print View

Updated: October 2018

Diagnose SAS Data Path Failures on Servers Using MegaRAID Disk Controllers

On Oracle x86 servers using MegaRAID disk controllers, Serial Attached SCSI (SAS) data path errors can occur. To triage and isolate a data path problem on the SAS disk controller, disk backplane (DBP), SAS cable, SAS expander, or hard disk drive (HDD), gather and review the events in the disk controller event log. Classify and analyze all failure events reported by the disk controller based on the server SAS topology.

To classify a MegaRAID disk controller event:

  • Gather and parse the MegaRAID disk controller event logs either by running the automated sundiag utility or manually using the MegaCLI or StorCLI commands.

    • For Oracle Exadata Database Machine database or storage cell servers, run the sundiag utility.

    • For the Sun Server X3-2, use the MegaCLI command.

For example, manually gather and parse the controller event log by using the MegaCLI command. At the root prompt, type:

root# ./MegaCli64 adpeventlog getevents –f event.log aall
Success in AdpEventLogExit
Code: 0x00

Note -  Use the existing name of the event log as the name for the disk controller event log. This produces a MegaRAID controller event log with the given file name event.log.

The following SCSI sense key errors found in the event log in SAS data path failures indicate a SAS data path fault:


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 controller, SAS cables, SAS expander, or disk backplane might be causing the interruption to the communication in the path between the RAID controller and the disks.

Oracle Service personnel can find more information about the diagnosis and triage of hard disk and SAS data path failures on x86 servers at the My Oracle Support web site: https://support.oracle.com. Refer to the Knowledge Article Doc ID 2161195.1. If there are multiple, simultaneous disk problems on an Exadata server, Oracle Service personnel can refer to Knowledge Article Doc ID 1370640.1.