Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1368699.1
Update Date:2012-06-28
Keywords:

Solution Type  Problem Resolution Sure

Solution  1368699.1 :   SL8500 - Drop Off Cells On Both Sides of Library Are Full, Preventing the Robots to Initialize  


Related Items
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
  •  




In this Document
Symptoms
Changes
Cause
Solution


Created from <SR 3-4754883812>

Applies to:

Sun StorageTek SL8500 Modular Library System - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

The STK Log AnalyTics (SPLAT) tool shows the following messages in the Library Summary and Library Condition reports:

1.  HBC logs report BOT failed to init due to tapes in drop off cells
2.  Robot initialization error - reinitialize - no operational robot to push with , robot=x,x,x,x,x
3.  Safety door path not clear-Robot in path of safety door: right, robot=x,x,x,x,x location=x,x,x,x,x


These messages are logged in the Error Warning Info Event log:

Error 5613 :
Robot initialization error - Data: 2011-10-17T13:46:15.152, 1.1.0.1.0, root, default, internal, 0, error, 1302, Failure from robot Code: 512 - Robot can not go operational, DIRECTOR End of Rail Init: Cartridge dropoff failed, cannot init, cmo_user_init_drop_off: Cannot dropoff Cartridge, Cell is FULL

Changes

One or more robots failed to initialize

Cause

Robot initialization requires the robot hand to be empty to allow the robot to verify its gripper, reach and scanner sensors. 

If there is a cartridge in the robot's hand, the cartridge has to be put away in the robot's drop-off cell.  If the robot's drop-off cell is already full or if the path to its drop-off cell is blocked,  the robot's initialization process will fail.  The robot will not be functional until the initialization process completes.

Solution

1. Remove tapes from the robot drop-off cells:
    a. Close the SSD on the left side.
    b. Remove any tapes from the drop off slot.
    c. Center the SSD.
    d. Initialize the left side robot.
    e. If there is also a problem with the right side robot, follow instructions 1 through 4 but referencing the right
        side and the right robot.
2. Reboot the failing robot(s).
3. If the robot initialization fails, replace the robot.

Note: 

If  the robot's drop-off cell is full, this is an indication that the robot has previously failed to initialize.  

Note: (Added 6-28-12)

Clarification on the drop off slot:

If there is a tape in the drop-off cell during bot initialization the initialization can fail. The handbot can use the drop-off cell during initialization and it must be empty/available.

There has been code problems in the past that unexpectedly left a tape in the drop-off slot under the right conditions and a subsequent full bot initialization can fail as a result. The library is architected to remove the tape from the drop-off cell after it completes initializes but if a bot fails with a tape in hand it must be able to put the cartridge in the drop cell first before it can complete initialization.

There is only one drop-off cell per side/bot and if the slot is full the bot cannot complete the put to the drop-off cell thus the initialization will fail and post an event, “device Code: 512 - Robot can not go operational & Cannot dropoff Cartridge, Cell is FULL”, noting the drop off cell is full.

Tapes left/abandoned in the drop-off cell is a signature of intermittent bot problems on a rail and should be investigated. Any site seeing this event in the log should not only remove the tape via the SSD as soon as possible but also investigate why the library is having intermittent bot resets.

To address the code problem of recovering the cartridge from the drop-off slot the library code should be upgraded to 6.07 or 7.70 but addressing the reasons for the intermittent bot resets which led to the original failed cartridge recovery also needs to be investigated and addressed.


Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback