If they aren't assigned to a storage pool, there is no valid data on
them, so no recovery is necessary.

When TSM has a problem completing a mount, it doesn't know whether the
problem is with the tape or the drive.
So it marks the tape private to prevent a repetitive failure on the next
mount, in case the problem is indeed the tape itself.

Since you know the problem was with the drive (i.e., it had no power!)
and not the tape, all you need to do is mark it as Scratch again:

update libv yourlibname 223AHV status=scratch

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
PEEK, CHRISTOPHER
Sent: Tuesday, December 28, 2004 8:32 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Tape Recovery Questions


We had an UPS failure in the data center.  When the UPS failed, it
immediately disconnected power to all devices in the data center.  At
the time of the failure, there were 3 tapes being written to in our 3583
library.  After the UPS was repaired, I brought everything back online.
TSM marked the three tapes as having an I/O error (no shock here) and
wrote the following type message to the log for each tape:

12/17/04 05:07:29     ANR8355E I/O error reading label for volume 223AHV
in dri 
                       ve DRIVE2 (/dev/rmt2). (SESSION: 383, PROCESS:
18)       
12/17/04 05:08:01     ANR8778W Scratch volume 223AHV changed to Private
Status  
                       to prevent re-access. (SESSION: 383, PROCESS: 18)


Now, my question is how to recover from this.  I have tried to identify
what was on the tapes so that I may recover it from other tape pools, or
maybe discard it if not necessary to rebuild it.  However, the tapes are
not assigned to any storage pools so the "query volume" and "query
content" commands are not working.  

Any suggestions on what to do next to identify what is on the tapes?