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-1605188.1
Update Date:2017-05-18
Keywords:

Solution Type  Problem Resolution Sure

Solution  1605188.1 :   SL150 - Fails to Initialize on Start Up, Fault Code: 9104 Robot Initialization Error  


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




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-8072338951>

Applies to:

StorageTek SL150 Modular Tape Library - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Library fails to initialize. Errors point to a defective robot assembly. After replacing robotic assembly, the library still fails to initialize.

Symptoms

Library fails to initialize.  Errors point to a defective robot assembly. After replacing robotic assembly, the library still fails to initialize.

When SL150 library initializes, an error message appears.

• Fault Code: 9104 Robot Initialization Error
• Suspect Components: Robot
The robot is replace multiple times with no success or the problem returns soon after the part is replaced.

After gathering a log snapshot,  A review of the log_health shows:

----> Library Start-up Detected <----  FW Version:0201 (1.34.00)
O,0001,2013-11-21T18:32:33.747,9104,ROBOT_REACH_MOVE_ERROR,1,Robot,,,,,,,,,Check for unseated tape. Inspect/replace robot

The log_error messages show:

robot, /usr/local/bin/Ifm,  error, 0000, 5082, "Director - initResponse() srv_reach_sweep: Grip get ready state at start = 1, grip ready state after sweep = 1; srv_reach_sweep: saw grip state not changed after reach sweep; srv_reach_sweep: Performing retry on reach initialization.; srv_reach_sweep: Grip get ready state at start"
            ifm,                 ,  error, 0100, 5082, "IfmInitThread:Failure to Initialize...reason==An attempt to put the grip in 'ready to get' or 'ready to put' state failed - GOING INOP"



Changes

 The robotics are replaced multiple times.

Cause

Robotic module failure.
 
Suspect defective from stock parts, due to sensor breaking away from the circuit card within the hand assembly.  Several DOA's reported.

See photo's attached to this Knowledge Entry.

Solution

Review photos attached to this KB.

Note if sensor is lost, loose or otherwise damaged.

Replace bot with a good spare.
 

References

<NOTE:1474118.1> - SL150 - How to Generate and Retrieve a Service Bundle (Health / Error Log) From the StorageTek SL150 Modular Tape Library

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