ADSM-L

Re: Storage media inaccessible in a 3494 library

1999-11-18 03:32:22
Subject: Re: Storage media inaccessible in a 3494 library
From: Reinhard Mersch <mersch AT UNI-MUENSTER DOT DE>
Date: Thu, 18 Nov 1999 09:32:22 +0100
Amazingly - I have gone through that trouble just yesterday.

We had three 3590B drives upgraded to 3590E and one new 3590E drive
installed. I forgot to delete and redefine the drives. From the ADSM
server point of view, the old drives were still B-type, and volumes
initially written on them were refused to be mounted (writable) on E-type
drives, and vice versa!

The solution: Delete the drives and define them again. For the volumes
making trouble: set their access to READONLY and start MOVE DATA for them
(beeing READONLY, ADSM is now willing to mount them).

To all the ADSM guys out there having 3590E-drives which where upgraded
from 3590B: Did you delete and redefine them? Otherwise you will run into
the same problems as soon as you add a new (or redefine an existing)
3590E drive!

Of couse, I do not know, whether this is your problem, but I give it a
good chance. Hope it helps.

Forrester, Benjamin S. writes:
 > I am trying to move data from some suspect volumes in our library, but the
 > move datas consistently fail. The accounting log gives me the following
 > errors:
 >
 > 11/17/99   09:55:11  ANR8447E No drives are currently available in library
 >                       LIB3494A.
 > 11/17/99   09:55:11  ANR1401W Mount request denied for volume A00088 - mount
 >                       failed.
 > 11/17/99   09:56:25  ANR1144W Move data process terminated for volume A00088
 > -
 >                       storage media inaccessible.
 > 11/17/99   09:56:25  ANR0985I Process 126 for MOVE DATA running in the
 >                       BACKGROUND completed with completion state FAILURE at
 >                       09:56:25.
 > The problem is that there are available 3590E drives available when I issue
 > the command, and issuing the move data command on a different volume works
 > perfectly. Has anyone seen this before or have any ideas as to what is
 > wrong? Is the data or the cart so corrupt that it cannot be mounted? Any
 > comments or suggestions would be very helpful. We are at ADSM level 3.1.2.40
 > and have the latest microcode for the 3590E drives. The following
 > information is the detailed information on the volume I was trying to move.
 >
 > Thanks,
 >
 > Ben Forrester
 > System Administrator
 > University of Missouri - Columbia
 >
 >                    Volume Name: A00088
 >              Storage Pool Name: BACKUPCART
 >              Device Class Name: 3590
 >        Estimated Capacity (MB): 10,240.0
 >                       Pct Util: 15.6
 >                  Volume Status: Filling
 >                         Access: Read/Write
 >         Pct. Reclaimable Space: 29.9
 >                Scratch Volume?: Yes
 >                In Error State?: No
 >       Number of Writable Sides: 1
 >        Number of Times Mounted: 13
 >              Write Pass Number: 1
 >      Approx. Date Last Written: 10/07/99   05:18:23
 >         Approx. Date Last Read: 10/08/99   10:03:43
 >            Date Became Pending:
 >         Number of Write Errors: 0
 >          Number of Read Errors: 0
 >                Volume Location:
 > Last Update by (administrator): DILLB
 >          Last Update Date/Time: 11/16/99   23:49:28

--
Reinhard Mersch                        Westfaelische Wilhelms-Universitaet
Reinhard Mersch                        Westfaelische Wilhelms-Universitaet
Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum
Roentgenstrasse 9-13, D-48149 Muenster, Germany      Tel: +49(251)83-31583
E-Mail: mersch AT uni-muenster DOT de                       Fax: 
+49(251)83-31653