Veritas-bu

[Veritas-bu] Eight new SDLT320 drives not being recognzied by NBU Datacenter 3 .4

2004-05-04 22:06:40
Subject: [Veritas-bu] Eight new SDLT320 drives not being recognzied by NBU Datacenter 3 .4
From: jon.hardt AT cendant DOT com (Hardt, Jon)
Date: Tue, 4 May 2004 20:06:40 -0600
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C43245.9AA06AE5
Content-Type: text/plain;
        charset="iso-8859-1"

My st driver version is...
39 102cb226  12dcc  33   1  st (SCSI tape Driver 1.216)

We are at kernel rev 108528-24

Although it seems to me that a driver/patch issue seems unlikely, given that
we can actually use 2 of the 8 tape drives. My st.conf, devlinks and sg.conf
files look correct...it must be some sort of configuration error.

bash-2.03# ./sgscan all
/dev/sg/c0t6l0: Cdrom: "TOSHIBA DVD-ROM SD-M1401"
/dev/sg/c0tw21000004cf20f03el0: Disk (???): "SEAGATE ST336605FSUN36G"
/dev/sg/c0tw21000004cf20f8d3l0: Disk (???): "SEAGATE ST336605FSUN36G"
/dev/sg/c2t4l0: Tape (/dev/rmt/0): "QUANTUM SDLT320"  -- ## This drive works
/dev/sg/c2t4l1: Tape (/dev/rmt/1): "QUANTUM SDLT320"
/dev/sg/c2t4l2: Tape (/dev/rmt/2): "QUANTUM SDLT320"
/dev/sg/c2t4l3: Tape (/dev/rmt/3): "QUANTUM SDLT320"
/dev/sg/c2t5l0: Tape (/dev/rmt/4): "QUANTUM SDLT320"  -- ## This drive works
/dev/sg/c2t5l1: Tape (/dev/rmt/5): "QUANTUM SDLT320"
/dev/sg/c2t5l2: Tape (/dev/rmt/6): "QUANTUM SDLT320"
/dev/sg/c2t5l3: Tape (/dev/rmt/7): "QUANTUM SDLT320"
/dev/sg/c2t9l0: Changer: "STK     L180"

It seems like too much of a coincidence that LUN 0 on both targets are the
only drives that work correctly. But I have verified the conf files to be
correct ....


-----Original Message-----
From: Simon, John [mailto:JSimon AT reliant DOT com]
Sent: Tuesday, May 04, 2004 7:40 PM
To: Hardt, Jon; Veritas-Bu (E-mail)
Subject: RE: [Veritas-bu] Eight new SDLT320 drives not being recognzied
by NBU Datacenter 3 .4


How do you have persistant binding setup? What version of the st patch do
you have? You may need to update your st driver or add to the st.conf if
your drives aren't supported directly. What kernel rev are you at?

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Hardt, Jon
Sent: Tuesday, May 04, 2004 5:03 PM
To: Veritas-Bu (E-mail)
Subject: RE: [Veritas-bu] Eight new SDLT320 drives not being recognzied
by NBU Datacenter 3 .4


Orginally I thought that could perhaps be an issue, but apparently NBU's
naming convention is purely abstract...meaning SuperDLT, DLTIV, etc have no
direct correspondence with NBU's dlt, dlt2, dlt3 etc naming convention. They
are for you to use however you like; a good example would be if you had two
different types of drives in the same library...wouldn't want one drive
using the other drives tapes so you could configure them in different dltX
environments. Oh if my problem were only that easy :)

-----Original Message-----
From: Major, Rusty [mailto:jrmajor AT TexasChildrensHospital DOT org]
Sent: Tuesday, May 04, 2004 3:51 PM
To: Hardt, Jon
Subject: RE: [Veritas-bu] Eight new SDLT320 drives not being recognzied
by NBU Datacenter 3 .4


Jon,

I'm on a windows environment, so I'm no Unix expert.
I thought that maybe the devices were not set up correctly?
Maybe setup as dlt instead of dlt2, etc...

Good luck!
Rusty

> -----Original Message-----
> From: Hardt, Jon [mailto:jon.hardt AT cendant DOT com]
> Sent: Tuesday, May 04, 2004 3:24 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Eight new SDLT320 drives not being recognzied by
> NBU Datacenter 3 .4
> 
> 
> Recently, we upgraded our tape library (StorageTek L180) from 
> 4 Quantum 8000
> tape drives to 8 Quantum SDLT320 drives. However, only 2 
> drives are usable
> at this point. The other 6 drives are reported as DOWN-TLD in NBU 3.4
> 
> Our setup:
> 
> StorageTek L180
> 8 SDLT320 drives connected through 2 StorageTek 3300 routers
> Local host is Sun 220R running Solaris 8 -- fiber 
> connectivity HBAs JNI 6410
> 
> The odd thing is that a sgscan produces the correct mappings:
> 
> bash-2.03# ./sgscan all
> /dev/sg/c0t6l0: Cdrom: "TOSHIBA DVD-ROM SD-M1401"
> /dev/sg/c0tw21000004cf20f03el0: Disk (???): "SEAGATE ST336605FSUN36G"
> /dev/sg/c0tw21000004cf20f8d3l0: Disk (???): "SEAGATE ST336605FSUN36G"
> /dev/sg/c2t4l0: Tape (/dev/rmt/0): "QUANTUM SDLT320"
> /dev/sg/c2t4l1: Tape (/dev/rmt/1): "QUANTUM SDLT320"
> /dev/sg/c2t4l2: Tape (/dev/rmt/2): "QUANTUM SDLT320"
> /dev/sg/c2t4l3: Tape (/dev/rmt/3): "QUANTUM SDLT320"
> /dev/sg/c2t5l0: Tape (/dev/rmt/4): "QUANTUM SDLT320"
> /dev/sg/c2t5l1: Tape (/dev/rmt/5): "QUANTUM SDLT320"
> /dev/sg/c2t5l2: Tape (/dev/rmt/6): "QUANTUM SDLT320"
> /dev/sg/c2t5l3: Tape (/dev/rmt/7): "QUANTUM SDLT320"
> /dev/sg/c2t9l0: Changer: "STK     L180"
> 
> However, when trying to use drives 2, 3, 4, 6, 7 and 8 we 
> will get some sort
> of varation of this messages in /var/adm/messages:
> 
> May  4 11:01:12 med01den avrd[5623]: [ID 914860 daemon.error] 
> Fatal open
> error on Drive6 (device 5, /dev/rmt/5cbn),
>  errno = 6 (No such device or address), DOWN'ing it
> May  4 11:01:12 med01den avrd[5623]: [ID 529501 daemon.error] 
> Fatal open
> error on Drive7 (device 6, /dev/rmt/6cbn),
>  errno = 6 (No such device or address), DOWN'ing it
> 
> Same type of this when trying to stat the drive:
> 
> bash-2.03# mt -f /dev/rmt/0cbn stat      # This is one of the 
> working drives
> /dev/rmt/0cbn: Device busy
> bash-2.03# mt -f /dev/rmt/1cbn stat
> /dev/rmt/1cbn: No such device or address
> bash-2.03# mt -f /dev/rmt/2cbn stat
> /dev/rmt/2cbn: No such device or address
> bash-2.03# mt -f /dev/rmt/3cbn stat
> /dev/rmt/3cbn: No such device or address
> bash-2.03# mt -f /dev/rmt/4cbn stat        # This is the 
> other working drive
> /dev/rmt/4cbn: Device busy
> bash-2.03# mt -f /dev/rmt/5cbn stat
> /dev/rmt/5cbn: No such device or address
> bash-2.03# mt -f /dev/rmt/6cbn stat
> /dev/rmt/6cbn: No such device or address
> bash-2.03# mt -f /dev/rmt/7cbn stat
> /dev/rmt/7cbn: No such device or address
> bash-2.03#
> 
> All the expect links exist in /dev/rmt ... notations for 
> drives 0 through
> 7... I can't figure out why NBU doesn't think there is 
> anything attached at
> the /dev/rmt/Xcbn addresses. I've done what seems like hundreds of
> reconfiguration reboots, but no love. I am totally confused; 
> if anyone has
> any idea on why I can't use the other 6 drives or could give 
> me some good
> troubleshooting steps, please fire away.
> 
> ---
> Jon Hardt
> Unix Systems Administrator
> Cheap Tickets, part of Trip Networks
> 6560 Greenwood Plaza Blvd., Englewood, CO 80111
> Office: (303) 357-3314
> Mobile: (303) 522-7537
> jon.hardt AT cendant DOT com
> YIM: jonhardt
> www.cheaptickets.com
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

------_=_NextPart_001_01C43245.9AA06AE5
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>RE: [Veritas-bu] Eight new SDLT320 drives not being recognzied =
by NBU Datacenter 3 .4</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>My st driver version is...</FONT>
<BR><FONT SIZE=3D2>39 102cb226&nbsp; 12dcc&nbsp; 33&nbsp;&nbsp; 1&nbsp; =
st (SCSI tape Driver 1.216)</FONT>
</P>

<P><FONT SIZE=3D2>We are at kernel rev 108528-24</FONT>
</P>

<P><FONT SIZE=3D2>Although it seems to me that a driver/patch issue =
seems unlikely, given that we can actually use 2 of the 8 tape drives. =
My st.conf, devlinks and sg.conf files look correct...it must be some =
sort of configuration error.</FONT></P>

<P><FONT SIZE=3D2>bash-2.03# ./sgscan all</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c0t6l0: Cdrom: &quot;TOSHIBA DVD-ROM =
SD-M1401&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c0tw21000004cf20f03el0: Disk (???): =
&quot;SEAGATE ST336605FSUN36G&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c0tw21000004cf20f8d3l0: Disk (???): =
&quot;SEAGATE ST336605FSUN36G&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t4l0: Tape (/dev/rmt/0): &quot;QUANTUM =
SDLT320&quot;&nbsp; -- ## This drive works</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t4l1: Tape (/dev/rmt/1): &quot;QUANTUM =
SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t4l2: Tape (/dev/rmt/2): &quot;QUANTUM =
SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t4l3: Tape (/dev/rmt/3): &quot;QUANTUM =
SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t5l0: Tape (/dev/rmt/4): &quot;QUANTUM =
SDLT320&quot;&nbsp; -- ## This drive works</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t5l1: Tape (/dev/rmt/5): &quot;QUANTUM =
SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t5l2: Tape (/dev/rmt/6): &quot;QUANTUM =
SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t5l3: Tape (/dev/rmt/7): &quot;QUANTUM =
SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t9l0: Changer: =
&quot;STK&nbsp;&nbsp;&nbsp;&nbsp; L180&quot;</FONT>
</P>

<P><FONT SIZE=3D2>It seems like too much of a coincidence that LUN 0 on =
both targets are the only drives that work correctly. But I have =
verified the conf files to be correct ....</FONT></P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Simon, John [<A =
HREF=3D"mailto:JSimon AT reliant DOT com">mailto:JSimon AT reliant DOT 
com</A>]</FONT>=

<BR><FONT SIZE=3D2>Sent: Tuesday, May 04, 2004 7:40 PM</FONT>
<BR><FONT SIZE=3D2>To: Hardt, Jon; Veritas-Bu (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Eight new SDLT320 drives =
not being recognzied</FONT>
<BR><FONT SIZE=3D2>by NBU Datacenter 3 .4</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>How do you have persistant binding setup? What =
version of the st patch do you have? You may need to update your st =
driver or add to the st.conf if your drives aren't supported directly. =
What kernel rev are you at?</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: veritas-bu-admin AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu">mailto:veritas-b=
u-admin AT mailman.eng.auburn DOT edu</A>]On Behalf Of Hardt, Jon</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, May 04, 2004 5:03 PM</FONT>
<BR><FONT SIZE=3D2>To: Veritas-Bu (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Eight new SDLT320 drives =
not being recognzied</FONT>
<BR><FONT SIZE=3D2>by NBU Datacenter 3 .4</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Orginally I thought that could perhaps be an issue, =
but apparently NBU's</FONT>
<BR><FONT SIZE=3D2>naming convention is purely abstract...meaning =
SuperDLT, DLTIV, etc have no</FONT>
<BR><FONT SIZE=3D2>direct correspondence with NBU's dlt, dlt2, dlt3 etc =
naming convention. They</FONT>
<BR><FONT SIZE=3D2>are for you to use however you like; a good example =
would be if you had two</FONT>
<BR><FONT SIZE=3D2>different types of drives in the same =
library...wouldn't want one drive</FONT>
<BR><FONT SIZE=3D2>using the other drives tapes so you could configure =
them in different dltX</FONT>
<BR><FONT SIZE=3D2>environments. Oh if my problem were only that easy =
:)</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Major, Rusty [<A =
HREF=3D"mailto:jrmajor AT TexasChildrensHospital DOT org">mailto:jrmajor@TexasC=
hildrensHospital.org</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, May 04, 2004 3:51 PM</FONT>
<BR><FONT SIZE=3D2>To: Hardt, Jon</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Eight new SDLT320 drives =
not being recognzied</FONT>
<BR><FONT SIZE=3D2>by NBU Datacenter 3 .4</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Jon,</FONT>
</P>

<P><FONT SIZE=3D2>I'm on a windows environment, so I'm no Unix =
expert.</FONT>
<BR><FONT SIZE=3D2>I thought that maybe the devices were not set up =
correctly?</FONT>
<BR><FONT SIZE=3D2>Maybe setup as dlt instead of dlt2, etc...</FONT>
</P>

<P><FONT SIZE=3D2>Good luck!</FONT>
<BR><FONT SIZE=3D2>Rusty</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Hardt, Jon [<A =
HREF=3D"mailto:jon.hardt AT cendant DOT com">mailto:jon.hardt AT cendant DOT 
com</A>]<=
/FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Tuesday, May 04, 2004 3:24 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: [Veritas-bu] Eight new SDLT320 drives =
not being recognzied by</FONT>
<BR><FONT SIZE=3D2>&gt; NBU Datacenter 3 .4</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Recently, we upgraded our tape library =
(StorageTek L180) from </FONT>
<BR><FONT SIZE=3D2>&gt; 4 Quantum 8000</FONT>
<BR><FONT SIZE=3D2>&gt; tape drives to 8 Quantum SDLT320 drives. =
However, only 2 </FONT>
<BR><FONT SIZE=3D2>&gt; drives are usable</FONT>
<BR><FONT SIZE=3D2>&gt; at this point. The other 6 drives are reported =
as DOWN-TLD in NBU 3.4</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Our setup:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; StorageTek L180</FONT>
<BR><FONT SIZE=3D2>&gt; 8 SDLT320 drives connected through 2 StorageTek =
3300 routers</FONT>
<BR><FONT SIZE=3D2>&gt; Local host is Sun 220R running Solaris 8 -- =
fiber </FONT>
<BR><FONT SIZE=3D2>&gt; connectivity HBAs JNI 6410</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; The odd thing is that a sgscan produces the =
correct mappings:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03# ./sgscan all</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c0t6l0: Cdrom: &quot;TOSHIBA DVD-ROM =
SD-M1401&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c0tw21000004cf20f03el0: Disk (???): =
&quot;SEAGATE ST336605FSUN36G&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c0tw21000004cf20f8d3l0: Disk (???): =
&quot;SEAGATE ST336605FSUN36G&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c2t4l0: Tape (/dev/rmt/0): =
&quot;QUANTUM SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c2t4l1: Tape (/dev/rmt/1): =
&quot;QUANTUM SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c2t4l2: Tape (/dev/rmt/2): =
&quot;QUANTUM SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c2t4l3: Tape (/dev/rmt/3): =
&quot;QUANTUM SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c2t5l0: Tape (/dev/rmt/4): =
&quot;QUANTUM SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c2t5l1: Tape (/dev/rmt/5): =
&quot;QUANTUM SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c2t5l2: Tape (/dev/rmt/6): =
&quot;QUANTUM SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c2t5l3: Tape (/dev/rmt/7): =
&quot;QUANTUM SDLT320&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/sg/c2t9l0: Changer: =
&quot;STK&nbsp;&nbsp;&nbsp;&nbsp; L180&quot;</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; However, when trying to use drives 2, 3, 4, 6, =
7 and 8 we </FONT>
<BR><FONT SIZE=3D2>&gt; will get some sort</FONT>
<BR><FONT SIZE=3D2>&gt; of varation of this messages in =
/var/adm/messages:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; May&nbsp; 4 11:01:12 med01den avrd[5623]: [ID =
914860 daemon.error] </FONT>
<BR><FONT SIZE=3D2>&gt; Fatal open</FONT>
<BR><FONT SIZE=3D2>&gt; error on Drive6 (device 5, =
/dev/rmt/5cbn),</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; errno =3D 6 (No such device or address), =
DOWN'ing it</FONT>
<BR><FONT SIZE=3D2>&gt; May&nbsp; 4 11:01:12 med01den avrd[5623]: [ID =
529501 daemon.error] </FONT>
<BR><FONT SIZE=3D2>&gt; Fatal open</FONT>
<BR><FONT SIZE=3D2>&gt; error on Drive7 (device 6, =
/dev/rmt/6cbn),</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; errno =3D 6 (No such device or address), =
DOWN'ing it</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Same type of this when trying to stat the =
drive:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03# mt -f /dev/rmt/0cbn =
stat&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # This is one of the </FONT>
<BR><FONT SIZE=3D2>&gt; working drives</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/rmt/0cbn: Device busy</FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03# mt -f /dev/rmt/1cbn stat</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/rmt/1cbn: No such device or address</FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03# mt -f /dev/rmt/2cbn stat</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/rmt/2cbn: No such device or address</FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03# mt -f /dev/rmt/3cbn stat</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/rmt/3cbn: No such device or address</FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03# mt -f /dev/rmt/4cbn =
stat&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # This is the </FONT>
<BR><FONT SIZE=3D2>&gt; other working drive</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/rmt/4cbn: Device busy</FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03# mt -f /dev/rmt/5cbn stat</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/rmt/5cbn: No such device or address</FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03# mt -f /dev/rmt/6cbn stat</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/rmt/6cbn: No such device or address</FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03# mt -f /dev/rmt/7cbn stat</FONT>
<BR><FONT SIZE=3D2>&gt; /dev/rmt/7cbn: No such device or address</FONT>
<BR><FONT SIZE=3D2>&gt; bash-2.03#</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; All the expect links exist in /dev/rmt ... =
notations for </FONT>
<BR><FONT SIZE=3D2>&gt; drives 0 through</FONT>
<BR><FONT SIZE=3D2>&gt; 7... I can't figure out why NBU doesn't think =
there is </FONT>
<BR><FONT SIZE=3D2>&gt; anything attached at</FONT>
<BR><FONT SIZE=3D2>&gt; the /dev/rmt/Xcbn addresses. I've done what =
seems like hundreds of</FONT>
<BR><FONT SIZE=3D2>&gt; reconfiguration reboots, but no love. I am =
totally confused; </FONT>
<BR><FONT SIZE=3D2>&gt; if anyone has</FONT>
<BR><FONT SIZE=3D2>&gt; any idea on why I can't use the other 6 drives =
or could give </FONT>
<BR><FONT SIZE=3D2>&gt; me some good</FONT>
<BR><FONT SIZE=3D2>&gt; troubleshooting steps, please fire away.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; ---</FONT>
<BR><FONT SIZE=3D2>&gt; Jon Hardt</FONT>
<BR><FONT SIZE=3D2>&gt; Unix Systems Administrator</FONT>
<BR><FONT SIZE=3D2>&gt; Cheap Tickets, part of Trip Networks</FONT>
<BR><FONT SIZE=3D2>&gt; 6560 Greenwood Plaza Blvd., Englewood, CO =
80111</FONT>
<BR><FONT SIZE=3D2>&gt; Office: (303) 357-3314</FONT>
<BR><FONT SIZE=3D2>&gt; Mobile: (303) 522-7537</FONT>
<BR><FONT SIZE=3D2>&gt; jon.hardt AT cendant DOT com</FONT>
<BR><FONT SIZE=3D2>&gt; YIM: jonhardt</FONT>
<BR><FONT SIZE=3D2>&gt; www.cheaptickets.com</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>&gt; <A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist&nbsp; -&nbsp; =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C43245.9AA06AE5--

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