This is a multi-part message in MIME format.
------_=_NextPart_001_01C4B068.99E928AC
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
84 errors are a general error message indicating a problem in the SCSI
chain.
OK here comes all the crap we all are aware of... sorry
Are the firmware and SCSI drivers current?
Is the the SCSI cable in good shape? (if you can replace it just in
case)
Is the BIOS on the drive current?
Ready for the good new? It most likely a bad tape or dirty/failing
drive. Before you go through all that other stuff do the following:
Hopefully like me you are using SDLT drives. If so download DLTsage
from Quantum.
After you become familiar with it (shouldn't take more than 2days), you
will be able to determine if the problem is a bad tape or a dirty drive.
Two very easy fixes. And if you've been using quantum's tapes they will
replace the defective media... no questions asked!
=20
Good luck
Darby Moses
=20
=20
_____ =20
From: len boyle [mailto:len.boyle AT sas DOT com]=20
Sent: Tuesday, October 12, 2004 9:42 AM
To: Johan Redelinghuys; Veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Error 84 and comments
Hello Johan
=20
We found that most of our 84 errors were bad dlt tapes or bad dlt tape
drives. And it was always fun trying to determine which or both were the
problem.=20
We tixed this problem by replacing the tape drives with lto 2 tape
drives and lto 2 tape carts. So at this time 84 errors are for the most
part no longer an issue for us.=20
I am not sure if this will be the case a few years down the road.=20
=20
=20
Since you were getting 52 errors you might be seeing another reason
beyond bad tapes and drives.=20
=20
Can you let us know a little more about what you are seeing. Are you
using sso, scsi to fibre bridges, .....
=20
Regards len
----- Original Message -----=20
From: Johan Redelinghuys <mailto:johan.redelinghuys AT stg.co DOT za>
=20
To: Veritas-bu AT mailman.eng.auburn DOT edu=20
Sent: Tuesday, October 12, 2004 3:26 AM
Subject: [Veritas-bu] Error 84 and comments
Hi All
=20
Does it also seem to you people that error 84 is becoming more
and more of an issue? The focus point, it seems, have moved from error
52 to error 84 as being our no 1 problem at the moment.
=20
Can the people that had error 84's and managed to fix the
problem, please indicate what was causing the error and what they did to
fix it.
=20
From people on the WEB there seems to be 101 different reasons
and fixes, with no indication of any pattern to pinpoint the reason.
Also the fixes other people implemented, does nothing in our own
environment.
=20
Is there any good reason to upgrade from NBU_4.5_FP6 to NBU_5_x
other than it is the latest version?
=20
JR
------_=_NextPart_001_01C4B068.99E928AC
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40"; xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR>
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: red; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: red; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dred link=3Dblue bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>84 errors are a general error message =
indicating a problem=20
in the SCSI chain.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>OK here comes all the crap we all are aware =
of...=20
sorry</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Are the firmware and SCSI drivers=20
current?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Is the the SCSI cable in good shape? (if you =
can replace it=20
just in case)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Is the BIOS on the drive =
current?</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Ready for the good new? It most likely a =
bad tape or=20
dirty/failing drive. Before you go through all that other stuff do =
the=20
following:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hopefully like me you are using SDLT =
drives. If so=20
download DLTsage from Quantum.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>After you become familiar with it (shouldn't =
take more than=20
2days), you will be able to </FONT></SPAN><SPAN =
class=3D235542314-12102004><FONT=20
face=3DArial color=3D#0000ff size=3D2>determine if the problem is a bad =
tape or a=20
dirty drive. Two very easy fixes. And if you've been using =
quantum's=20
tapes they will replace the defective media... no questions=20
asked!</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Good luck</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Darby Moses</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D235542314-12102004><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> len boyle =
[mailto:len.boyle AT sas DOT com]=20
<BR><B>Sent:</B> Tuesday, October 12, 2004 9:42 AM<BR><B>To:</B> Johan=20
Redelinghuys; Veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> Re:=20
[Veritas-bu] Error 84 and comments<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=3DArial size=3D2>Hello Johan</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>We found that most of our 84 errors =
were bad dlt=20
tapes or bad dlt tape drives. And it was always fun trying to determine =
which or=20
both were the problem. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>We tixed this problem by replacing the =
tape drives=20
with lto 2 tape drives and lto 2 tape carts. So at this time 84 errors =
are for=20
the most part no longer an issue for us. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I am not sure if this will be the case =
a few years=20
down the road. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Since you were getting 52 errors you =
might be=20
seeing another reason beyond bad tapes and drives. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Can you let us know a little more about =
what you=20
are seeing. Are you using sso, scsi to fibre bridges, =
.....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Regards len</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Djohan.redelinghuys AT stg.co DOT za=20
href=3D"mailto:johan.redelinghuys AT stg.co DOT za">Johan Redelinghuys</A> =
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
title=3DVeritas-bu AT mailman.eng.auburn DOT edu=20
=
href=3D"mailto:Veritas-bu AT mailman.eng.auburn DOT edu">Veritas-bu AT mailman
DOT eng.=
auburn.edu</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, October 12, 2004 =
3:26=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Veritas-bu] Error 84 =
and=20
comments</DIV>
<DIV><BR></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
All<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Does it also seem to you =
people=20
that error 84 is becoming more and more of an issue? The focus point, =
it=20
seems, have moved from error 52 to error 84 as being our no 1 problem =
at the=20
moment.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Can the people that had =
error 84’s=20
and managed to fix the problem, please indicate what was causing the =
error and=20
what they did to fix it.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">From people on the WEB =
there seems=20
to be 101 different reasons and fixes, with no indication of any =
pattern to=20
pinpoint the reason. Also the fixes other people implemented, does =
nothing in=20
our own environment.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is there any good reason =
to=20
upgrade from NBU_4.5_FP6 to NBU_5_x other than it is the latest=20
version?<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">JR<o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C4B068.99E928AC--
|
