Users Guide

Table 35. Warning events (continued)
Event Code Message Text and Description Details and Solution
4163 Drive sled discovery timeout. Drive sled discovery timeout, status of Drive
sleds not available in time.
• Ensure that all modules are powered and
have the interconnect cable properly
attached.
• If this event is seen on multiple modules or
after ensuring all interconnect cables are
properly attached, ensure that the network
that the base module is connected to is not
experiencing broadcast storms or other
abnormal activity.
• Reboot or power cycle the system to
rediscover the modules.
4164 Inventory has been updated due to an
unexpected empty or full slot.
If a move fails due to an unexpected empty or
full slot, the slot is rescanned and the inventory
is corrected.
4165 Bottom magazine slots in the lowermost
unit are not accessible.
The installed accessor does not support access
to all 40 slots in the lowermost unit. The
bottom slots in the lowermost unit are not
accessible, so only 32 slots are available.
Install an accessor that supports access to all
40 slots in the lowermost unit.
4166 Drive self-test diagnostic failed. Reset Drive and run the test again. If still
failing, download drive dumps and contact
service.
4167 Drive primary port diagnostic failed.
• Check whether the wrap test connector is
correctly connected to the selected port.
• Reset drive and run test again.
• If the diagnostic still fails, download drive
dumps and contact service.
4168 Drive encryption key path diagnostic failed.
• Check the SKLM server conguration and
your network settings.
• If the diagnostic still fails, download the
library logs and contact service.
4173 Encryption Key Path diagnostics failed.
• Check the Key server conguration and your
network settings.
• If the diagnostic still fails, download the
library logs and contact service.
4174 KMIP CA certicate failure. Check whether you provided the correct CA
certicate or the CA certicate on the
encryption server was changed.
4175 Failed to create default logical library. Check that no errors occurred during the
startup and that at least one drive is present in
the library.
Chapter 5. Troubleshooting 101