cancel
Showing results for 
Search instead for 
Did you mean: 

Drive Issue

H_Sharma
Level 6

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

 

1 ACCEPTED SOLUTION

Accepted Solutions

mph999
Level 6
Employee Accredited

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 ?

 

View solution in original post

5 REPLIES 5

mph999
Level 6
Employee Accredited

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 ?

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
You are still having problems with OS losing connection to devices. Have you checked Windows Event logs for device-related errors? As per advice in your other posts, you need to check physical connections and config. Even drivers, firmware, settings, etc.

H_Sharma
Level 6

Found Robot has some issue. Needs to be replaced.

mph999
Level 6
Employee Accredited

Yes, I think there is more than one issue, the one I explained above, and this ;

TLD(0) going to DOWN state, status: Unable to open robotic path

... when it completely loses the ability to contact the library.

NOTE.  When you replace the library, make sure it (the new one ) is configured to display the same number  of characters in the barcode as the old one.

EG.

If robtest > s s    command shows

AA1234L5  (that is 8 characters) make sure the new library is configured the same, and NOT for example to display only 6 charaters of the barcode, else a whole new load of fun and games will start.

H_Sharma
Level 6

Thanks Martin for solution...

Finally...One drive and Robot are down. Need to replace.

Marianny you are right we are in the middle of crisis... Everything is failing...