From:	CSBVAX::CSBVAX::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  3-DEC-1988 18:37
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Multi-Volume Backup Problem with V5.0-n/TK-50/MicroVAX


Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Thu,  1 DEC 88 08:42:09 PDT
Date: Thu, 1 Dec 88 07:59:25 PST
From: Leonard Schwer <SCHWER@KL.SRI.COM>
Subject: Multi-Volume Backup Problem with V5.0-n/TK-50/MicroVAX
To: Info-VAX@KL.SRI.COM
cc: micro2.schwer@crvax.sri.com, micro2.kempf@crvax.sri.com
Message-ID: <12450966079.21.SCHWER@KL.SRI.COM>

 INFO-VAXers--

I've had problems performing multiple volume BACKUPs to a TK-50
on my MicroVAX since upgrading to V5.0-n. I've had Colorado CSC
working on this problem since 1 November. The symptom is that
BACKUP completes the first volume and requests, thru OPCOM, that
a second volume be mounted. After mounting the second volume and
REPLYing/TO= the BACKUP process just sits there in LEF forever,
as if it never got the OPCOM message. After aborting the BACKUP
job the tape drive is inaccessable, e.g. MOUNT and INIT generate
no responses. The machine must be shutdown and rebooted to again
access the TK-50 tape drive. 

CSC got a few more similar calls and was able to track the
problem down to the TK-50 controller board in the MicroVAX. If
the controller software version is greater than #3 there is no
problem; I was at #3 and recently upgrade to #5 which solved my
problem. An easy was to find the software version number is to
perform an analze/error (and probably put the result in a file):

          $ analyze/error/include=mua0/output=tape.err

Then search near the bottom of this *large* (>1000 blocks) file
for the string CONTROLLER SOFTWARE VERSION which will be followed
by #N indicating the version number.

                     --Len Schwer  Schwer@KL.SRI.COM
-------