SL8500 - Library Failed to Reboot After Code Upgrade or Has All Robots and a Elevator Offline. HBT is in a Standby State After Rebooting

Asset ID:	1-72-2239443.1
Update Date:	2018-04-10
Keywords:

Solution Type Problem Resolution Sure

Solution 2239443.1 : SL8500 - Library Failed to Reboot After Code Upgrade or Has All Robots and a Elevator Offline. HBT is in a Standby State After Rebooting

Applies to:

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

Symptoms

All robots go into a offline state with other components such as elevator or caps also going offline. It has also been observed that the HBT card will come up in a Standby state.

Library fails to complete initialization after microcode upgrade.

Changes

It has also been reported that firmware upgrades can also trigger HBC or HBK card issues ie upgrading firmware from version 8.05 to 8.51. It has been seen that coming from lower levels such as 4.73 has triggered this issue.

Cause

The underlying cause is file system corruption on the HBC and or HBK card. Below are examples of what you might see from the linux text output from the HBC card..

Here is 1 example of the HBK getting a I/O error. You will see this at the very end of the linux output.

root: /etc/init.d/alias_ilc: /mnt/idcard/etc/sysconfig/network-scripts/ifcfg-eth3 Doesn't exist

ls: /mnt/idcard/configuration/AccessStore: Input/output error
ls: /mnt/idcard/configuration/StkRobots.txt: Input/output error
ls: /mnt/idcard/configuration/CapacityConfiguration.txt: Input/output error

Here is 1 example of the HBK getting a Failed to mount error. You will see this at the very end of the linux output.

root: /etc/rc.d/rc3.d/S12hbc_master: mounts
mount: Mounting /dev/idcardfs on /mnt/idcard failed: No such device
root: FAILED to mount /mnt/idcard
root: Secure key not detected
/etc/init.d/secure_key_init.sh: echo: Argument list too long

This is a example of the HBK file corruption

root: /etc/rc.d/rc3.d/S12hbc_master: mounts
root: Secure key mounted successfully

/etc/init.d/secure_key_init.sh: echo: Argument list too long

Normally we should see a login prompt when the HBK is successfully mounted.

Here is another indication of a potential HBK issue.. When trying to do a network config clear command. Because the HBC wants to go out and clear the network information from the HBK you'll see the following when trying initiate this command.

HBC CLI Command

Solution

Order a replacement HBC or HBK card depending on which scenario is observe after analyzing the Linux text output from the HBC.

Attachments

This solution has no attachment