Veritas-bu

[Veritas-bu] L9 DLT Library SCSI issues

2002-11-19 10:30:02
Subject: [Veritas-bu] L9 DLT Library SCSI issues
From: BrochF AT europe.stortek DOT com (Brochart, Fabrice)
Date: Tue, 19 Nov 2002 15:30:02 -0000
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_01C28FE0.873D6830
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Well, I don't know if it's relevant but have you try to unload the sg =
driver
??

modinfo,modunload,modload ???

Hth

F@b

-----Message d'origine-----
De : Pete Bentley [mailto:pete AT sorted DOT org]
Envoy=E9 : mardi 19 novembre 2002 16:09
=C0 : Veritas-bu AT mailman.eng.auburn DOT edu
Objet : [Veritas-bu] L9 DLT Library SCSI issues


Hi,

This is probabkly more of a Solaris issue than NBU, but I was hoping
one of you guys might have seen it before...

We have an E450 running Solaris 2.6 using Veritas Netbackup to
back up to a Storedge L9 DLT library. The drive and loader in
the library are daisy-chained on the same SCSI bus, the loader
has ID 0, the drive ID 1 and there are no other devices connected
to that SCSI bus.

The robot in the L9 failed, and the unit was hot-swapped out by Sun
without rebooting the box (it's a 24x7 box, rebooting is not
really an option here).

The new unit appears to function OK:-
* Inventories itself fine and passes its "wellness" test
* Veritas can identify the DLT drive and seems to
  communicate with it OK
* Veritas can identify the loader but *not* communicate
  with it

We don't think this is a Veritas issue, as even running their
low level tldtest command fails:-

# /usr/openv/volmgr/bin/tldtest -r /dev/sg/c2t0l0
Opening /dev/sg/c2t0l0
mode_sense failed, CHECK CONDITION
sense key =3D 0x2, asc =3D 0x4, ascq =3D 0x1, LOGICAL UNIT IN PROCESS =
OF BECOMING
READY

Things that have been tried/ruled out:-
* Dodgy SCSI chain - Both the drive and loader show up fine in sgscan:-
/dev/sg/c2t0l0: Changer: "HP      C7145-8000"
/dev/sg/c2t1l0: Tape (/dev/rmt/0): "QUANTUM DLT8000"

* Power cycling the library (it comes up, invetopries itself and =
carries
on giving the same responses)

* Re-running drvconfig, devlinks, sg.build etc


So far Sun's only suggestion has been to reboot the box which, as I=20
mentioned, would not be an option for some weeks.

Any other ideas? A Google search suggests this has happened to other
people, but I've not managed to find an explanation...

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

------_=_NextPart_001_01C28FE0.873D6830
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.2653.12">
<TITLE>RE: [Veritas-bu] L9 DLT Library SCSI issues</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Well, I don't know if it's relevant but have you try =
to unload the sg driver ??</FONT>
</P>

<P><FONT SIZE=3D2>modinfo,modunload,modload ???</FONT>
</P>

<P><FONT SIZE=3D2>Hth</FONT>
</P>

<P><FONT SIZE=3D2>F@b</FONT>
</P>

<P><FONT SIZE=3D2>-----Message d'origine-----</FONT>
<BR><FONT SIZE=3D2>De : Pete Bentley [<A =
HREF=3D"mailto:pete AT sorted DOT org">mailto:pete AT sorted DOT org</A>]</FONT>
<BR><FONT SIZE=3D2>Envoy=E9 : mardi 19 novembre 2002 16:09</FONT>
<BR><FONT SIZE=3D2>=C0 : Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Objet : [Veritas-bu] L9 DLT Library SCSI =
issues</FONT>
</P>
<BR>

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

<P><FONT SIZE=3D2>This is probabkly more of a Solaris issue than NBU, =
but I was hoping</FONT>
<BR><FONT SIZE=3D2>one of you guys might have seen it before...</FONT>
</P>

<P><FONT SIZE=3D2>We have an E450 running Solaris 2.6 using Veritas =
Netbackup to</FONT>
<BR><FONT SIZE=3D2>back up to a Storedge L9 DLT library. The drive and =
loader in</FONT>
<BR><FONT SIZE=3D2>the library are daisy-chained on the same SCSI bus, =
the loader</FONT>
<BR><FONT SIZE=3D2>has ID 0, the drive ID 1 and there are no other =
devices connected</FONT>
<BR><FONT SIZE=3D2>to that SCSI bus.</FONT>
</P>

<P><FONT SIZE=3D2>The robot in the L9 failed, and the unit was =
hot-swapped out by Sun</FONT>
<BR><FONT SIZE=3D2>without rebooting the box (it's a 24x7 box, =
rebooting is not</FONT>
<BR><FONT SIZE=3D2>really an option here).</FONT>
</P>

<P><FONT SIZE=3D2>The new unit appears to function OK:-</FONT>
<BR><FONT SIZE=3D2>* Inventories itself fine and passes its =
&quot;wellness&quot; test</FONT>
<BR><FONT SIZE=3D2>* Veritas can identify the DLT drive and seems =
to</FONT>
<BR><FONT SIZE=3D2>&nbsp; communicate with it OK</FONT>
<BR><FONT SIZE=3D2>* Veritas can identify the loader but *not* =
communicate</FONT>
<BR><FONT SIZE=3D2>&nbsp; with it</FONT>
</P>

<P><FONT SIZE=3D2>We don't think this is a Veritas issue, as even =
running their</FONT>
<BR><FONT SIZE=3D2>low level tldtest command fails:-</FONT>
</P>

<P><FONT SIZE=3D2># /usr/openv/volmgr/bin/tldtest -r =
/dev/sg/c2t0l0</FONT>
<BR><FONT SIZE=3D2>Opening /dev/sg/c2t0l0</FONT>
<BR><FONT SIZE=3D2>mode_sense failed, CHECK CONDITION</FONT>
<BR><FONT SIZE=3D2>sense key =3D 0x2, asc =3D 0x4, ascq =3D 0x1, =
LOGICAL UNIT IN PROCESS OF BECOMING READY</FONT>
</P>

<P><FONT SIZE=3D2>Things that have been tried/ruled out:-</FONT>
<BR><FONT SIZE=3D2>* Dodgy SCSI chain - Both the drive and loader show =
up fine in sgscan:-</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t0l0: Changer: =
&quot;HP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C7145-8000&quot;</FONT>
<BR><FONT SIZE=3D2>/dev/sg/c2t1l0: Tape (/dev/rmt/0): &quot;QUANTUM =
DLT8000&quot;</FONT>
</P>

<P><FONT SIZE=3D2>* Power cycling the library (it comes up, invetopries =
itself and carries</FONT>
<BR><FONT SIZE=3D2>on giving the same responses)</FONT>
</P>

<P><FONT SIZE=3D2>* Re-running drvconfig, devlinks, sg.build etc</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>So far Sun's only suggestion has been to reboot the =
box which, as I </FONT>
<BR><FONT SIZE=3D2>mentioned, would not be an option for some =
weeks.</FONT>
</P>

<P><FONT SIZE=3D2>Any other ideas? A Google search suggests this has =
happened to other</FONT>
<BR><FONT SIZE=3D2>people, but I've not managed to find an =
explanation...</FONT>
</P>

<P><FONT SIZE=3D2>Pete.</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_01C28FE0.873D6830--

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