Usually an OFFL error is a problem dismounting the tape from a drive.
Unlikely this has anything to do with DRM; probably you would have the
same problems when using the drive for any other TSM operation.
Your drive was able to READ (because it was able to verify the label),
so probably the read/write head is ok. But, it had a problem on the
dismount and removing the tape from the drive.
On the other hand, since you were able to eject the tape using another
drive, we know that the tape isn't actually STUCK in the drive.
Sometimes you'll see an OFFL error, and it's transient and doesn't
happen again. But in this case you got the same error on 2 different
tapes. So, I think you are seeing the drive issue an error message
because it is starting to have mechanical problems.
Nothing to do but call IBM and let them come and fix (or replace) it.
BTW, I have never seen a need to have the drive mount the tape and read
the label for a DRM checkout where you are using tapes with barcodes.
If you enter SET DRMCHECKLABEL NO on the admin command line, that will
tell TSM to do your DRM ejects WITHOUT mounting each tape just to read
the label. Much faster that way.
Wanda Prather
"I/O, I/O, It's all about I/O" -(me)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Andrew Ferris
Sent: Thursday, February 23, 2006 2:00 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: LTO drive error on MOVE DRMEDIA
Hi *DSM-ers,
TSM Server 5.2.3.2 on Win 2000
3584 Tape Library with 4 LTO-2 drives
It's offsite backup day and our regularly scheduled MOVE DRMEDIA *
WHERE STATE=MOUNTABLE... produced this error on one of our tapes:
02/23/2006 09:04:46 ANR6696I MOVE DRMEDIA: CHECKOUT LIBVOLUME for
volume
ICA074L2 in library 3584 starting. (SESSION:
95513,
PROCESS: 3435)
02/23/2006 09:05:00 ANR8336I Verifying label of LTO volume ICA074L2
in drive
F1R3 (mt2.0.0.4). (SESSION: 95513, PROCESS:
3435)
02/23/2006 09:05:15 ANR8942E Could not move volume ICA074L2 from
slot-element
259 to slot-element 774. (SESSION: 95513,
PROCESS: 3435)
02/23/2006 09:05:15 ANR8418E CHECKOUT LIBVOLUME: An I/O error
occurred while
accessing library 3584. (SESSION: 95513,
PROCESS: 3435)
02/23/2006 09:05:15 ANR6698E MOVE DRMEDIA: CHECKOUT LIBVOLUME for
volume
ICA074L2 in library 3584 failed. (SESSION:
95513,
PROCESS: 3435)
slot-element 259 is one of the LTO-2 drive (F1R3 to be precise) and
slot-element 774 is in the 3584's I/O station. I re-ran the MOVE DRMEDIA
command for that specific tape and it moved to the I/O station just fine
though via another LTO drive.
A quick look at the TSM admin console (dsmadmc) showed this additional
error on a subsequent DRM tape:
9:06:59 MOVE DRMEDIA: CHECKOUT LIBVOLUME for volume ICA051L2 in library
3584 starting.
ANR8302E I/O error on drive F1R3 (mt2.0.0.4) (OP=OFFL, Error Number=21,
CC=0, KEY=02, ASC=04,
ASCQ=02,~SENSE=70.00.02.00.00.00.00.1C.00.00.00.00.04.02.30.00.10.12.00.
00.00.00.20.20.20.20.20.20.20.00.00.00.00.00.00.13.00.00.00.14.FF.FF.FF.
FF.6B.8F.00.00.6C.8F.00.00.6D.8F.00.00.6E.8F.00.00.6F.8F.00.00.70.8F.00.
00.71.8F.00.00.72.8F.00.00.73.8F.00.00.74.8F.00.00.75.8F.00.00.76.8F.00.
00.77.8F.00.00,~Description=An
undetermined error has occurred). Refer to Appendix D in the 'Messages'
manual for recommended action.
So that's the same drive (F1R3). I've looked up the ANR 8302E in the
5.2 messages manual:
User Response: Ensure that the DEVICE parameter associated with the
drive was identified correctly in the DEFINE PATH command, and that the
device is currently powered on and ready. The drive or library reference
manual provided with the device usually contain tables that explain the
values of the KEY, ASC, and ASCQ fields. If the problem persists,
contact your service representative and provide the internal code values
and sense data from this message.
All four drives show as online in the 3584's IBM UltraScalable
Specialist Web page and they also show as online in TSM.
I see KEY=02 equaling "not ready" in the messages manual. ASC=04 &
ASCQ=02 are "Not ready, initializing command required"
This the first tape error I've seen so I'm a bit flummoxed as to where
to go to next. Could someone please give me a bit of advice or context
on these errors?
thanks,
Andrew Ferris
Network Support Analyst
iCAPTURE Research Centre
University of British Columbia
|
