Thanks to Alan (alan_at_nabeth.cxo.dec.com) and to John J. Francini
(francini_at_progress.com) for their replies to my question (original
question is after my summary). It was Alan who came up with the best
explanation/solution:
"The operating system and the console were not written by the
same group. There's never been any guarantee that the two
probe methods would exactly match. For what it is worth, the
AS500 is the only system that I've seen where they differed
between Tru64 UNIX and the console. OpenVMS is far more likely
to have the probe order not match.
The best work-arounds I can think of are:
o Change fstab and /etc/fdmns to reflect the new device names.
o Take out the KZPAA so you can boot the system using the
old names and hand edit the configuration so that the
kernel's probe order matches the one desired. You can
do this by explicitly setting the "scsi#" association
to each adapter. Build a new kernel, put the KZPAA back
and it should probe in the desired order."
The latter is essentially what I did. I actually copied the (UFS) root file
system to a spare partition, made the changes to fstab and rc.config, booted
genvmunix from the new root file system and ran sizer to get a new config
file. Then edited the config file to change
bus pci0 at nexus?
callout after_c "../bin/mkdata pci"
bus pci1000 at pci0 slot 8
bus isp0 at pci1000 slot 0 vector ispintr
--> controller scsi0 at isp0 slot 0
bus isp1 at pci0 slot 9 vector ispintr
--> controller scsi1 at isp1 slot 0
to
bus pci0 at nexus?
callout after_c "../bin/mkdata pci"
bus pci1000 at pci0 slot 8
bus isp0 at pci1000 slot 0 vector ispintr
--> controller scsi1 at isp0 slot 0
bus isp1 at pci0 slot 9 vector ispintr
--> controller scsi0 at isp1 slot 0
Then built a new kernel and rebooted with the original system disk and
all the devices show up with the 'correct' IDs.
thanks again,
john
----------------------------------------------------------------------------
John Deacon | UCL Starlink Site Manager
Dept Physics and Astronomy | Email: jrd_at_star.ucl.ac.uk
University College London | Tel: 0171-380 7147
Gower Street London WC1E 6BT | Fax: 0171-380 7145
----------------------------------------------------------------------------
>Hi All -
>
>I've got an AlphaStation 500/500 with 2 internal disks (rz3 and rz5) a
>CDROM (rz4) and 4 external disks (rz0, rz1, rz2 and rz6). I've just now
>added a second SCSI card (a KZPDA-AA) in one of the PCI slots and have
>plugged in an external DAT drive (SCSI ID 5).
>
>At the console prompt the original SCSI card shows up as pka0 with devices
>DKA0, DKA100...etc and the second SCSI card is pkb0 with the tape drive
>MKB500. All as expected.
>
>The problems start when I boot the machine. DKA300 is the boot device
>and everything starts off fine until the boot prcedure gets to the point
>where it probes the devices, at this point it detects the new SCSI card
>first and picks up the tape drive as tz5 and then it detects the original
>SCSI card with devices rz8, rz9, rz10...etc. Not surprisingly it then
>falls over when it tries to mount rz3 as the root file system because it
>thinks its now rz11...
>
>Have I missed some thing obvious here, why does it first detect the cards
>one way around and then swap them over during the boot process ? How do I
>get the new card to appear as the second card when the machine boots ?
>
>cheers,
>
> john
>
Received on Tue Aug 03 1999 - 13:35:15 NZST