Sun StorageTek SL3000 Modular Library System
 
Sun StorageTek SL8500 Modular Library System
 

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

In this Document

Purpose

Troubleshooting Steps

References

Applies to:

Purpose

The hand assembly has a reach mechanism that is responsible for fetching or putting a cartridge from/to a designated location in the library.  A "servo mech reach" event occurs when the reach mechanism is not able to fully extend or retract during a fetch or put operation.

Possible causes of   "servo mech reach" errors are:
1.  defective motor
2.  power issues
3.  location full/obstructed issues
     example:    broken drive bezel
                      target slot already has a cartridge in it
                      tape physically stuck in the gripper
                      defective tape array

Examples of "servo mech reach" error messages:
-  Warning from device, cmo_user_put: Retry Performed 5611; servo mech reach event 5010 address = Cell(1,3,-18,2,8)

-  Error from device Code: 510 - Robot says location full/obstructed, servo mech reach event 5069 address = Drive(1,3,-2,1,3)

- Warning from device, cmo_user_put: Retry Performed 5611; servo mech reach event 5069 address = Drive(1,3,-1,1,3)

- Warning from device, cmo_user_put: hand empty, forcing successful flag=true, cmo_status=4, code=5069, opState=0; cmo_user_put: Retry Performed 5611; servo mech reach event 5069 address = Drive(1,3,2,1,3)


The result codes on the error messages above are defined below:
Error 5010 means "An excessive position error was detected during motion".
Error 5069 means "The max or min current was requested an excessive amount of times during a stall move with a minimum position not reached"

Troubleshooting Steps

1.  Verify if the "servo mech reach" error is caused by an obstruction on the target location.  There should
      be error messages similar to the following:
       -  Error from device Code: 510 - Robot says location full/obstructed, servo mech reach event 5069
          address = Drive(1,3,-2,1,3)
        - Error from device Code: 510 - Robot says location full/obstructed, cmo_user_put: Retry Performed
          5611; servo mech reach event 5010 address = Cell(5,1,-12,2,10)
        - Error from device Code: 510 - Robot says location full/obstructed, cmo_user_put: Retry Performed
          5611; servo mech reach event 5010 address = PTP(5,1,6,1,2)
        - Error from device Code: 510 - Robot says location full/obstructed, cmo_user_put: Retry Performed
          5611; servo mech reach event 5010 address = SwapCell(5,1,-6,1,6)

     Determine if the obstruction is caused by a tape stuck in the target location.  Check the target location
     from the SL Console.  If it is empty,  the obstruction may be caused by a tape stuck in the hand or if the
     target location is a drive, there may be a drive bezel problem.

     If there is already a tape in the target location during a robot put operation,  it is possible that the
     library management software (ACSLS or HSC) has an issue with the status of the target location (i.e.,
     it thinks the target is "empty" but actually it is "full".   Audit the location using the SLConsole to verify.
     Also Audit the location from ACSLS or HSC.

     If the obstruction is referring to a PTP or elevator cell location, an FE will have to be dispatched onsite
     to clear the error and run diagnostic tests on the PTP (or elevator) and the robot.

     If the obstruction is referring to a swap cell (or drop-off cell),  this implies that the robot is in the process
     of initializing when the error occurred.  Dispatch an FE to remove the tape in the robot hand and in the
     drop-off cell.  Run diagnostic tests on the robot.  Do not enter the tapes back into the library until ACSLS
     or HSC has removed the tape volumes in its database. 

2.  Verify if the "servo mech reach" error is caused by a defective tape array or a defective tape.  There
     should be error messages similar to the following:   
     - error 3955 Error from device Code: 504 - Robot says cartridge stuck in location
     - cmo_eval_op_state, Reach Not Safe: SENSORS; servo mech reach event 5069
   
     Check out this document:
    <Document: 1390586.1> - Robots went offline after "Robot reach not safe" errors during put operations
    <Document: 1392136.1> - Robot operation failed Code: 504 - Robot says cartridge stuck in location Data

3.  In all other cases, when the robot fails to initialize successfully, send a field engineer onsite to replace the
     robot.

References

This solution has no attachment