Allan,
I have the same configuration as you :
NT 4.0 STK9714 4xDLT7000 on 2xAHA2944UW Differential, and ADSM NT V3.1
PTF2.
I am on pilote phase. I note this problem last night. I perform a full
IPL of STK9714 (Server Off), then I turn off the server. I have done
some test. For the moment it seems to works. I have to check tomorow.
One question, I didn't check it yet. Have you this problem with PTF1 ?

> g          GE Medical Systems 
> __________________________________
> Eric Boireau                                                GITS
> Unix / NT  System Engineer
> 
> GE Medical Systems S.A
> 283, rue de la Minière 
> 78533 BUC Cedex France
> Tél: (33) 01 30 70 39 51,  DC: 8*644 3951
> Fax: (33) 01 30 70 39 20, DC: 8*644 3920
> mailto:Eric.Boireau AT med.ge DOT com
> 
> Salutations / Best Regards
> 
> 
> 
> 
> ----------
> From:         Allan Kelly[SMTP:KellyJA AT BCRAIL DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         jeudi 9 avril 1998 21:30
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: STK9714 library, DLT7000, NT4.0 ADSM 3.1.0.2 problem
> 
> Brad,
> 
> Thanks for your reply.  We did have a bad cable and the tech fixed it
> but maybe it is still bad - I will get a replacement and try it.  Also
> we are using BusLogic BT-958D Wide PCI SCSI adapters (one to the
> STK9714
> and a DLT7000, another to two DLT7000 drives) and we have begun to
> wonder whether we should use other adapters.
> 
> All further suggestions are welcome!
> 
> Thanks.
> 
> Allan.
> 
> 
> > -----Original Message-----
> > From: Brad Wallace [SMTP:BradleyWallace AT COMPUSERVE DOT COM]
> > Sent: Thursday, April 09, 1998 11:03 AM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      Re: STK9714 library, DLT7000, NT4.0 ADSM 3.1.0.2
> problem
> >
> > Allan,
> >         We have an STK9714 with DLT7000 hooked up to an IBM RS6000
> > under
> > AIX.  We had the problems that Kelly was talking about (and more)
> with
> > the
> > library.  After weeks of trouble shooting and parts swapping, the
> > cause
> > turned out to be the cable going from the SCSI card in the CPU to
> the
> > robot.
> >
> > We also had a bad drive that was causing read errors on the tapes.
> >
> > Check the activity log ("q ac" command) and see if you can track the
> > error
> > to a specific drive.  Since the error is on the changer, and you
> don't
> > see
> > any tapes left in the drive, it probably won't be a bad drive.
> Also,
> > since
> > the error is SCSI related I'd bet on the cables being bad.  Have
> your
> > service tech. run a new set of cables to the library.  Just run'em
> > accross
> > the floor temporarily.  And see if you get through a day without the
> > error.
> >  At the same time you're doing that, you may want to have your NT
> > server
> > tech check the SCSI card, to be sure that isn't the problem.
> >
> > Brad Wallace
> > UNIX Systems Administrator
> > The Guardian Life Insurance Co.
>