![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 2167242.1 : FS System: FS1-2 May Record DWORD Errors on a Faulty SAS Link.
In this Document
Oracle Confidential PARTNER - Available to partners (SUN). Applies to:Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform. SymptomsSerial Attached SCSI (SAS) link errors are logged by a Controller. These are observed following the scanlog6 processing of the system log bundle. Link error example: dl_pmcIombRcvSasHwEventProcess PSG_PI PSG_PI_IC "CTRL[0] Port[2] PHY[10] SAS HW event=0x12"
event=0x12 indicates that the error is of type PDG_DL_PM8018_HW_EVENT_PHY_ERR_INVALID_DWORD which is an error decoding the DWORD
Multiple entries may also be recorded in a single day, which would justify further investigation. Example command: grep "SAS HW event" output-1459726141816915402-1460002299735613382-0.txt | grep "2016-04-07T04:10" | wc -l
CauseThe cause is a faulted or 'marginal' component on the SAS link. The link remains online but DWORD (line encoding) errors are recorded by the SAS HBA port. SolutionIf there are multiple entries of this event type identified on the system, SA link components will require replacement. The suggested order would be:
The CTRL and Port details will identify the appropriate SAS HBA port locations. Reference the topology output in conjunction with this document: FS System: How to Read and Interpret the FS1-2 CLI Topology Command (Doc ID 1970990.1) In the example "dl_pmcIombRcvSasHwEventProcess PSG_PI PSG_PI_IC "CTRL[0] Port[2] PHY[10] SAS HW event=0x12" this translates to HBA 0, Port 2 which is a Controller<>Controller SAS link.
References<BUG:23072999> - ASSIST TSC: BS PANIC DUE TO TIMEOUTAttachments This solution has no attachment |
||||||||||||||||||
|