Known Install/Update Problems

HP CIFS Server Product

The new version of the HP CIFS Server A.01.09.04 is based on Samba 2.2.5 and is available on HP-UX 11i v2 release. Please refer to the HP CIFS Server 2.2e (version A.01.09.04) Release Notes for new features, known problems, and workarounds for this product. The CIFS Server 2.2e (version A.01.09.04) Release Notes are available in the Networking and Communication Section of the HP document web site:

http://docs.hp.com

Known Issues with OE Media Install Tool and Network Depots

The Ignite-UX install tool on the OE media supports the use of network depots. However, network depots must match the media depots for the choices in the install tool to work properly.

The Ignite-UX documentation also explains the setup and use of network depots without using the OE media for each installation. See the following web site for information on the Ignite-UX product:

http://software.hp.com/products/IUX

Error Message When Trying to Ignite an HP-UX 11i v1.6 System with an HP-UX 11i v2 Ignite-UX Server

If you are trying to install HP-UX 11i v2 on an HP-UX 11i v1.6 system from an HP-UX 11i v2 Ignite-UX server, you may see the following error message if your HP-UX 11i v1.6 system is using VxVM:

ERROR:   VxVM installs of 11.22 are not supported with the 11.23 or
          later install kernel due to VxVM 3.5 versus 3.1           incompatibilities.  The VxVM disk group “rootdg” must be           changed to LVM or whole-disk or be removed

How Do You Know If This Affects You

If your current system is running HP-UX 11i v1.6 and VxVM, and you attempt to install HP-UX 11i v2 from an Ignite-UX server, you will receive this message.

What to Do

Because of incompatibilities between VxVM 3.1 (on HP-UX 11i v1.6) and VxVM 3.5 (on HP-UX 11i v2), you can not install HP-UX 11i v2 on an HP-UX 11i v1.6 system running VxVM 3.1 from an Ignite-UX server. Instead, you can do one of the following:

For more information, please see the Ignite-UX website:

http://software.hp.com/products/IUX

HIDS Becomes Unbundled during Update

The following warning message may appear in your swagent.log after the update process, or from running swverify.

From swagent.log:
       * [20255] Running “checkinstall” script for fileset
         “IDS.IDS-AGT-KRN”.
WARNING: Excluding fileset IDS-AGT-KRN because the IDDS driver is
         already configured. An unbundled IDS-AGT-KRN fileset may
         result. If your system contains an unbundled IDS-AGT-KRN
         fileset, the installation, configuration and operation of
         HP-UX Host IDS is not affected. You can safely ignore the
         unbundled IDS-AGT-KRN fileset.
NOTE:    [20259] The “checkinstall” script for “IDS.IDS-AGT-KRN 	gave an “exclude” return (exit code “3”). The script location was
         “/var/tmp/BAAa04878/catalog/IDS.2/IDS-AGT-KRN/checkinstall”.
NOTE:    [140257] This software will be excluded from further
         processing.
       * [20255] Running “checkinstall” script for fileset
         “IDS.IDS-ADM-RUN”.
 
From swverify:
ERROR:   [140167] The product “IDS,l=/opt/ids,r=C.02.01.44” is not
         compatible with this system’s architecture or operating
         system. If the OS has been updated since this product was
         installed, a newer version should be installed if available
       * [140061]     Configured    IDS.IDS-AGT-KRN,l=/opt/ids,r=C.02.01.44

How Do You Know If This Affects You

If you update your system to HP-UX 11i v2 from either HP-UX 11i v1.6 or HP-UX 11i v2, you will encounter this error message.

The problem is caused by an ‘orphaned’ fileset IDS-AGT-KRN left on your system in order to prevent an unnecessary reboot, and results in swverify errors after the update.

What to Do

You can safely ignore this message. HIDS will work properly. However, if you want to ensure a clean installation of IDS:

“Incorrect protocol version (20) in volboot file” Error

After updating to HP-UX 11i v2 from HP-UX 11i v1.6, the following error message may appear during reboot:

Starting vxconfigd in boot mode (pre_init_rc).
vxvm:vxconfigd: WARNING: volboot: Incorrect protocol version (20) in volboot file.
vxvm:vxconfigd: WARNING: volboot: Using the highest supported protocol version 40
Checking root file system.

How Do You Know If This Affects You

You will encounter this error if you updated an HP-UX 11i v1.6 system with VxVM 3.1 as your volume manager to HP-UX 11i v2 with VxVM 3.5. The problem is caused by different version values in the volboot file (20 in VxVM 3.1; 40 in VxVM 3.5

What to Do

You can safely ignore this error message.

“Unable to flush file system metadata for /stand to disk” Warning

The following warning message will appear just before your system reboots after updating to HP-UX 11i v2 from HP-UX 11i v1.6:

WARNING: Unable to flush file system metadata for /stand to disk

How Do You Know If This Affects You

The problem occurs after updating to HP-UX 11i v2 from HP-UX 11i v1.6. During the reboot after the update, the HP-UX 11i v2 Update-UX kernel attempts to reboot the system.

While the system has been updated with HP-UX 11i v2 bits, the system kernel is still running as HP-UX 11i v1.6 before the reboot. You will encounter this warning message because of differences between the Update-UX kernel and system kernel commands used to shut down your system.

What to Do

You can safely ignore this warning message.

mod_load_helper Error

After updating from HP-UX 11i v1.6 to HP-UX 11i v2, you may see the following dmesg or syslog error:

MOD: mod_load_helper:gvid_him_fgl(gvid_him_fgl):_load returned error 13

What to Do

You can safely ignore this error.

/stand/ioconfig Read Warning

After cold-installing HP-UX 11i v2, you may see the following warning message while rebooting your system:

Booting kernel WARNING: GIO: read_ioconfig_file(): /stand/ioconfig read error. ioconfig = NULL NOTICE: cachefs_link(): File system was registered at index 4. NOTICE: nfs3_link(): File system was registered at index 7. td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/2/1/0 igelan1: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/

How Do You Know If This Affects You

This problem occurs on new installed kernels because there is no ioconfig file from a previous boot. GIO issues the warning because it cannot find an ioconfig file.

What to Do

You can safely ignore this warning.

No Dump Devices Configured Warning

After cold-installing HP-UX 11i v2, you may see the following warning message while rebooting your system:

WARNING: No dump devices are configured. Dump is disabled. Starting the STREAMS daemons-phase 1 execve(“/sbin/sh”) failed, errno 0xffffffff execve(“/bin/sh”) failed, errno 0xffffffff Create STCP device files Starting the STREAMS daemons-phase 2

What to Do

You can safely ignore this warning.