I finally was able to install the SCSI card by rearranging the cards without
having to edit any files. It turned out that the top slot on the PCI0 bank
gave me the last SCSI bus. I wish I could have found documentation on how
the SCSI buses get set. Thanks for everyone's help.
Steve March
e-mail: Steve.March_at_airgas.com
-----Original Message-----
From: g.vanoene_at_kpn.com [mailto:g.vanoene_at_kpn.com]
Sent: Friday, November 10, 2000 3:07 AM
To: Steve March
Subject: RE: Problems adding a new SCSI Card
Steve.
You (probably) don't have a hardware problem.
The controller you've added reassigns you're hardware devices and for that
reason you need a new /sys/conf/MACHINENAME configurationfile. And make new
links in /etc/fdmns with ln -s.
First boot in single user mode with /vmunx. Then mount -u / and /usr.
sizer -n oldconfig (this creates 2 files in /tmp.
Now boot in single user mode with genvmunix (b -fi /genvmunix -fl s).
Mount -u / and /usr. sizer -n newconfig.
Compare newconfig with oldconfig and add differences in
/sys/conf/MAchinename. Now you're ready to build a new kernel. Before
booting the new kernel make a copy of /etc/fdmns because the links to the
filedomains need to be replaced with new diskdevice names. E.g. rz8 probably
will become rz16.
NOW boot with new kernel in single user mode. Look for new devices in /dev.
Replace links in /dev/fdmns/filedomains with the new added devices. Replace
swap link in /etc/fstab. Reboot the system and hopefully it works.
Good luck.
Regards
Gerwin van Oene
KPN Telecom
The Netherlands
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Indeed, bus numbering is position AND search order dependent.
Adding a new adapter can have the result you're seeing with
the change in device names. Your options for a solution are:
1. Hand edit the configuration file to put the new adapter
on a particular SCSI bus after the existing ones. This
is complicated by the fact that your system disk is one
of those that had its name changed.
2. Move the adapters around so that the new one is the
last one found. The 4100 has two PCI busses. So the
search order is as relevant as position.
The slot numbering of the 4100 is documented on the panel
that covers the slots. Briefly it looks like:
PCI 1 Slot 5
PCI 1 Slot 4
PCI 1 Slot 3
PCI 1 Slot 2
PCI 0 Slot 5
EISA Slot 3
PCI 0 Slot 4
EISA Slot 2
PCI 0 Slot 3
EISA Slot 1
PCI 0 Slot 2
I believe that Tru64 UNIX sizes PCI 1 first and then goes
to PCI 0, so getting the system disk back may only mean
having to order the top four slots. Depend on the combinations
of UFS, AdvFS and LSM that you use, renumbering devices can
be as simple as editing /etc/fstab once the system disk is
mountable. Or, it may be easier to move adapters around.
Since V4 should create the special device files for any
"new" device it sees, you may be able to mount the root
file system without having to deal with the names. This
is particularly easy with a UFS root:
mount -u /dev/rzwhatever /
Once the root is mounted, changing the rest may be easy.
To hand edit the configuration, you're probably best off
taking the new adapter out and building a custom kernel
before putting it back in. You can use the boot message
from the generic kernel to see what needs to be added.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hi,
It may help you shifting down the cards, so you have PCI slot available, if
this is PCI to SCSI card. I know I had to do that once to avoid the devices
change.
Other thing is, even that you can see the devices at console level, you
still have to run .MAKEDEV otherwise, you will not see the drives. So it is
BUS * 8 + the target number and your LUN. Base on that you create your
devises. Then run disklabel on each of them, then mount them. You only run
the genvmunix and then build thenew kernel to see the card.
Zibbyb_at_comusearch.ca <mailto:Zibbyb_at_comusearch.ca>
Hope it helps!!
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Steve,
You are probably correct about the new scsi card forcing a renumbering of
the buses. This is a very common problem in the AS4100's.
The bus order is determined by the slot priority, which isn't top-down or
bottom-up.
There are two banks of PCI slots, the highest priority slot is the top slot
of the /bottom/ bank. Priority goes down, the second from the top slot in
the /bottom/ bank is priority 2, etc. to the bottom of the bottom bank. The
next lowest priority slot is the top slot of the /top/ bank and goes down
from there.
I'm betting that the controller that drives your boot disks is in the top
bank below the new card.
You can shift the cards around to get the new board in a lower priority
slot. For example, since the top slot of the top bank was open, move all the
boards in the top bank up one slot and put the new card in the bottom slot
of the top bank.
You may also have a kernel config file that remaps then buses. This would
explain why it boots (the dk device name is correct) but when the kernel
takes over and tries to remount the boot disk it's not on the bus that it
should be any more.
If you have any questions, don't hesitate to ask. When I was with Compaq
Services I worked out the bus priority maps for the AS4100 and published
them for the specialists and field service staff.
Alan Davis
davis_at_tessco.com
----Original Message-----
>From: "Steve March" <Steve.March_at_Airgas.com>
>To: "tru64-unix-managers_at_ornl.gov"
<tru64-unix-managers_at_ornl.gov>
>Cc:
>Bcc:
>Subj: Problems adding a new SCSI Card
>Type: IPM.Note
>Sent: donderdag 9 november 2000 15:50
>
>Yesterday I installed a new SCSI adapter card into our Alpha 4100
(Digital
>UNIX 4.0E) which is attached to a new HSZ70 disk array that we
purchased.
>When I do a "show device" at the console mode prompt it can see all the
new
>drives. When I boot into UNIX, the diskconfig utility does not see the
new
>drives. I booted the system with the generic kernel "genvmunix" and
when I
>attempted to do a bcheckrc to mount file systems I need to do a
doconfig, I
>get error messages saying that the older file systems is invalid or
cannot
>be open and it can't run fsck on anything nor mount any filesystems in
the
>/etc/fstab. Because of this, I am not able to do a doconfig to rebuild
the
>kernel off the generic kernel. I tried to rebuild the kernel of the
current
>production kernel which worked but the newly generated kernel still did
not
>see the new drives on the added SCSI adapter. I then tried to boot of
the
>generic kernel and just mount /usr and /tmp which are advfs which worked
but
>the new kernel I built failed at the "bcheckrc" stage again and file
systems
>failed to mount. Another problem I had is that I cannot mount root as
advfs
>in single user mode since it is already mounted. So at this point I am
>running off a backup kernel and UNIX still cannot see my new drives. It
>seems like the generic kernel can see the new drives but it chokes on
the
>older drives and the current production kernel just can't see the new
SCSI
>card and it's new drives. I don't think it's a hardware problem since
it
>can see the new devices at the console mode prompt.
>
>The SCSI card I added is installed at the very top. I think what is
>happening is all the device names are being renumbered when using the
>genvmunix and rebuilding a new kernel. Does anyone know if installing
the
>SCSI card at the top would do this? Since I'm out of free PCI slots,
would
>all the SCSI bus numbers remain the same if I move all the existing
cards up
>one slot and put the new SCSI card at the very bottom?
>
>Any help will be appreciated.
>
>Thank you,
>Steve March
>Airgas, Inc.
>e-mail: Steve.March_at_airgas.com
>
>
Received on Mon Nov 13 2000 - 14:50:19 NZDT