Hello,
Oh, boy, i remember working on STK 9714 and DLT7000, placing weekly calls
to support, your problem seems to be hardware related at first glance,
make sure you get it thoroughly checked out. Running Diag on the SCSI Card
may also rule out any issues, you many also want to go through HBA Bios
settings, if there were any recent changes to it & make sure they match
STK, servers recommendation.
Is this a new install or did you just started having issue recently, did
you update any software including Networker recently ?
What happens if you load unload tapes manually, when there are no backups
running ? Does the lib panel have any errors displayed ?
HTH
Thomas S Pinard <tom.pinard AT VERIZON DOT COM>
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
06/02/2008 02:43 PM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond
to
Thomas S Pinard <tom.pinard AT VERIZON DOT COM>
To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc
Subject
[Networker] No Additional Sense, Diagnostic Failure on Component
Folks-
I am seeing an odd error... I'm wondering if anyone else has seen this
before.
Background:
Server:
Sun Netra t1125, SunOS 5.8
NetWorker 7.3.2.Build.364 Network Edition
Jukebox:
Storagetek Timberwolf 9710, DLT7000 drives
Backups cruise along just fine for a while, it swaps full tapes just fine,
etc. Eventually, though, a tape will fill and it won't load a new tape.
In the log files, I see things like this:
==========
nsrd: Operation 5893 started : Load volume `production.0026'.
nsrlcpd #1: Jukebox error: Jukebox:juke0 access:[email protected] failed:MOVE
MEDIUM key:4 status:CHECK CONDITION No Additional Sense, Diagnostic
Failure on Component 0x02
nsrmmgd: lcpd 1 at host backup0 reported error 'Jukebox:juke0
access:[email protected] failed:MOVE MEDIUM key:4 status:CHECK CONDITION
No Additional Sense, Diagnostic Failure on Component 0x02 ' for the
command `4'.
==========
>From that point on, I can't load/unload any tapes. Even "nsrjb -H -E"
fails. If the jukebox is power cycled, then everything is fine until the
next time the error occurs. I even tried disabling all but one tape
drive, but it still does it.
My first suspicions are that it is a SCSI cable or SCSI bus issue, but
before I send a tech out to look at it, I thought I would check to see if
anyone else has run across this before. I kind of doubt it is software
related, but it's always possible...
Thanks,
TomP
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type
"signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
