cancel
Showing results for 
Search instead for 
Did you mean: 

Library Issue

SUMAKSHI
Level 3
Hello Friends,
 
We are having issues with the library and below is th error code for the same. Kindly suggest, what meight be an issue.
 
# ./tldtest -r /dev/sg/c3t0l0 -d1 /dev/rmt/0cbn -d2 /dev/rmt/1cbn -d3 /dev/rmt/2cbn -d4 /dev/rmt/3cbn
read_element_status failed, CHECK CONDITION
sense key = 0x2, asc = 0x5a, ascq = 0x1, UNKNOWN ERROR, SENSE_KEY: 0x02, ASC: 0x5A, ASCQ: 0x01
[ID 209712 daemon.error] Fatal open error on QUANTUMDLT7000-3 (device 2, /devices/pci@4,2000/scsi@1/sg@3,0:raw), errno = 19 (No such device), DOWN'ing it
 vmd[12780]: [ID 631293 daemon.notice] terminating - successful (0)
 ltid[529]: [ID 265732 daemon.warning] Sending shutdown to tldcd daemon...
 tldcd[642]: [ID 343350 daemon.notice] TERMINATION requested from koktsv51
 vmd[13972]: [ID 734361 daemon.notice] ready for connections on socket 2

Drv Type   Control  User      Label  RVSN    EVSN    Ready   Wr.Enbl.  ReqId
  0 dlt      AVR                -                     No       -        -
  1 dlt      AVR                -                     No       -        -
  2 dlt     DOWN                -                     No       -        -
  3 dlt      AVR                -                     No       -        -
3 REPLIES 3

Omar_Villa
Level 6
Employee
Based on the SCSI you show, it can be taked like this:
 
sense key = 0x2, asc = 0x5a, ascq = 0x1

2h

NOT READY
 
5A/00  DTLPWROM  BK    OPERATOR REQUEST OR STATE CHANGE INPUT
5A/01  DT  WROM  BK    OPERATOR MEDIUM REMOVAL REQUEST
5A/02  DT  WRO A BK    OPERATOR SELECTED WRITE PROTECT
5A/03  DT  WRO A BK    OPERATOR SELECTED WRITE PERMIT
So means that your Medium Removal is Not Ready, you should call Quantum or your library vendor support is a library issue is for sure.
 
hope this helps.
regards

zippy
Level 6
use your operating system tools or command to see if the drive is physically there and that the device files are the same as the netbackup output.
 
 
also it looks like you robot is not "online" AVR -- you need to see TLD.
 
bpps -a
 
MM Processes
------------
    root  2734  2673  0  Mar 17  ?         0:09 tldd -v
    root  2673     1  0  Mar 17  ?         0:49 /usr/openv/volmgr/bin/ltid
    root  2741  2673  0  Mar 17  ?        13:08 avrd -v
    root  2682     1  0  Mar 17  ?         2:22 vmd -v
    root  2746     1  0  Mar 17  ?         0:35 tldcd -v
 


Message Edited by James Dunn on 04-09-2008 12:33 PM

Stumpr2
Level 6
I would delete the configuration and rebuild it.
See what you have with sgscan/scan/ioscan whatever...
 and tpautoconf -t
 
the following indicates that the library has a fault
# ./tldtest -r /dev/sg/c3t0l0 -d1 /dev/rmt/0cbn -d2 /dev/rmt/1cbn -d3 /dev/rmt/2cbn -d4 /dev/rmt/3cbn
read_element_status failed, CHECK CONDITION