Dear Manager,
Many thanks to those who reply.
The confusion over why the console sees the external devices connected to
the 2nd controller whereas Unix sees it connected to the 4th controller is
now clear up. Most of you pointed out
the reason why Unix sees the external devices are connected to the 4th
controller is to do with the setting in the configuration file
'/sys/conf/machine_name'
This confusion came about was because I was used to see the device file
(/dev/rznn) associate with the controller with PWS Alpha 500 au system under
DU4.0d. For example dkd500 is associate with the device file rz29 and dkc0
is associate with device file rz16.
Thanks to:
Don (rye_at_jwfc.acom.mil)
Joe Fletcher
Oisin McGuinness
Chris Wilson
Andrew Johnson
alan_at_nabeth.cxo.dec.com
Dr. Tom Blinn
Arnold Sutter
Duncan Webbe
Dr. Tom Blinn, Chris Wilson & Oisin McGuinness provides the explanation and
some example which I think will benefit to others. Their replies are as
follows:
>From Dr. Tom Blinn:
.
I don't have an XP1000 to test on, but I suspect that if you use the command
>>>show config
in the console firmware, you will discover that the hardware topology has an
IDE bus with two ports, and nothing connected to them. If the IDE busses
are
connected to the PCI bus between your two SCSI controllers, then the kernel
is going to see the two "ata" devices, map them to SCSI bus structures, and
number the devices as you note. The console doesn't use the "dka" names for
IDE devices, and if there are no devices, only busses, then the console is
not going to do anything obvious.
If you want the kernel's naming to use rz8, rz8, etc. for the devices on the
second SCSI controller, then you need to edit the kernel configuration file
you are using and comment out the "ata" lines, the "scsi" lines that match
them, and change the scsi line associated with your other controller to be
"scsi1" instead of "scsi3".
Actually, since you seem to have an IDE CDROM, you will have to really poke
things around in the config file. The best advice is just "learn to live
with
it, it's doing exactly what it's designed to do". And, if you manage to
find
the right PCI slot configuration, you MIGHT get the second real SCSI
interface
to appear in the hardware topology before the IDE ports, in which case, all
of
this will change and you'll have trouble explaining where your CDROM drive
moved to..
>From Chris Wilson:
.
You kernel configuration has the bus named as 'scsi3'. look in
/sys/conf/<YourMachineName>
This is probably because there is configuration file for scsi2 also in
the kernel config file. It does not matter if there is no actual scsi2
device.
You can edit the kernel file to change this name, but it will also cause
the device names to change.
Example from my kernel configuration file
controller scsi0 at psiop0 slot 0
controller scsi16 at pza0 slot 0
controller scsi17 at pza1 slot 0
controller scsi3 at pza2 slot 0
controller scsi4 at isp0 slot 0
controller scsi5 at isp1 slot 0
I could just as easily rename scsi3 to scsi2. rz28 would then change to
rz20. If you've got file systems mounted on rz28 partitions you'll have
to fix up fstab, lsm or whatever you're using.
>From Oisin McGuinness :
.
It depends on how the SCSI controllers are configured in the kernel.
If one uses the generic kernel genvmunix to configure a system, usually
the order of probing of controllers and disks by the kernel or by sizer is
the
same as what the console level sees.
What I've ended up doing, e.g., for compatibility between Sybase installs,
where
we want all our sybase devices to be the same between machines, is edit the
config files until the buses are numbered the way I want them, not the way
the probes
want them.
Specifically, find your kernel config file, in /sys/conf/HOSTNAME, and look
for
the lines with scsi1 scsi2 etc.
Renumber to taste, rebuild the kernel, install and reboot.
Sample kernel lines:
# We compose a machine description for the 2100a with
# two ethernets and 2 fast wide SCSI cards.
bus ibus0 at nexus?
# Primary PCI bus.
bus pci0 at ibus0 slot 0
callout after_c "../bin/mkdata pci"
bus eisa0 at pci0 slot 2
callout after_c "../bin/mkdata eisa"
controller ace0 at eisa0 slot 10 vector aceintr
controller ace1 at eisa0 slot 11 vector aceintr
controller lp0 at eisa0 slot 12 vector lpintr
controller fdi0 at eisa0 slot 13
device disk fd0 at fdi0 drive 0
# Describe all other slots on Primary PCI bus.
controller trio0 at pci0 slot 6
# Ethernet.
controller tu1 at pci0 slot 7
# Fast Wide SCSI, want counted as 2nd SCSI bus.
bus pci4000 at pci0 slot 8
bus isp1 at pci4000 slot 0 vector ispintr
controller scsi1 at isp1 slot 0
# Slot 9 empty.
# Secondary PCI bus.
bus pci2000 at pci0 slot 3
# Built in SCSI controller on Secondary PCI bus.
bus psiop0 at pci2000 slot 1 vector psiopintr
controller scsi0 at psiop0 slot 0
# Ethernet.
controller tu0 at pci2000 slot 6
# Narrow SCSI card, use for tape.
bus psiop1 at pci2000 slot 7 vector psiopintr
controller scsi3 at psiop1 slot 0
# Fast Wide SCSI, want counted as 3rd SCSI bus.
bus pci3000 at pci2000 slot 8
bus isp0 at pci3000 slot 0 vector ispintr
controller scsi2 at isp0 slot 0
#
controller gpc0 at ibus0 slot 0 vector gpcintr
This was on a machine where it really really wanted to call what I wanted to
call scsi3 scsi1....
Note disks on scsi0 will get numbered 0 to 7; disks on scsi1 get numbered 8
to 15 etc.
The major thing when making changes is to be careful not to upset your
system disks, or
to be prepared to do some creative relinking in /etc/fdmns/*/.
Original Question
=================
>We have a XP1000 recently delivered and preinstalled with tru64 Unix 4.0F,
>EV6 (no patches applied)
>
>We add a second SCSI controller for the external devices like tape drive
>etc. When I switch on and do a show device at the console prompt, it
>indicates external devices are attached to the 2nd controller as you would
>expect (dkb500, mkb400 etc). However, when I boot the machine, Unix sees
the
>external devices attached to the 4th controller (rz29, rz28 etc)>
>
>Using SCU to scan the system shows the following:
>
> bus 0, target 0, lun 0 // internal disk
> bus 1, target 0, lun 0 // internal CD-ROM
>** bus 3, target 5, lun 0 // external disk
>** bus 3, target 4, lun 0 // external tape
>
>Has anyone come across this before and does anyone know why at the console,
>it sees external devices attached to the 2nd controller (dkb500, mkb400)
but
>when booted the system, Unix sees the external devices attached to the 4th
>controller (rz29, rz28) ?
Eric
15/07/1999
Received on Thu Jul 15 1999 - 13:44:12 NZST