StorageTek SL150 Modular Tape Library
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL150 Library
 

In this Document

Symptoms

Cause

Solution

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: The log entries are Oracle Internal only

Applies to:

Symptoms

SL150 - Incorrect Fault Code 9091 Shown for a Track Error On the Robot.

This will cause the SL150 to go inoperative due to the following error messages:

2009-05-18T05:11:17.534, 0.0.0.0.0, 000, sensor-manager, , error, 0000, 8035, "getCheckProductIDSN: Base KLM module location reading 6, expecting 1."
2009-05-18T05:11:17.539, 0.0.0.0.0, 000, sensor-manager, , error, 0000, 8035, "SensorMgr - setting library InOp due to Product ID issues!"

These are as a result of a track error on the robot.

Cause

There is a bug in the SL150 code where a track error gets mapped to a 9091 fault code which will call out the incorrect part to replace.

The 9091 fault code calls out the Base Chassis CRU to be replaced but in this specific scenario it is actually the robot that had an obstruction or is bad.

define LIBMD_BASE_KLM_MODULE_MISMATCH_FAULT_CODE 9091 //_supported_
faultCode=9091
faultString="MOD_MB_BASE_MODULE_LOCATION_INCORRECT"
helpString="Check for obstruction affecting robot vertical range. Replace base module chassis or have it's midplane replaced."
cru1="Chassis"
cru1Priority=1

As reported in the Health File in the Service Bundle:

0045 - MOD_MB_BASE_MODULE_LOCATION_INCORRECT - Fault Code:9091

Probable Failed Components
1. Module 1 Chassis

Actions to Take
Replace base module chassis or have it's midplane replaced.

Solution

If the 9091 is received and the above entries are found in the error log at the time of the 9091 then you should troubleshoot the Robot CRU and not the Base Chassis CRU.

This was fixed in 2.60 code.  In 2.60 and higher code the 9091 will state that you need to look for an obstruction that is causing the Z range to fail.

Upgrade firmware to 2.60 or above.

This solution has no attachment