ADSM-L

Re: [ADSM-L] ANR8302E I/O error

2010-02-26 12:09:31
Subject: Re: [ADSM-L] ANR8302E I/O error
From: Mario Behring <mariobehring AT YAHOO DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 26 Feb 2010 09:08:27 -0800
Hi Richard,

Firmware is the same on both drives....97F2
Element number is correctly referenced on both drives also.....256 and 257.

Mario






________________________________
From: Richard Sims <rbs AT BU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Sent: Fri, February 26, 2010 1:53:17 PM
Subject: Re: ANR8302E I/O error

On Feb 26, 2010, at 11:33 AM, Mario Behring wrote:

> Hi list,
>
> I am getting the following error on one of my drives when performing a MOVE 
> DATA:
>
> ANR8302E I/O error on drive DRIVE01 (MT4.0.0.3) with
>  volume  (OP=OFFL, Error Number=1, CC=0, rc = 1, KEY=05,
>  ASC=53, ASCQ=02, SENSE=70.00.05.00.00.00.00.58.00.00.00.-
>  00.53.02.30.00.2C.19.00.00.00.01.32.30.30.30.32.36.4C.00-
>  .00.00.00.00.04.00.00.00.00.04.81.1B.60.00.00.00.00.00.0-
>  5.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.00.00.00.00.00.00.00.00-
>  .30.38.39.4C.31.31.33.39.37, Description=An undetermined
>  error has occurred).  Refer to Appendix C in the
>  'Messages' manual for recommended action. (SESSION: 1,
>  PROCESS: 2)

Did you pursue the codes in the Messages manual?  They tell of a llegal request 
/ medium removal prevented condition.  This may resolve to a device driver 
issue, as previously outlined in postings on this library.  If one tape drive 
is working fine but not the other, check the firmware levels on them, where the 
problem one may well be at a lower level.  A firmware defect can result in 
timing issues, such that a tape dismount may be rejected as too early in a 
mechanical/electronic process.  Also double-check element numbers to assure 
that the drive is being addressed correctly.  You may want to exercise the 
drive via NTUTIL or the like, to verify functionality.

    Richard Sims