[Networker] AW: [Networker] Tape Looping Scenario

That sounds quite like the track on the tape and the head in the DLT are not
in sync. Maybe even only the density marker on the tape. We've had similar
problems - some tapes simply did not load properly and caused the dirty lamp
to light up. 
Our technical support suggested to replace the tapes which cause this
behaviour. But because this jukebox was to be used for another 3 months we
did not bother copying all the data and simply added cleaning tapes... so I
cannot tell you if it would have succeded

just my 2 cents...

-----Ursprüngliche Nachricht-----
Von: Charles Walther [mailto:CWalther AT SAROFIM DOT COM]
Gesendet: Freitag, 11. Oktober 2002 14:15
An: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Betreff: [Networker] Tape Looping Scenario


NW 6.1.1 for W2K on Proliant DL580

Two Problems:
Our Exabyte690d autoloader has a problem where it tries to load a tape into
our DLT7000 drive and the drive light goes dirty.  Legato usually unloads
the tape, then loads the cleaning cartridge before it tries to use the drive
again.  This happens multiple times per night.  We go through a cleaning
cartridge every couple of days. We have several hundred DLT-IV cartridges
that Legato can't seem to handle, but when we take them to a standalone DLT7
or 8000, they work just fine,  on load the drive light goes dirty, but then
clears itself.    This happens when trying to label, or when a group calls
for a mount.  We've replaced the exabyte, we've replaced the SCSI cables,
but it appears that it's the way that Legato handles the load process -
something is definitely different in 6.x from 5.x, or something is different
in NT 2K from NT 4.0.  We have d/l'ed MS hotfixes for the DLT handling, but
this did not help.  We have tried various DLT drivers, but we are stuck.
Please help.


Problem #2:
Occasionally, Legato tries to unload, it starts issueing:
\\.\Tapex Requires cleaning

messages at the rate of 2-5 per second

The drive tries to unload, but is not successful, therefore the messages
just keep pooring out by the boatload.  This loop goes on until we manually
eject, or the SAVEGROUP is stopped.

Has anyone else experienced this problem ?   This started when we upgraded
from NT 4.0, Legato 5.5.1 to Win2K and Legato 6.1.1.

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=