Hello -
We have recently been applying PK6 to ES-40s running 4.0F and have been
seeing some strange behavior with the emx portion of the upgrade.
Previously, we were at PK4 with emx driver V1.12 and KGPSA firmware rev
3.03X2. Through applying PK6 and firmware upgrades, we are now using emx
driver V1.29 and KGPSA firmware rev 3.81A4. We're running ACS 8.5 with
plans to upgrade to 8.6, as soon as all KGPSA firmwares have been upgraded
to 3.81A4.
When the systems boot for the first time, with the new 1.29 emx driver, it
is recreating the /etc/emx* files and rediscovering the HSG80s / targets in
a new order, which is wreaking havoc with advfs / LSM. When using the 1.12
drivers, we just used the emxmgr to maintain the target configurations, and
after rebooting the boxes, we never had problems with target information
getting rearranged or /etc/emx* files getting recreated. To initially
correct this, we copied older /etc/emx* files over the new files and it
seemed to work on a few boxes. What we have done to keep this from
happening in the future (we thought) is to cut and paste the /etc/emx.info
information into the emx_data.c file and rebuild the kernel. We are still
seeing the problem where the systems boot for the first time and it
reordering the targets. But, now, any boot, after the initial boot, with
the new driver, updates the /etc/emx* files and everything seems to be ok.
The questions I have are: Is this normal when upgrading emx drivers? Is
there a way to "initialize" the /etc/emx* files so that the initial boot
does not scramble the targets, even though we have them hardcoded via the
kernel?
Thanks,
TK
tom.kemp_at_dowjones.com
Received on Tue Sep 25 2001 - 15:34:58 NZST