Sun StorageTek SL500 Modular Library System
 

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

In this Document

Symptoms

Changes

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Customers don't work on the SL500 or have ability to view logs
Created from <SR 3-15098910061>

Applies to:

Symptoms

SL500 library is down, even after an attempt to reboot.

From log_warning

2017-06-10T18:44:52.187, 0.0.9.0.2, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 1. Address for this retry (LMRC) 0,2,2,9"
2017-06-10T18:44:57.574, 0.0.0.0.0, 000, servo, , warn, 0000, 5014, "Asynchronous event for wrist"
2017-06-10T18:45:08.968, 0.0.9.0.2, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 2. Address for this retry (LMRC) 0,2,2,9"
2017-06-10T18:45:12.817, 0.0.0.0.0, 000, servo, , warn, 0000, 5014, "Asynchronous event for wrist"
2017-06-10T18:45:24.397, 0.0.9.0.2, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 3. Address for this retry (LMRC) 0,2,2,9"
2017-06-10T18:45:29.116, 0.0.9.0.2, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 4. Address for this retry (LMRC) 0,2,2,9"
2017-06-10T18:45:33.098, 0.0.9.0.2, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 5. Address for this retry (LMRC) 0,2,2,9"
2017-06-10T18:45:43.265, 0.0.4.0.3, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 6. Address for this retry (LMRC) 0,2,3,4"
2017-06-10T18:45:45.866, 0.0.0.0.0, 000, servo, , warn, 0000, 5014, "Asynchronous event for wrist"
2017-06-10T18:45:55.520, 0.0.4.0.3, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 7. Address for this retry (LMRC) 0,2,3,4"
2017-06-10T18:46:00.037, 0.0.0.0.0, 000, servo, , warn, 0000, 5014, "Asynchronous event for wrist"
2017-06-10T18:46:09.665, 0.0.4.0.3, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 8. Address for this retry (LMRC) 0,2,3,4"
2017-06-10T18:46:13.836, 0.0.0.0.0, 000, servo, , warn, 0000, 5014, "Asynchronous event for wrist"
2017-06-10T18:46:23.660, 0.0.4.0.3, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 9. Address for this retry (LMRC) 0,2,3,4"
2017-06-10T18:46:27.843, 0.0.0.0.0, 000, servo, , warn, 0000, 5014, "Asynchronous event for wrist"
2017-06-10T18:46:37.712, 0.0.4.0.3, 000, robot-cmo, , warn, 0000, 0000, "Performed put retry. Put retry total = 10. Address for this retry (LMRC) 0,2,3,4"
2017-06-10T18:46:42.184, 0.0.0.0.0, 000, servo, , warn, 0000, 5014, "Asynchronous event for wrist"
2017-06-10T18:46:53.192, 0.0.0.0.0, 3202, ifm, , warn, 0000, 3305, "IFM drive event and the Library state is unknown."
2017-06-10T18:46:53.291, 0.0.0.0.0, 3202, ifm, , warn, 0000, 3305, "IFM drive event and the Library state is unknown."

From log_error

2017-06-10T18:45:37.321, 0.0.9.0.2, 510, robot, /usr/local/bin/Ifm, error, 0000, 5014, "Director - putResponse() servo mech reach event 5014 at 1949 tachs, 1794 mils"
2017-06-10T18:46:51.959, 0.0.4.0.3, 510, robot, /usr/local/bin/Ifm, error, 0000, 5069, "Director - putResponse() servo mech reach event 5069 at 2118 tachs, 1949 mils"
2017-06-10T18:46:52.045, 0.0.0.0.0, 3202, ifm, , error, 3000, 3313, "(request id = HOST/0x1025da68) IfmMove::doPut(): move back to source from (LMRC) 0,2,2,9 failed, going inop"
2017-06-10T18:46:52.532, 0.0.0.0.0, 3202, ifm, , error, 3000, 3322, "(request id = HOST/0x1025da68) IfmMove::doPut() to (LMRC) 0,2,2,9 : cartridge in hand, going inop"
2017-06-10T18:46:52.575, 0.0.0.0.0, 3202, ifm, , error, 3000, 3322, "(request id = HOST/0x1025da68) IfmMove::commonMoveCommand(): PUT request of tape 020153L4 from (LMRC) 0,2,3,4 to (LMRC) 0,2,2,9 failed:"

Changes

Cause

Tape was stuck in robot hand due to the cartridge being dropped previously.  This dislodged the leader and caused expansion of the cartridge case.  
The cartridge case being expanded results in either the tape not being able to be put in a drive or cell, or results in the tape getting stuck in the robot hand.
 

Solution

Dispatch an FE to inspect the robot to verify a tape is stuck and then remove the tape.
 

References

This solution has no attachment