I have checked the drives frequently during my testing with these
problems and there were never any tapes in the drives (although we did
once get the spurious message that there were (CC=315, etc.)  Also the
system takes a very long time to do anything once the CC=205 messages
start coming out.  It is as if something is timing out or as if ther
were a "missing interrupt" from mainframe days.  We are still at a loss
and are stuck.

Thanks in advance for any help.

Allan.


> -----Original Message-----
> From: Kelly J. Lipp [SMTP:lipp AT STORSOL DOT COM]
> Sent: Tuesday, April 07, 1998 7:28 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: STK9714 library, DLT7000, NT4.0 ADSM 3.1.0.2 problem
>
> This looks like the famous "cartridge stuck in drive" error.  You
> might
> look and see if there is a cartridge in the drive.  We've seen lots of
> this
> this week on those robots for some reason.  ADSM thinks the drive is
> unloaded but it isn't and it comes along and tries to hang another
> tape on
> that drive and can't.  Thus the error message.
>
> I think there were some bad drives as well as a firmware fix that
> might
> help.
>
> Kelly
>
> -----Original Message-----
> From:   Allan Kelly [SMTP:KellyJA AT BCRAIL DOT COM]
> Sent:   Tuesday, April 07, 1998 1:27 PM
> To:     ADSM-L AT VM.MARIST DOT EDU
> Subject:        STK9714 library, DLT7000, NT4.0 ADSM 3.1.0.2 problem
>
> We are new to ADSM-land: just now implementing ADSM Server 3.1.0.2 on
> an
> Intel (Pentium II) based server running NT4.0 using an STK9714 library
> with 3 DLT7000 drives.
>
> We have a problem: several operations seem to "hang up" and eventually
> time out - e.g., sometimes migrating from the disk pool to a tape pool
> or moving the data from a tape volume back to the disk pool ("move
> data
> 000027 stg=backuppool").
>
> We also get messages:
>
> 04/07/1998 10:54:04 ANR8300E I/O error on library DLTLIB (OP=8401C058,
> CC=304, KEY=04, ASC=40, ASCQ=02,
> SENSE=70.00.04.00.00.00.00.0C.00.00.00.00.40.02.00.00.00.00.00.00.,
> Description=Changer failure).  Refer to Appendix B in the 'Messages'
> manual for recommended action.
> 04/07/1998 10:54:04 ANR1404W Scratch volume mount request denied -
> mount
> failed.
>
>
> When I looked in Appendix B, I did not find these ASC/ASCQ values -
> perhaps I'm looking at the wrong place?
>
> 04/02/1998 15:45:00 ANR8302E I/O error on drive DRIVE1 (MT2.0.0.0)
> (OP=READ, CC=205, KEY=FF, ASC=FF, ASCQ=FF, SENSE=**NONE**,
> Description=SCSI adapter failure).  Refer to Appendix B in the
> 'Messages' manual for recommended action.
>
> We checked all connections, hardware setup, etc. and found nothing
> wrong.
>
> We can use any help or insight you can offer!
>
> Thanks.
>
> Allan Kelly
> BC Rail Ltd.