I've been having some trouble with SCSI tape on some of the later
snapshots.  I decided I would try Chuck's snapshot of 1.4V he put
up on ftp.neurotica.com to make sure I still had the problem.  In 
fact, it is still there.

I've got a Vaxstation 3100 M76, 16 Mb RAM, booting off an external
Fujitsu M2266S.  I'm having no problems with SCSI disk access, and
I've put the drive through the paces, compiling the kernel a couple
of times and doing some large scale file copying with tar.

However, everytime I try to make a tape archive to TK50Z, I get
SCSI sense errors, and the process eventually gives up.  

It might be helpful to know that this machine is dual booting 
OpenVMS 7.2.  Yesterday I did a full backup, as well as some 
directory tree backups with that tape drive, using VMS BACKUP, 
and not a single error.

Here is a snipped of my boot messages, and the error code I see
when I try to create a tar archive:


scsibus0 at ncr0: 8 targets, 8 luns per target
ncr1 at vsbus0 csr 0x200c0180 vec 774 ipl 14 maskbit 0
scsibus1 at ncr1: 8 targets, 8 luns per target
smg0 at vsbus0 csr 0x200f0000 vec 104 ipl 14 maskbit 3
wsdisplay0 at smg0
wsdisplay0: screen 0-7 added (128x57, vt100 emulation)
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 targ 0 lun 0: <DEC, DSP3210S, 436D> SCSI2 0/direct fixed
sd0: 2049 MB, 3045 cyl, 16 head, 86 sec, 512 bytes/sect x 4197520 sectors
sd1 at scsibus0 targ 2 lun 0: <DEC, RZ25     (C) DEC, 0900> SCSI2 0/direct fixed
sd1: 406 MB, 1476 cyl, 9 head, 62 sec, 512 bytes/sect x 832527 sectors
scsibus1: waiting 2 seconds for devices to settle...
sd2 at scsibus1 targ 2 lun 0: <FUJITSU, M2266S-512, 001F> SCSI1 0/direct fixed
sd2: 1030 MB, 1658 cyl, 15 head, 84 sec, 512 bytes/sect x 2111018 sectors
st0 at scsibus1 targ 5 lun 0: <, , > SCSI1 1/sequential removable
st0: rogue, drive empty
boot device: sd2
root on sd2a dumps on sd2b
Clock has gained 19722 days - CHECK AND RESET THE DATE.
root file system type: ffs
swapctl: adding /dev/sd2b as swap device at priority 0
Automatic boot in progress: starting file system checks.
/dev/rsd2a: file system is clean; not checking
/dev/rsd2d: file system is clean; not checking

inforumvax# cd /
inforumvax# tar cvf /dev/st0 /etc
st0(ncr1:5:0):  Check Condition on CDB: 0x1e 00 00 00 01 00
    SENSE KEY:  Illegal Request
 COMMAND INFO:  117440512 (0x7000000)
     ASC/ASCQ:  No Additional Sense Information

tar: Removing leading / from absolute path names in the archive.Feb 28 21:04:15 inforumvax /netbsd: st0(ncr1:5:0):  Check Condition on CDB: 0x1e 00 00 00 01 00

Feb 28 21:04:16 inforumvax /netbsd:     SENSE KEY:  Illegal Request
Feb 28 21:04:16 inforumvax /netbsd:  COMMAND INFO:  117440512 (0x7000000)
Feb 28 21:04:16 inforumvax /netbsd:      ASC/ASCQ:  No Additional Sense Information
Feb 28 21:04:16 inforumvax /netbsd: 
etc/
etc/disklabels/
etc/kerberosIV/
    .
    .
etc/profile
etc/protocols
etc/pwst0(ncr1:5:0): d Check Condition on CDB: 0x1e. 00d 00b 00 00 00et
    SENSE KEY:  Illegal Requestc
 COMMAND INFO:  117440512 (0x7000000)/
     ASC/ASCQ:  No Additional Sense Informationr
bootd.conf
etc/rc.conf
etc/wscons.conf
etc/resolv.conf
etc/ifconfig.le0
etc/fstab
inforumvax# Feb 28 21:04:44 inforumvax /netbsd: st0(ncr1:5:0):  Check Condition on CDB: 0x1e 00 00 00 00 00
Feb 28 21:04:44 inforumvax /netbsd:     SENSE KEY:  Illegal Request
Feb 28 21:04:44 inforumvax /netbsd:  COMMAND INFO:  117440512 (0x7000000)
Feb 28 21:04:44 inforumvax /netbsd:      ASC/ASCQ:  No Additional Sense Information
Feb 28 21:04:44 inforumvax /netbsd: 

inforumvax# 

(That was where it quit.)

The first time I saw this, I thought it might have been a cabling problem,
or problem with bad power supply, but I've tried several cables and two
different Vaxstations (also an M30) and the error is very predictable.

Is the TK50Z external tape drive considered 'supported' with this
distribution?

Doug