Xref: utzoo comp.unix.ultrix:1153 comp.sys.dec:1482 comp.periphs:1885 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!ames!purdue!gatech!ncsuvx!mcnc!rti!shaddock From: shaddock@rti.UUCP (Mike Shaddock) Newsgroups: comp.unix.ultrix,comp.sys.dec,comp.periphs Subject: Exabyte vs. Ultrix 3.1 Message-ID: <3064@rti.UUCP> Date: 7 Jul 89 01:51:39 GMT Reply-To: shaddock@rti.UUCP (Mike Shaddock) Organization: Research Triangle Institute, RTP, NC Lines: 39 We have a DILOG SQ703A tape controller with an Exabyte 8mm tape drive (prom 4$22) attached to VAXstation II running Ultrix 3.1. Under Ultrix 2.2, the Exabyte worked perfectly, but since we upgraded to Ultrix 3.x it has not worked very well. It understands commands like "mt -f /dev/rmt1h rewind" or "mt -f /dev/rmt1h offline", but dd, tar, and dump all fail in a moderately strange way. Tar will begin to write on the tape, but then will come back with: /dev/rmt1h: Error 0 tar: Archive 1 write error Dd and dump also report "Error 0" and complain about write errors. Our current kernel config file has adapter uba0 at nexus ? controller klesiu0 at uba0 controller uq1 at klesiu0 csr 0174500 vector uqintr tape tms0 at uq1 drive 0 controller klesiu1 at uba0 controller uq2 at klesiu1 csr 0160404 vector uqintr tape tms1 at uq2 drive 0 controller uda0 at uba0 controller uq0 at uda0 csr 0172150 vector uqintr disk ra0 at uq0 drive 0 disk ra1 at uq0 drive 1 disk ra2 at uq0 drive 2 device qv0 at uba0 csr 0177200 flags 0x0f vector qvkint qvvint device qe0 at uba0 csr 0174440 vector qeintr device dz0 at uba0 csr 0160100 flags 0xff vector dzrint dzxint in the relevant devices section. Has anyone else out there seen this problem, and if so, do you have a fix? -- Mike Shaddock {decvax,seismo,ihnp4,philabs}!mcnc!rti!shaddock shaddock@rti.rti.org "You're in a twisty maze of sendmail rules, all obscure."