Veritas-bu

[Veritas-bu] drives showing UNKNOWN

2006-03-23 10:31:27
Subject: [Veritas-bu] drives showing UNKNOWN
From: andrew.x.smith AT jpmchase DOT com (andrew.x.smith AT jpmchase DOT com)
Date: Thu, 23 Mar 2006 15:31:27 +0000
This is a multipart message in MIME format.
--=_alternative 005546A98025713A_=
Content-Type: text/plain; charset="us-ascii"

The mt status showing no tape can mean the tape is ejected, but still in 
the drive - have u tried moving the UNKNOWN tape from the drive using 
robtest? m d3 s?? ? I suspect that will work (and the library just wasnt 
able to read the barcode for these tapes). If it doesnt then you probably 
have a hardware fault.





Dave Markham <dave.markham AT fjserv DOT net>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
23/03/2006 15:14
Please respond to dave.markham

 
        To:     "veritas-bu AT mailman.eng.auburn DOT edu" <veritas-bu AT 
mailman.eng.auburn DOT edu>
        cc: 
        Subject:        [Veritas-bu] drives showing UNKNOWN


Netbackup 5.0 mp5s2 on solaris 8 connected to L1000 with 4 DLT7000
drives in.

Has anyone seen it where robtest shows drive with barcode UNKNOWN, yet
there are no tapes in the drive?

Invoking robotic test utility:
/usr/openv/volmgr/bin/tldtest -r /dev/sg/c3t0l0 -d1 /dev/rmt/0cbn -d2
/dev/rmt/1cbn -d3 /dev/rmt/2cbn -d4 /dev/rmt/3cbn

Opening /dev/sg/c3t0l0
MODE_SENSE complete
Enter tld commands (? returns help information)
s d
drive 1 (addr 128) access = 1 Contains Cartridge = no
SCSI ID from drive 1 is 2
drive 2 (addr 129) access = 1 Contains Cartridge = no
SCSI ID from drive 2 is 3
drive 3 (addr 130) access = 1 Contains Cartridge = yes
Barcode = UNKNOWN
SCSI ID from drive 3 is 4
drive 4 (addr 131) access = 1 Contains Cartridge = yes
Barcode = UNKNOWN
SCSI ID from drive 4 is 5
READ_ELEMENT_STATUS complete


The drives keep going down if i up them and a job tries to use them.

I currently have them in a down state. The drives are flashing, but the
akibia support after not responding for ages are trying to say its a
netbackup problem as mt -f /dev/rmt/2cbn status shows there is no tape
loaded. ( which it wouldnt because there isnt one )

# for d in 0 1 2 3; do mt -f /dev/rmt/$d'cbn' status; done
/dev/rmt/0cbn: no tape loaded or drive offline
/dev/rmt/1cbn: no tape loaded or drive offline
/dev/rmt/2cbn: no tape loaded or drive offline
/dev/rmt/3cbn: no tape loaded or drive offline


I am thinking the drives are goosed and robtest cannot talk to them to
get a clear picture. Is this on the right track?

Anyone any ideas?


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



--=_alternative 005546A98025713A_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="sans-serif">The mt status showing no tape can mean the 
tape is ejected, but still in the drive - have u tried moving the UNKNOWN tape 
from the drive using robtest? m d3 s?? ? I suspect that will work (and the 
library just wasnt able to read the barcode for these tapes). If it doesnt then 
you probably have a hardware fault.</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>Dave Markham &lt;dave.markham AT fjserv 
DOT net&gt;</b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT 
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">23/03/2006 15:14</font>
<br><font size=1 face="sans-serif">Please respond to dave.markham</font>
<br>
<td><font size=1 face="Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbsp; 
&nbsp; &nbsp; &nbsp;&quot;veritas-bu AT mailman.eng.auburn DOT edu&quot; 
&lt;veritas-bu AT mailman.eng.auburn DOT edu&gt;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbsp; 
&nbsp; &nbsp; &nbsp;</font>
<br><font size=1 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject: &nbsp; 
&nbsp; &nbsp; &nbsp;[Veritas-bu] drives showing UNKNOWN</font></table>
<br>
<br>
<br><font size=2 face="Courier New">Netbackup 5.0 mp5s2 on solaris 8 connected 
to L1000 with 4 DLT7000<br>
drives in.<br>
<br>
Has anyone seen it where robtest shows drive with barcode UNKNOWN, yet<br>
there are no tapes in the drive?<br>
<br>
Invoking robotic test utility:<br>
/usr/openv/volmgr/bin/tldtest -r /dev/sg/c3t0l0 -d1 /dev/rmt/0cbn -d2<br>
/dev/rmt/1cbn -d3 /dev/rmt/2cbn -d4 /dev/rmt/3cbn<br>
<br>
Opening /dev/sg/c3t0l0<br>
MODE_SENSE complete<br>
Enter tld commands (? returns help information)<br>
s d<br>
drive 1 (addr 128) access = 1 Contains Cartridge = no<br>
SCSI ID from drive 1 is 2<br>
drive 2 (addr 129) access = 1 Contains Cartridge = no<br>
SCSI ID from drive 2 is 3<br>
drive 3 (addr 130) access = 1 Contains Cartridge = yes<br>
Barcode = UNKNOWN<br>
SCSI ID from drive 3 is 4<br>
drive 4 (addr 131) access = 1 Contains Cartridge = yes<br>
Barcode = UNKNOWN<br>
SCSI ID from drive 4 is 5<br>
READ_ELEMENT_STATUS complete<br>
<br>
<br>
The drives keep going down if i up them and a job tries to use them.<br>
<br>
I currently have them in a down state. The drives are flashing, but the<br>
akibia support after not responding for ages are trying to say its a<br>
netbackup problem as mt -f /dev/rmt/2cbn status shows there is no tape<br>
loaded. ( which it wouldnt because there isnt one )<br>
<br>
# for d in 0 1 2 3; do mt -f /dev/rmt/$d'cbn' status; done<br>
/dev/rmt/0cbn: no tape loaded or drive offline<br>
/dev/rmt/1cbn: no tape loaded or drive offline<br>
/dev/rmt/2cbn: no tape loaded or drive offline<br>
/dev/rmt/3cbn: no tape loaded or drive offline<br>
<br>
<br>
I am thinking the drives are goosed and robtest cannot talk to them to<br>
get a clear picture. Is this on the right track?<br>
<br>
Anyone any ideas?<br>
<br>
<br>
_______________________________________________<br>
Veritas-bu maillist &nbsp;- &nbsp;Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
--=_alternative 005546A98025713A_=--

<Prev in Thread] Current Thread [Next in Thread>