SL3000 - Robotic Error During Drive Cleaning

Asset ID:	1-72-2253985.1
Update Date:	2018-05-24
Keywords:

Solution Type Problem Resolution Sure

Solution 2253985.1 : SL3000 - Robotic Error During Drive Cleaning

Applies to:

Sun StorageTek SL3000 Modular Library System - Version All Versions and later
Information in this document applies to any platform.

Symptoms

Our observation is that the robotic arm is not aligning with the drive(s) and it is damaging the tapes. The service light is also engaged on the library. Not able to conduct any backups and have a number of drives down because of this.

2017-04-03 12:22:48 IfmInitThread:Failure to Initialize...reason==Robot initialization failed - GOING INOP
2017-04-03 11:43:50 (SA 525) The SL500 logs are showing that the library failed to initialize. You will need to look at the SL500 logs to see what caused the library to fail the initialization. This could be a bad robot, a broken target bezel on a drive, or possibly some sort of obstruction inside of the library. The logs should help determine which of those has caused the initialization to fail.

2017-04-03T11:42:08.275 warn 0.0.0.0.0 5051 "Asynchronous event for reach: Door Opened"
2017-04-03T11:43:50.626 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for track"
2017-04-03T11:43:50.706 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for wrist"
2017-04-03T11:43:50.787 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for reach"
2017-04-03T11:43:50.869 error 0.0.0.1.0 0000 "Director - initResponse() Initialize: failed general init routine.; End of Text" /usr/local/bin/Ifm
2017-04-03T11:43:50.998 warn 0.0.0.0.0 1104 "LibifLibrary::LibifLibrary() 0x1026b950 - attempt to create a duplicate LibifLibrary"
2017-04-03T11:43:50.999 error 0.0.0.0.0 3717 "IfmInitThread:Failure to Initialize...reason==Robot initialization failed - GOING INOP"
2017-04-03T11:43:52.379 error 0.0.0.0.0 1103 "HostInit::discoverStkDevicePorts() 0x1025b838 - no host interfaces exist"
2017-04-03T11:43:52.397 error 0.0.0.0.0 1103 "HostInit::discoverLunPartitionPorts() 0x1025b838 - STK Surrogate SCSI partition support is TBD"
2017-04-03T11:49:06.409 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for track"
2017-04-03T11:49:06.489 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for wrist"
2017-04-03T11:49:06.577 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for reach"
2017-04-03T11:49:06.668 error 0.0.0.1.0 0000 "Director - initResponse() Initialize: failed general init routine.; End of Text" /usr/local/bin/Ifm
2017-04-03T11:49:06.848 warn 0.0.0.0.0 1104 "LibifLibrary::LibifLibrary() 0x1026c010 - attempt to create a duplicate LibifLibrary"
2017-04-03T11:49:06.889 error 0.0.0.0.0 3717 "IfmInitThread:Failure to Initialize...reason==Robot initialization failed - GOING INOP"
2017-04-03T11:49:08.409 error 0.0.0.0.0 1103 "HostInit::discoverStkDevicePorts() 0x1025b838 - no host interfaces exist"
2017-04-03T11:49:08.428 error 0.0.0.0.0 1103 "HostInit::discoverLunPartitionPorts() 0x1025b838 - STK Surrogate SCSI partition support is TBD"
2017-04-03T12:09:49.771 error 0.0.0.1.0 0000 "Robot Home sensor failure. Sensor on after z-sweep."
2017-04-03T12:09:50.367 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for z"
2017-04-03T12:09:50.486 warn 0.0.0.0.0 5037 "Asynchronous shutdown request for reach"
2017-04-03T12:09:50.502 error 0.0.0.1.0 0000 "Director - initResponse() Initialize: Z failed from park position.; End of Text" /usr/local/bin/Ifm
2017-04-03T12:09:50.597 error 0.0.0.0.0 3717 "IfmInitThread:Failure to Initialize...reason==Robot initialization failed - GOING INOP"
2017-04-03T12:09:50.716 warn 0.0.0.0.0 3305 "IFM drive event and the Library state is unknown."
2017-04-03T12:09:50.755 warn 0.0.0.0.0 3305 "IFM drive event and the Library state is unknown."
2017-04-03T12:09:50.786 warn 0.0.0.0.0 3305 "IFM drive event and the Library state is unknown."
2017-04-03T12:09:50.864 warn 0.0.0.0.0 3305 "IFM drive event and the Library state is unknown."
2017-04-03T12:09:50.904 warn 0.0.0.0.0 3305 "IFM drive event and the Library state is unknown."
2017-04-03T12:17:44.672 warn 0.0.0.0.0 0000 "sys_reboot(): system reboot invoked. Calling reboot()..."
2017-04-03T12:20:13.368 error 0.0.0.1.0 0000 "Robot Home sensor failure. Sensor on after z-sweep.

Cause

Robot Home sensor failure. Sensor on after z-sweep.

Solution

Before replacing the robot, check that there is nothing interfering with the movement of the robot up and down. It could be a stuck cartridge in the hand or in a slot.
Appears to be a sensor error on the robot.

Recommend the robot be replaced.

Attachments

This solution has no attachment