ADSM-L

Re: ANR8302E error on drive

2003-02-25 07:13:30
Subject: Re: ANR8302E error on drive
From: Farren Minns <fminns AT WILEY.CO DOT UK>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 25 Feb 2003 11:45:06 +0000
We had a similar problem recently with one of our 3590 drives. In the end,
it turned out of the little brush that cleans the heads in the drive was
all but knackered. We had it replaced and it was fine again.

I would say it's most likely a drive problem of some sort rather then TSM
releated. As Rick says, the errors are persistent, TSM will set the drive
off-line just in case.

Farren

John Wiley & Sons Ltd



Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:        ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:        Re: ANR8302E error on drive


Hi,

If Tivoli discovers 'persistent' errors working with a drive, it will take
the drive offline, so it cannot 'accidentally' operate the drive for a
backup action.

I'd check to see if this happens with the same tape - that might indicate
that the tape is bad. I'm no expert on all those errorcodes (there might be
something in one of the manuals), but if the error occurs with another
tape,
there's probably something wrong with the drive. If the drive is in a
library, you could check the library's display (if it has one) to seen if
there is something there that might help you determine the exact nature of
the error.

Kind regards,

Rick

-----Oorspronkelijk bericht-----
Van: Sylvia Nergard [mailto:sylvianer AT NO.IBM DOT COM]
Verzonden: 25 februari 2003 12:03
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: ANR8302E error on drive


Does this indicate a hardware error?

ANR8302E I/O error on drive MT1.0.0.2 (mt1.0.0.2)
(OP=READ, Error Number=1117, CC=305, KEY=00, ASC=00,
ASCQ=00,
SENSE=70.00.00.00.00.00.00.0E.00.00.00.00.00.00-
.00.00.00.00.00.00.00.00., Description=Drive
failure).
Refer to Appendix D in the 'Messages' manual for
recommended action.
ANR8792E Unrecoverable drive failures on drive MT1.0.0.2
(mt1.0.0.2); drive is now taken offline.

This has happend twice, when I set the drive online again it works.
Is it really a hardware error, or could it be something else that makes TSM
to set this drive offline?


Regards

Sylvia Nergård




<Prev in Thread] Current Thread [Next in Thread>