Looks to me like you need to do an AUDIT LIBRARY <libname> CHECKL=BARCODE.
TSM keeps its own library inventory.  If someone opens the library and
removes a tape or moves them around, TSM's inventory will be out of sync
with what's really in there.  This can also happen on some libraries if the
library auto-loads tapes through the entry-exit ports while tapes are in
drives... the new tapes may go into the "home" slot of a mounted tape...
happened to us on our ATL P3000, so we turned off auto-load.

Robin Sharpe
Berlex Labs



                    Bill Wheeler
                    <Bill.Wheeler@LA-
                    Z-BOY.COM>        To:    [EMAIL PROTECTED]
                                      cc:    (bcc: Robin Sharpe/WA/USR/SHG)
                    01/09/02 03:03 PM Subject:
                    Please respond to        Re: Tape Drive Failures
                    "ADSM: Dist Stor
                    Manager"







Here is a look at what the message is giving me in the actlog when it
fails.
It looks just like a plan tape error:

ANR8499I Command accepted.
01/05/02 08:58:03     ANR8300E I/O error on library MAGSTAR (OP=00006C03,

                       CC=314, KEY=05, ASC=3B, ASCQ=0E,
SENSE=70.00.05.00.00.0-

0.00.48.00.00.00.00.3B.0E.FF.02.00.A8.00.00.1E.09.01.00-

.00.00.00.00.00.00.A5.00.00.00.00.00.00.00.00.00.00.00.-

00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.0-

0.00.00.00.00.00.00.00.00.00.00.00.32.38.37.20.20.20.20-
                       .00., Description=The source slot or drive was empty
in
                       an attempt to move a volume).  Refer to Appendix B
in
the
                       'Messages' manual for recommended action.

01/05/02 08:58:03     ANR9999D mmsscsi.c(10695): Could not move volume
1DA7D

                       from slot 31 to slot 16.

01/05/02 08:58:03     ANR8841I Remove volume from slot 31 of library
MAGSTAR
at
                       your convenience.


After this the drive then goes offline.  So when the archive runs at 22:30
this is the message it gets:

01/05/02 22:41:20     ANR8447E No drives are currently available in library

                       MAGSTAR.

01/05/02 22:41:21     ANR1404W Scratch volume mount request denied - mount

                       failed.


When i look at the error message in the O/S errpt this is what i see

4865FA9B   0108012102 P H rmt1           TAPE OPERATION ERROR
476B351D   0108012102 P H rmt1           TAPE DRIVE FAILURE
0F78A011   0108011902 T H rmt1           RECOVERY LOGIC INITIATED BY DEVICE

Any ideas???

Bill Wheeler
PDM Administrator
La-Z-Boy Incorporated
(734) 242-1444 x 6170

-----Original Message-----
From: George Lesho [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 09, 2002 1:41 PM
To: [EMAIL PROTECTED]
Subject: Re: Tape Drive Failures


Perhaps if y ou included some representitive samples of the errors so the
SCSI error codes there is some hope of helping
you with the problem. Pull some from your O/S errpt and TSM actl. Cheers

George Lesho
AFC Enterprises
Storage/System Admin





Bill Wheeler <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/09/2002
10:20:52 AM

Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by:  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


To:   [EMAIL PROTECTED]
cc:    (bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Tape Drive Failures


Hello *SMers,

        Just a quick question out there for all of you.   I am currently
receiving tape drive failures when trying to check in and out tapes, also
during our nightly archive.   They have been increasing during the last few
months.  My environment is Magstar 3570, 2 drives.   I am currently running
TSM 4.1.2.0 on AIX 4.3.3.   I have been cleaning the drives regularly, but
am not sure if I should be IBM involved or not.  One of the main problems
is
that when the drive gets the error, the drive does not reset.  It could be
the tapes causing the problems, but the drives are still not resetting.
Just yesterday someone was checking in tapes and loaded the wrong one, but
the drive failed due wrong tape being mounted.  Then the drive did not
reset
itself.   Is there anything that I can do without calling IBM to see if I
can get this fixed?


Thanks in advance,

Bill Wheeler
PDM Administrator
La-Z-Boy Incorporated
(734) 242-1444 x 6170

Reply via email to