Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1917513.1
Update Date:2017-09-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  1917513.1 :   SL150 - Robot is Hitting the Tape Cartridges, Fault Code:9102  


Related Items
  • StorageTek SL150 Modular Tape Library
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL150 Library
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-9463689541>

Applies to:

StorageTek SL150 Modular Tape Library - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

The problem occurred over the weekend as a hardware issue and none of the backups get completed and customer falls behind. It also seems to be scratching the labels on the tapes making them unreadable. I have taken a picture of the damage it did to the tapes. I was able to remove two of the scratched tapes as they were scratch media. However one of the tapes has data on it and now I'm not sure if I can use that tape or if I need to get a custom label made so I don't lose any data.

Symptoms

Since replacing the robot about a month ago we are still having intermittent issues with the robot.

2014-08-13T00:14:03.016,      0.0.1.0.2, 519,            robot, /usr/local/bin/Ifm,  error, 0000, 5093, "Director - putResponse() Slack Detected, Marking Mech 1 non-operational; srv_mech_move:  failed. mcuIfStatus = 1, mechStatus = 12; End of Text"

Cause

According to the logs the robot is not able to move properly, there is an obstruction in the line of movement that is not allowing the free movement of the robot.  The "slack" reported by the robot is the clue that shows us that it has obstructions to move.

 

Solution

- Check for any obstructions in the library that are causing the robot to not be able to move down.

- Check for tapes sticking too far out of the magazines.

- Check that the base and expansion modules are fully seated and aligned.

- Check for any cables that might be in the path of the robot.  If nothing is found then try to park the robot by powering down via the Web GUI and checking the "Park Robot" option. 

 -If that doesn't work then manually park the robot via the procedure documented in the Knowledge doc:
     SL150 - How to Remove/Replace the Robot CRU in a StorageTek SL150 Modular Tape Library:ATR:1473774.1:0 (Doc ID 1473774.1)
                 How to Park the Robot Manually:
                 1. Remove the top tape drive from the base module.
                 2. Locate the bull wheel gear above the top drive slot.
                 3. Place your finger in an indent on the body of the bull wheel gear.
                 4. Turn the gear clockwise to raise the robot.

        Note: Assume that the 12 o’clock position is toward the front control panel.

                 5. Hold the bull wheel gear with the robot fully raised until the robot is locked.
                 6. Reposition the robot lock (loosen the thumb screw, remove the mechanism, rotate the mechanism 180 degrees, insert the mechanism, and tighten the thumb screw).

- Pull the robot out and check it for any loose cables and also for any slack in the suspension cables that the robot assembly hangs from and also check to see if the suspension cables have jumped off of the pullys.  If they have and they cannot easily be fixed then a new robot should be ordered.

- If nothing was found wrong when the robot was pulled out, put the robot back in and unlock it. Pull all of the drives but the bridge drive so you can watch the library initialize.  Power up the library and watch it initialize through the empty drive bays.

- Watch specifically to see if the robot catches on anything during the initialization.  If the initialization completes OK then run the "Full Self Test" with the diagnostic tape.


Final Fix:
The problem was caused by the expansion tray was not latched correctly with the upper main unit, causing the magazine to be crooked. By reinserting the expansion module, this fixed the mechanical problem.

The wire on the original robot was too loose on the right side, this is why the robot needed to be replaced.  The robot was damaged by hitting the bottom magazines.
 

References

<NOTE:1473774.1> - SL150 - How to Remove/Replace the Robot CRU in a StorageTek SL150 Modular Tape Library:ATR:1473774.1:0
<NOTE:1327031.1> - LTO5 - Part Number For Diagnostic Label Sheets With LTO5 Labels
<NOTE:1530198.1> - SL150 - How to Run a Library Diagnostic Self-test

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback