We had many of these "bogus" I/O errors on older releases of the microcode.

We got far fewer errors on tapes WRITTEN with the older microcode being READ
with the new microcode.

And we seldom have any I/O errors on tapes WRITTEN and READ with the new
microcode.


===============================================================
Wanda Prather
Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think."
              - Scott Adams/Dilbert
===============================================================


> ----------
> From:         Carl Makin[SMTP:Carl.Makin AT ipaustralia.gov DOT au]
> Sent:         Thursday, April 16, 1998 5:38 AM
> To:   ADSM-L AT vm.marist DOT edu
> Subject:      Re[2]: Tape with write error going Read/Only
>
> > Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> (Claudia
> Masters
> > <cmaster1 AT TUELECTRIC DOT COM>) at INTERNET
>
>
> > I am using ADSM Server on NT with a STK9714 and 4
> > DLT7000s. I have not encountered any problems labeling
> > the tapes.
>
> > Recently, though, I found that there were many tapes in "filling" status
> > with a read-only access due to errors.  In all cases, I have
> successfully
> > used the MOVE DATA command to empty the tape.  I then relabeled the tape
>
> The microcode on your DLT7000's needs updating.  Apparently version "70"
> or
> later fixes this problem.
>
> We had the same problem with our 9714 and 2xDLT7000s.
>
> Contact your StorageTek rep and get them to bring out the microcode update
> tape.
>
>
> Carl.
>