When I see this we have had read errors on the tape.
My method of resolution is to mark the tape read only, then
do a move data to get the data off the tape.

   update vol volumename123 acc=reado
   move data volumename123

This gets all the data off the tape.  Then I check it out,
delete the volume with discard data.  If the tape had many
read or write errors, I try to send it back for warantee replacement :)

   checkout libv mylibrary volumename123 checkl=n

Or if it only has a few, re-label and retry using it again as scratch.

  label libv mylibrary search=bulk labels=b overwrite=yes checkin=scratch

Sometimes it seems 'healed' then (no good reason, it just seems to work).

If this is happening to many volumes, check the drives for errors,
make sure you clean the drives regularly (whether they need it or not),
and use other good data hygene techniques as you find them.

I have a 3583 LTO library.  ... Lots of Luck.

-----Original Message-----
From: bkupmstr [mailto:bkupmstr AT YAHOO DOT COM]
Sent: Friday, September 05, 2003 9:29 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: tape going unavail


Has anyone seen a scenario like this.
 TSM server 5.1.0 running on aix 4.3.3
 Standalone 3590E tape rive defined to a manual library roblib00

09/04/03 23:24:00 ANR8325I Dismounting volume 040337-60 minute mount
retention expired.
09/04/03   23:24:41      ANR8469E Dismount of 3590 volume 040337 from drive
RMT2
                          (/dev/rmt2) in library ROBLIB00 failed.
09/04/03   23:24:41      ANR1410W Access mode for volume 040337 now set to
                          "unavailable".
09/04/03   23:24:41      ANR8475I Dismount of volume 040337 failed. It may
still be
                          in the drive.


It actually dismounts teh tape from thedrive but still puts it into
unavailable mode???????


---------------------------------
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software