ADSM-L

Re: Errors on tapepool volume

1998-11-25 17:34:05
Subject: Re: Errors on tapepool volume
From: "Thomas A. La Porte" <tlaporte AT ANIM.DREAMWORKS DOT COM>
Date: Wed, 25 Nov 1998 14:34:05 -0800
At this point I would suspect the drive(s). If ADSM is unable to
read the label, my instinct is that either (a) the label was
written while the drive was bad, or (b) the drive is still bad,
and thus is unable to read the label for ADSM.

As far as I know, it is impossible to non-destructively relabel
the tape. It would seem possible, given that you are only dealing
with the leader blocks, and not the data, but it can't be done,
at least not in a supported manner.

Before restoring from a copy pool, I would ensure that the drive
and library microcode is up to date, and that the drives are,
indeed, working properly.

 -- Tom

On Wed, 25 Nov 1998, Kevin Corning-Hyman wrote:

>Hello,
>
>Being relatively new to ADSM, I have already spent too much time on this
>problem.  This week we had a problem with our 3494 tape library and 3590
>drives (2).  The 3494 reported that one of the drives had failed.  By the
>time the IBM tech came onsite there was a message on the 3494 console that
>the other drive had failed.  ADSM could not access these drives.  After
>monkeying around, powering everything off, checking drives, it was
>determined that the library was ok and the drives were ok.  After
>everything came back up ADSM saw the drives again.
>
>Now for the problem that may or may not be related to this.  I have a
>volume (A00202) designated to the tapepool that ADSM can't check in.  It
>should have never been checked out, but it was.  The specific error
>(ANR8353E) tells me that I should run DSMLABEL to relabel to volume.  At
>this point ADSM makes the volume "unavailable."   I have also received an
>ANR8387I message trying to move data from the volume.  Should I run
>DSMLABEL?  Can this be done without losing data?  Should I try to restore
>the volume from the copypool using RESTORE VOLUME?  I have included a part
>of the activity log below:
>
>11/25/98 10:36:27     ANR1199I Removable volume A00026 is required for
>audit process.
>11/25/98 10:36:27     ANR1199I Removable volume A00202 is required for
>audit process.
>11/25/98 10:36:27     ANR8324I 3590 volume A00026 is expected to be mounted
>(R/O).
>11/25/98 10:36:27     ANR8324I 3590 volume A00202 is expected to be mounted
> (R/W).
>11/25/98 10:36:27     ANR0984I Process 45 for AUDIT VOLUME (INSPECT ONLY)
>
>                       started in the BACKGROUND at 10:36:27.
>
>11/25/98 10:36:27     ANR2313I Audit Volume (Inspect Only) process started
>for volume A00202 (process ID 45).
>11/25/98 10:37:35     ANR8337I 3590 volume A00026 mounted in drive
>DR1(/dev/rmt1).
>11/25/98 10:37:56     ANR8308I 013: 3590 volume A00202 is required for use
>in
>                       library ADSM-TAPE; CHECKIN LIBVOLUME required within
>60 minutes.
>11/25/98 10:38:56     ANR8308I 013: 3590 volume A00202 is required for use
>in
>                       library ADSM-TAPE; CHECKIN LIBVOLUME required within
>59 minutes.
>11/25/98 10:38:58     ANR0984I Process 46 for CHECKIN LIBVOLUME started in
>the
>                       BACKGROUND at 10:38:58.
>
>11/25/98 10:38:58     ANR8422I CHECKIN LIBVOLUME: Operation for library
>
>                       ADSM-TAPE started as process 46.
>
>11/25/98 10:38:58     ANR0609I CHECKIN LIBVOLUME started as process 46.
>
>11/25/98 10:39:00     ANR8319I 014: Insert 3590 volume A00202 R/W into
>library
>                       ADSM-TAPE within 60 minute(s).
>
>11/25/98 10:39:30     ANR8335I 014: Verifying label of 3590 volume A00202
>in drive DR0 (/dev/rmt0).
>11/25/98 10:39:32     ANR8353E 014: I/O error reading label of volume in
>drive DR0 (/dev/rmt0).
>
>Any and all help will be appreciated.  Thank you.
>
>Kevin Corning-Hyman
>Info Center Consultant
>Munson Medical Center
>kcorning AT mhc DOT net
>
<Prev in Thread] Current Thread [Next in Thread>