You should also run through a manual mount of each drive and verify that
each physical drives matches up with what the OS and NetWorker sees.  You
can use tools like sjirdtag and sjirelem to query each drive and move
elements around. I have seen an issue with one of our LTO Tape Libraries
where the NetWorker server and StorageNode where off on what drives they
were seeing.  Based on my experience these errors are one of the following:

        A Blank Tape
        A Tape that is labeled with a different label then what NetWorker is
looking for (Hence tape in wrong drive or query of wrong drive)

Hope some of this info helps.


Chad Smykay, RHCE, LCNA
Systems Storage Administrator
Rackspace Managed Hosting (TM)


-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU] 
On
Behalf Of Oscar Olsson
Sent: Monday, March 15, 2004 5:18 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: Re: [Networker] AIT-3 Problem - "No Tape Label Found"

On Thu, 11 Mar 2004, Matt Temple wrote:

MT> Last month, one of my three AIT-3 drives (in a 126-Qualstar library)
MT> started showing tape mount filaures.  The following is a sample:
MT>
MT> 03/10/04 22:34:17 nsrd: media info: loading volume Full.0343 into
MT> /dev/nst1
MT> 03/10/04 22:34:35 nsrd: /dev/nst1 Verify label operation in progress
MT> 03/10/04 22:35:47 nsrd: media warning: /dev/nst1 reading: Success
MT> 03/10/04 22:36:07 nsrd: media warning: /dev/nst1 reading: no tape
MT> label found.
MT> 03/10/04 22:36:08 nsrd: /dev/nst1 Eject operation in progress ...
MT> 03/10/04 22:36:44 nsrd: Jukebox 'jukebox1' failed: expected volume
MT> 'Full.0343' got 'NULL'.
MT>
MT> This will show up for all available tapes.
MT> No problem with the other drives.
MT>
MT> My first conclusion is simply that the drive is failing.   To complicate
MT> matters, if I power down the Qualstar unit, /dev/nst1 will mount
MT> a tape, once.   Then the above will occur.
MT>
MT> Has anyone experienced this sort of problem?
MT> Does anyone have any ideas beyond sticking a fork in the drive?

Yes. I had the exact same problem last week. It was due to a broken AIT-2
drive.

What I did to troubleshoot it was the following - you should probably try it
too:

1. shut down networker
2. open the jukebox or otherwise disable it so you can manually feed media
into the drives 3. take a known good tape - a brand new tape might be
sufficient too and insert it into one of the drives 4. check the status of
the drive with mt and confirm that there is a tape in the drive 5. tar some
medium-sized directory to the tape and then do a tar cvf to verify the data.
6. repeat for each drive
7. repair/burn the malfunctioning drive ;)

//Oscar

--
Note: To sign off this list, send a "signoff networker" 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 networker" 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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=