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-1937288.1
Update Date:2017-09-13
Keywords:

Solution Type  Problem Resolution Sure

Solution  1937288.1 :   SL500 - Tape Library Goes to Inoperative State Due to Tape Drive Over-Ejecting tape (Fetch failed)  


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




In this Document
Symptoms
Changes
Cause
Solution


Created from <SR 3-9680658230>

Applies to:

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

Symptoms

 Keep getting the following error even after robot replaced twice. SL500 going Inop.

2014-09-08T14:38:08.199,      0.0.9.0.2, 506,            robot, /usr/local/bin/Ifm,  error, 0000, 5066, "Director - fetchResponse() servo mech reach event 5066 at 2551 tachs, 2348 mils"
2014-09-08T14:38:08.302,      0.0.0.0.0, 3202,              ifm,                 ,  error, 3000, 3312, "(request id = HOST/0x10254fc8) ***ERROR::IfmMove::doFetch(): WE ARE INOP"
2014-09-08T14:38:08.721,      0.0.0.0.0, 3202,              ifm,                 ,  error, 3000, 3312, "(request id = HOST/0x10254fc8) IfmMove::commonMoveCommand(): FETCH request of tape SUN077L4 from (LMRC) 0,2,2,9 failed:"

======================
Replaced robot Sept 11
======================

2014-09-16T07:43:48.729,      0.0.9.0.1, 509,            robot, /usr/local/bin/Ifm,  error, 0000, 5014, "Director - fetchResponse() servo mech wrist event 5014 at 11255 tachs, 7695 mils"
2014-09-16T07:43:48.767,      0.0.0.0.0, 3202,              ifm,                 ,  error, 3000, 3312, "(request id = HOST/0x10254fc8) ***ERROR::IfmMove::doFetch(): WE ARE INOP"
2014-09-16T07:43:48.921,      0.0.0.0.0, 3202,              ifm,                 ,  error, 3000, 3312, "(request id = HOST/0x10254fc8) IfmMove::commonMoveCommand(): FETCH request of tape SUN003L4 from (LMRC) 0,1,1,9 failed:"

======================
Replaced robot Sept 25
======================

2014-09-29T16:04:54.019,      0.0.9.0.1, 509,            robot, /usr/local/bin/Ifm,  error, 0000, 5014, "Director - fetchResponse() servo mech z event 5014 at 21821 tachs, 5050 mils"
2014-09-29T16:04:54.065,      0.0.0.0.0, 3202,              ifm,                 ,  error, 3000, 3312, "(request id = HOST/0x10254fc8) ***ERROR::IfmMove::doFetch(): WE ARE INOP"
2014-09-29T16:04:54.211,      0.0.0.0.0, 3202,              ifm,                 ,  error, 3000, 3312, "(request id = HOST/0x10254fc8) IfmMove::commonMoveCommand(): FETCH request of tape SUN042L4 from (LMRC) 0,1,1,9 failed:"

 

Changes

 No change

Cause

From Sept 8 to Sept 29, we got 3 event that the robot go
Inop after a fetch that involved drive 0,1,1,9.

3 different media was involved in the inop
SUN077L4,SUN003L4 and SUN042L4.

All above logs indicated error detected area is 0,1,1,9 and positioned
5050 mils = 12.827cm from the top.


You may decode the mils to cm using the following website.
http://www.convertunits.com/from/mils/to/cm
4782 mils is 12.146cm
5050 mils is 12.827cm

 

This problem was cause by a bad drive in 0,1,1,9. The cartridge in this tape drive was ejected to far out
from the tape drive and obstruct the robot from moving down.   (See attachment SL500-Inop.jpeg)

 SL500-Inop.jpeg

Note : The picture was taken after we move the tape drive from 0,1,1,9 to 0,2,2,9 to confirm the drive issue.

 

Solution

Replace drive in 0,1,1,9 solved the problem.
 


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