First Actions to be Performed On Service Call with DDD Drives

First Actions to be Performed On Service Call with DDD Drives

Pull RAID Administration Log created by RAID Administration Program or Netfinity Manager. RAID Administration Program can be obtained from the Configuration Diskette which contains the device drivers under the specific operating system subdirectory. The diskette is available on the IBM website http://www.us.pc.ibm.com/files.html . Search on 'RAID'.
From reading the RAID Administration Log or Netfinity Manager log, determine whether a HSP drive was present in the system or not. The log will indicate that a drive in a specific bay went DDD. Then, if hot spare was present, it will indicate that a drive in a specific bay auto-replaced the DDD drive bay.
View the Drive Information under Options in RAID Administration Program or under Netfinity RAID Manager to determine if any errors were recorded against DDD drive.

NOTE: Do not reboot the system because these error counters initialize to zero when the system is rebooted.

•  Hard Events - The number of SCSI I/O processor errors that occurred on the  drive since the Device Error Table was last cleared. It also  indicates if the drive exceeded Predictive Failure Analysis (PEA)  threshold.
•  Action:  Contact your support representative for further problem  determination.

•  Soft Events - The number of SCSI Check Condition status messages returned  from the Drive (except Unit Attention) since the Device Error  Table was last cleared.
•  Action: 
   1. If HSP is present, follow procedures in the section:
    Recovery Procedures when HSP is Present at Time of Failure
   2. If HSP is not present, follow procedures in the section:
    Recovery Procedures When HSP is Not Present at Time of Failure

•  Miscellaneous Events - The number of other errors (such as selection timeout,  unexpected bus free, or SCSI phase error) that occur on the  drive since the Device Error Table was last cleared.
•  Action:  Ensure cabling and connectors are seated properly. If backplane,  ensure backplane is not bowed causing poor drive connection. If  there are no problems with cable, backplane, etc., determine  whether HSP drive is present or not and follow appropriate  Recovery Procedures listed below but do not software replace the  drive. Physically replace the drive.

•  Parity Events - The number of parity errors that occurred on the SCSI bus since  the Device Error Table was last cleared.
•  Action:  Check to ensure SCSI bus is properly Terminated with one and  only one Active Terminator placed at the end of the SCSI Chain. If  a backplane is the last device on the chain, then the backplane  terminates the bus as long as no cable is plugged into the  daisy-chained connector on the backplane.

•  PFA Events - Predictive Failure Analysis
•  Action:  Determine whcthcr HSP drive is present or not and follow  appropriate Recovery Procedures listed below, but do not software  replace the drive. Physically replace the drive.

Please see the LEGAL  -  Trademark notice.
Feel free - send a   for any BUG on this page found - Thank you.