A hearty thank you to all who offered help:
Jeffrey_HXXXXXX_at_
Davis_at_
mjbr_at_
Roger.MXXXX_at_
pobrien_at_
alan_at_
While I have yet to determine the precise cause of my
situation, it would appear that my systems are safe and will
continue operating in their current mode with minimal risk.
Based on the solutions offered, I suspect these machines
are not as "static" as I thought, but there are several people
working with them, so it's quite possible they have changed
since the 4.0F install. So I will leave well enough alone
and possibly isolate the cause at a later date.
Solutions follow the text of my original message.
>Hello All,
>
>I have several DS-10/DS-20/ES-40 machines that I am migrating from
>version 4.0f to 4.0G (Application vendor requirement). I have found
>that my hard drive device files have changed as a result of applying
>patches to get to 4.0G (as opposed to re-installing to the 4.0G level).
>The change is consistent across platforms, although the numbering
>varies depending on what I have for disks (IE, raid vs internal).
>
>EG:
> before upgrade - /dev/rz16
> after upgrade - /dev/rz32
>
> before upgrade - /dev/rz17
> after upgrade - /dev/rz33
>
> before upgrade - /dev/rz18
> after upgrade - /dev/rz34
>
>I am able to get around this problem, but I'm curios if it is a known
>bug or an issue related to the way I upgraded? or is it something
>serious that will bite me in the future? I've searched the archives,
>but haven't found anything about this issue.
>
>Your input is appreciated and I will summarize.
>
>Regards,
>Robert
SOLUTIONS:
Have you done any hardware alterations? This is very like what happens
when you change the physical configuration by adding an extra SCSI card.
<<<In my case, I didn't think there had been any, but it's probable
<<<given the nature of this problem, and the advice of others. Read on:
===================================
In V4 disk and tape devices inherit their name from their
bus address and bus number using the algorithm (*):
rz#, where # = (bus * 8) + target-id
The bus number is assigned in the order that adapters
are found, which is controlled by the configuration
file. Between versions it is unlikely that the built-
in order changed, but if you or some previous system
manager edited the configuration to use some other
order, that would explain the change.
The basic problem is quite common when new adapters are
added between existing adapters. The new I/O adapter
inherits a new bus number and the existing adapters
all move up, getting a new bus number and thus the
devices on that bus changing name. This can be annoying,
so system managers often hand edit the configuration to
put the new adapter after the existing one. Then, they
promptly forget they made the change until they rebuild
the kernel and everything gets renumbered.
(*) array controllers that use non-zero logical units
complicate this a bit more, but it isn't relevant to
your problem.
======================
My first thought is that there are 2 new scsi busses detected in lower
bus order than which previously were not. What bothers me is I can
not think of a device which is autodetected in any version of 4.0F
which is seen in 4.0G. A kzpcm dual with network option comes to
mind as a likely canidate, but I am not aware of any versions in F
which it is not autodetected. I dunno.
=========================
http://www.tru64unix.compaq.com/docs/updates/V40G/TITLE.HTM
go to this section:
May 1, 2001: KZPCC i2o Upgrade and Recovery Procedure
Check this link out, with the info. provided I can't tell if it
applies are not.
===========================
It's possible that the upgrade/patch changed the order of the bus-probe
or modified the kernel config file. If so there should be something in
the release notes or on the mailing list archives. The other thing to
check is to compare your old kernel config with the new one and see if the old one had been modified to change the order of the scsi bus names.
===========================
If you go into the kernel configuration file you will see notations like
scsi2, scsi3, scsi4, etc. This is where the rz numbers are determined.
scsi2 gets translated to rz16 (2*8).
The file is found with the same name as your system in the directory
/usr/sys/conf. By updating the file and rebuilding the kernel with
doconfig -c filename you can set the rz numbers to whatever will work best
for you.
--
__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop_at_Netscape! http://shopnow.netscape.com/
Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
Received on Fri Feb 08 2002 - 18:20:41 NZDT