SUMMARY: DLT tape drive install help needed

From: <ASIMEONE_at_iga.com>
Date: Mon, 24 Feb 1997 14:25:11 -0500 (EST)

Hello,

Thanks for replies from...

alan_at_nabeth.cxo.dec.com
robert_at_digi-data.com
pirie_at_diamond.cfas.washington.edu

The problem was installing my tlz7l-da tape drive.

It was suggested from the above people, I had a SCSI ID conflict,
plus other config problems such as not rebuilding the kernel for the
new scsi card. Since this was my first time installing this
kind of device, I wasn't sure what scsi devices I was suppose to
see at console mode. It originally had about 14 devices configured
for the tape drive at console mode. After fixing everything as outlined
below, I ended up with just 2 devices for the tape drive, which was
jkb101 and mkb100.

I booted genvmunix to find out what I would have to configure into
the new kernel. I ended up adding the following...

bus psiop1 at pci0 slot 12 vector psiopintr
controller scsi1 at psiop1 slot 0
device tape tz9 at scsi1 drive 72


I also had to change the SCSI id on the tape drive itself. I found
this out by disconnecting every device on the system except for the
tape loader. I still had a scsi id conflict after doing this. After
changing the scsi id, all was well with the tape drive.

thanks for the time and help from the people named above.

original question follows

Allan

_____________________________________________

Hi,

I'm trying to install a tzl7 DLT tape drive with a 12 mag loader.
The system I'm trying to install it on is a DEC2000 AXP
system running DU 3.2c.

I installed a scsi card which comes up as pkb0.
I have the scsi addresses on the tape drive set to
the default settings which should be 0.

If I do a show dev at the console prompt it shows (from
memory as the system is up now)....


jkb1
jkb101
jkb102
jkb103
.
.
.
mkb0
mkb100
mkb200
.
.
.

Is the jkb numbers correct? or should they be jkb1, jkb100, jkb200
and so on? I don't think anything can be conflicting as it is on its own
scsi card.

next I go into scu and do show edt

here's the output...

scu> show edt
CAM Equipment Device Table (EDT) Information:

    Bus: 0, Target: 0, Lun: 0, Device Type: Direct Access
    Bus: 0, Target: 0, Lun: 1, Device Type: (not present)
    Bus: 0, Target: 0, Lun: 2, Device Type: (not present)
    Bus: 0, Target: 0, Lun: 3, Device Type: (not present)
    Bus: 0, Target: 0, Lun: 4, Device Type: (not present)
    Bus: 0, Target: 0, Lun: 5, Device Type: (not present)
    Bus: 0, Target: 0, Lun: 6, Device Type: (not present)
    Bus: 0, Target: 0, Lun: 7, Device Type: (not present)
    Bus: 0, Target: 1, Lun: 0, Device Type: Sequential Access
    Bus: 0, Target: 1, Lun: 1, Device Type: (not present)
    Bus: 0, Target: 1, Lun: 2, Device Type: (not present)
    Bus: 0, Target: 1, Lun: 3, Device Type: (not present)
    Bus: 0, Target: 1, Lun: 4, Device Type: (not present)
    Bus: 0, Target: 1, Lun: 5, Device Type: (not present)
    Bus: 0, Target: 1, Lun: 6, Device Type: (not present)
    Bus: 0, Target: 1, Lun: 7, Device Type: (not present)
    Bus: 0, Target: 2, Lun: 0, Device Type: Direct Access
    Bus: 0, Target: 2, Lun: 1, Device Type: (not present)
    Bus: 0, Target: 2, Lun: 2, Device Type: (not present)
    Bus: 0, Target: 2, Lun: 3, Device Type: (not present)
    Bus: 0, Target: 2, Lun: 4, Device Type: (not present)
    Bus: 0, Target: 2, Lun: 5, Device Type: (not present)
    Bus: 0, Target: 2, Lun: 6, Device Type: (not present)
    Bus: 0, Target: 2, Lun: 7, Device Type: (not present)
    Bus: 0, Target: 3, Lun: 0, Device Type: Direct Access
    Bus: 0, Target: 3, Lun: 1, Device Type: (not present)
    Bus: 0, Target: 3, Lun: 2, Device Type: (not present)
    Bus: 0, Target: 3, Lun: 3, Device Type: (not present)
    Bus: 0, Target: 3, Lun: 4, Device Type: (not present)
    Bus: 0, Target: 3, Lun: 5, Device Type: (not present)
    Bus: 0, Target: 3, Lun: 6, Device Type: (not present)
    Bus: 0, Target: 3, Lun: 7, Device Type: (not present)
    Bus: 0, Target: 4, Lun: 0, Device Type: Read-Only Direct Access
    Bus: 0, Target: 4, Lun: 1, Device Type: (not present)
    Bus: 0, Target: 4, Lun: 2, Device Type: (not present)
    Bus: 0, Target: 4, Lun: 3, Device Type: (not present)
    Bus: 0, Target: 4, Lun: 4, Device Type: (not present)
    Bus: 0, Target: 4, Lun: 5, Device Type: (not present)
    Bus: 0, Target: 4, Lun: 6, Device Type: (not present)
    Bus: 0, Target: 4, Lun: 7, Device Type: (not present)
    Bus: 0, Target: 5, Lun: 0, Device Type: Direct Access
    Bus: 0, Target: 5, Lun: 1, Device Type: (not present)
    Bus: 0, Target: 5, Lun: 2, Device Type: (not present)
    Bus: 0, Target: 5, Lun: 3, Device Type: (not present)
    Bus: 0, Target: 5, Lun: 4, Device Type: (not present)
    Bus: 0, Target: 5, Lun: 5, Device Type: (not present)
    Bus: 0, Target: 5, Lun: 6, Device Type: (not present)
    Bus: 0, Target: 5, Lun: 7, Device Type: (not present)
    Bus: 0, Target: 6, Lun: 0, Device Type: Direct Access
    Bus: 0, Target: 6, Lun: 1, Device Type: (not present)
    Bus: 0, Target: 6, Lun: 2, Device Type: (not present)
    Bus: 0, Target: 6, Lun: 3, Device Type: (not present)
    Bus: 0, Target: 6, Lun: 4, Device Type: (not present)
    Bus: 0, Target: 6, Lun: 5, Device Type: (not present)
    Bus: 0, Target: 6, Lun: 6, Device Type: (not present)
    Bus: 0, Target: 6, Lun: 7, Device Type: (not present)
scu>

This seems to be only showing the first scsi card (pka0) as all the
target numbers look like the disks and one tape drive and the cdrom.

The directions say to do /sbin/scu show edt bus (number)
If I do scu show edt bus 1 (or 2...) nothing shows up.
just bus 0 has info.

Am I missing some kind of connection with the new scsi card? I
just plugged it into the mother board. I thought that would
be the only thing I have to do except connect the tape unit via
the scsi cable of course.

I also installed the robot software using setld. I've never
installed a DLT tape drive so any help would be appreciated.
I've also done the ./MAKEDEV.MC mc(number)b and it only creates
one device. I've tried several numbers according to the directions.
I don't think I can get the device files created until scu
works correctly.


Thanks,
Allan
Received on Mon Feb 24 1997 - 21:02:21 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:47 NZDT