SL150 - Fails to Initialize on Start Up, Fault Code: 9104 Robot Initialization Error
(Doc ID 1605188.1)
Last updated on DECEMBER 28, 2021
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
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |