I had a similar experience.. What would happen is the 3494 library(robot) would do it's job, and after a million + mounts a month a screw would come lose in the back of the library causing the drive to move back say .09823650124650418751 of an inch. (CE explained that one, said I wasn't the only one experiencing) This would cause the library robot when grabbing a dismounted tape - to call a dismount failed message. When the tape was really dismounted.. I had this 1 particular volume always popping up in the actlog around the time the "No Drives Available" message would appear.
It seems when the volume in question failed to dismount(the first time) the status/category changed(From the Library's perspective) I queried the Library for the tape and it came back with category # it shouldn't have, TSM thought it was a scratch when it really was a private.(Or vise versa, depending on the action being performed with the tape) Resolution: 2 Gallons of Lock tite and a couple railroad ties to shore up the back of the tape drive.... Not a TSM problem, misunderstanding of a weird situation. Pager has been sleeping like a log ever since I figured that one out... Gabriel C. Wiley ADSM/TSM Administrator AIX Support Phone 1-614-308-6709 Pager 1-877-489-2867 Fax 1-614-308-6637 Cell 1-740-972-6441 Siempre Hay Esperanza Allen Barth <allen_barth@SCUD To: [EMAIL PROTECTED] DER.COM> cc: Sent by: "ADSM: Subject: Re: No drives available - UPDATE Dist Stor Manager" <[EMAIL PROTECTED] .EDU> 03/12/2002 06:04 PM Please respond to "ADSM: Dist Stor Manager" Actually it's a little worse.... I found the hard way that the tapes which been emptied by move data or reclamation also needed to be deleted. TSM somehow seems to record the tape density/capacity when the tape is added to a stg pool. I had, um, several tapes that would fail mounts and generate a 'No tape drives available' message. It took a little while to piece what was going on, but after I deleted the vols and checked them back in they have all been quite useable. Al Barth Joe Faracchio <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 03/07/02 12:00 PM Please respond to Joe Faracchio To: [EMAIL PROTECTED] cc: Subject: Re: No drives available - UPDATE If its the same or similiar problem I had in converting from a 3466-C00 (tsm 3) to a 3466-C01(tsm 4) but using the same 3494/3590s then its because your system thinks the tapes are ONLY capatible in READ/ONLY mount modes. Even though you are mounting a tape for RESTORE if you look closely you will find the tapes are being mounted R/W. If the system sees a tape R/O it will mount it R/O and this bypasses the problem. The system thinks the tapes were originally written using heads (B1/E1/whatever) that are write-incompatible with your 'current/new' (even though the same) drives. IBM offered the above workaround but I know of no APAR to adddress it with a fix. I think TIVOLI doesn't understand IBM's religious belief in upward compatibility and so TSM 4 doesn't have a bridge from ADSM/TSM 3. If I'm right then your works cut out for you. You have to move data or reclamate all FILLING tapes and make all FULL tapes READ/ONLY until they are re-cycled. that's what I had to do. SIGH. hope this helps. ... joe.f. Joseph A Faracchio, Systems Programmer, UC Berkeley Private mail on any topic should be directed to : [EMAIL PROTECTED] (510)642-7638 (w) (209)483-JOEF (M) 5633 2 weeks left!!! On Thu, 7 Mar 2002, Jason Morgan wrote: > Earlier I posted a question regarding a migration problem I was having > while trying to restore to a 3590 with a tape stacker. > > I was encountering a no drives availabel while trying to restore. > > To overcome this problem, I had to mark the volume as READ ONLY. The > restore went throught without a hitch. > > Can anyone tell me what TSM does differently on a restore when a tape is > marked as READ ONLY instead of READ WRITE ? > > I think it has something to do with mount points. > > Thanks in advance. > > Jason > ******************* PLEASE NOTE ******************* This message, along with any attachments, may be confidential or legally privileged. It is intended only for the named person(s), who is/are the only authorized recipients. If this message has reached you in error, kindly destroy it without review and notify the sender immediately. Thank you for your help. **********************************************************