Drive Issue
Hello Experts,
What are these below errors? We have these error in our master server's event logs. Expereincing multiple 98 error codes.
1:- TLD(0) key = 0x2, asc = 0x4, ascq = 0x3, LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED
2:-TLD(0) drive read_element_status error
3:-TLD(0) going to DOWN state, status: Unable to sense robotic device
4:-Request for media ID RTY879 is being rejected because mount requests are disabled (reason = robotic daemon going to DOWN state)
5:-TLD(0) [4204] timed out after waiting 855 seconds for ready, drive 8
6:-TLD(0) mode_sense ioctl() failed: The operation completed successfully.
7:-Unable to send scsi command, ScsiStatus = 0x2
8:-TLD(0) [14832] Could not get serial number for robot \\.\Scsi1: (SCSI coordinates {1,0,2,1})
9:-TLD(0) going to DOWN state, status: Unable to open robotic path
10:-Invalid magic number from client tnmmnetmed02p
11:-TLD(0) unavailable: initialization failed: Unable to open robotic path
The library is sending this error
TLD(0) key = 0x2, asc = 0x4, ascq = 0x3, LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED
So it's not responding correctly, which will cause the other errors you see.
This a bit odd though
TLD(0) unavailable: initialization failed: Unable to open robotic path
As it must have contacted the library to get the asc/ascq error back.
First, I'd power cycle the library, then do stopltid and then ltid -v
(commands are in /usr/openv/volmgr/bin)
... and then see if robtest works
1. Does robtest connect
2. If it does, what happens when you type mode
You could also try
/usr/openv/volmgr/bin/scsi_command -r <path to robot> (get the path from tpconfig -d)
Does that respond ?