![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 2072338.1 : SL150 - CAP Eject Failure
In this Document
Applies to:StorageTek SL150 Modular Tape Library - Version All Versions and laterInformation in this document applies to any platform. Issue on a SL150 CAP. SymptomsCustomer ejects 13 tapes into extended mailslot. The robot fills the mailslots - no problem. Open CAP from Op Panel - Small CAP pops open - Large CAP is released to pull out. Customer gets all tapes out of the CAPS - pushes both CAPs back in at the same time. Library then thinks there are still tapes in the Small CAP and get the following User Activity event: Unlocking the Mailslot ExpansionOpening the MailslotMailslot failed to pop openLocking the Mailslot ExpansionERROR: Mailslot failed to pop open.
Error Log:
2015-09-22T09:19:14.212, 0.0.0.0.0, 535, robot, /usr/local/bin/Ifm, error, 0000, 1234, "Director - directorVerdeCapResp() directorVerdeCapRequ: CAP sensor not Opened after Open Operation; End of Text" 2015-09-22T09:42:19.643, 0.0.0.0.0, 535, robot, /usr/local/bin/Ifm, error, 0000, 1234, "Director - directorVerdeCapResp() directorVerdeCapRequ: CAP sensor not Opened after Open Operation; End of Text" 2015-09-22T09:54:26.619, 0.0.12.0.1, 505, robot, /usr/local/bin/Ifm, error, 0000, 5022, "Director - fetchResponse() srv_coord_fetch: no cart after fetch; End of T" 2015-09-22T09:54:26.630, 0.0.0.0.0, 3200, ifm, , error, 3000, 3312, "(request id = HOST/0x89ffd98) IfmMove::commonMoveCommand(): FETCH request of tape DA0722L5 from (Mailslot #) 1 failed:" 2015-09-22T09:58:33.890, 0.0.13.0.1, 505, robot, /usr/local/bin/Ifm, error, 0000, 5022, "Director - fetchResponse() srv_coord_fetch: no cart after fetch; End of T" 2015-09-22T09:58:33.899, 0.0.0.0.0, 3200, ifm, , error, 3000, 3312, "(request id = HOST/0x89ffd98) IfmMove::commonMoveCommand(): FETCH request of tape DA0743L5 from (Mailslot #) 2 failed:" 2015-09-22T10:03:11.342, 0.0.14.0.1, 505, robot, /usr/local/bin/Ifm, error, 0000, 5022, "Director - fetchResponse() srv_coord_fetch: no cart after fetch; End of T" 2015-09-22T10:03:11.358, 0.0.0.0.0, 3200, ifm, , error, 3000, 3312, "(request id = HOST/0x89ffd98) IfmMove::commonMoveCommand(): FETCH request of tape DA0874L5 from (Mailslot #) 3 failed:" 2015-09-22T10:09:12.625, 0.0.15.0.1, 505, robot, /usr/local/bin/Ifm, error, 0000, 5022, "Director - fetchResponse() srv_coord_fetch: no cart after fetch; End of T" 2015-09-22T10:09:12.636, 0.0.0.0.0, 3200, ifm, , error, 3000, 3312, "(request id = HOST/0x89ffd98) IfmMove::commonMoveCommand(): FETCH request of tape DA0876L5 from (Mailslot #) 4 failed:"
Warning Log: 2015-09-16T14:03:07.167, 0.0.0.0.0, 3200, ifm, , warn, 3018, 1234, "ifmOpenCap - Director failed, Robot OK but CAP did not Open" 2015-09-22T09:19:14.213, 0.0.0.0.0, 3200, ifm, , warn, 3018, 1234, "ifmOpenCap - Director failed, Robot OK but CAP did not Open" 2015-09-22T09:42:19.643, 0.0.0.0.0, 3200, ifm, , warn, 3018, 1234, "ifmOpenCap - Director failed, Robot OK but CAP did not Open" CauseDefective CAP Sensor. The thin metal flange not seating tight to the plastic sensor-flag tab. SolutionFound out that the CAP sensor (for the 4-slot CAP) is indeed on the Robot. With that information the plan was to pull the Robot and check for any loose connection to that sensor. There was no evident problem so the Robot was replaced. Pulled the 4-slot CAP out to inspect it and found the thin metal flange not seating tight to the plastic sensor-flag tab. No idea if this had anything to do with the intermittent problem of not seeing the CAP open but it was corrected anyway. This is a picture of the CAP sensor that is on the Robot - circled in red. This is a general picture of the CAP sensor-flag for perspective. The "GAP" picture below shows the thin metal flange not fitting tightly to the plastic sensor-flag tab. The "Fixed" picture below is after I unscrewed the metal plate (T20) and bent it together to fit tightly to the plastic tab and screwed it back on.
Attachments This solution has no attachment |
||||||||||||||||
|