Ignite-UX Release Notes (769572-001, March 2014)

ERROR: Could not execute net_cfg_prep
NOTE: System rebooting...
Shutdown at 10:36 (in 0 minutes)
System shutdown time has arrived
◦ While installing an rx5670 via the network, when the installation settings are finalized
and installation started, the following error message is displayed on the client console:
* Loading configuration utility...
* Beginning installation from source: 16.113.12.86
======= 06/21/13 09:05:29 EDT Starting system configuration...
* Configure_Disks: Begin
* Will install B.11.31 onto this system.
#
If you were installing the system from the physical or virtual DVD media previously, a possible
workaround is to use an Ignite-UX server for installing the client. HP recommends you to try
this workaround, though it might not always be successful. If 11i v2 or 11i v3 ISO images
are created using March 2013 Ignite-UX version, then you may face the issue.
To obtain the fixed March 2013 ISO images, contact HP Support Center. Mention that fixed
HP-UX 1303 OE ISO images must be provided. This is caused by an Ignite-UX issue which is
tracked in QXCR1001268768, and fixed in C.7.17.361.
• If an installation does not seem to be making progress after a reasonable amount of time (the
log file is not getting updated); check the client console. There are some cases where errors
are not written to the log file, but are displayed on the console. Normally, the log file is updated
every few minutes. The only known exception is when a large archive is being extracted.
• Ignite-UX can sometimes assign the "wrong" swap volume to be "primary". If you set up a
primary swap-only volume, and then set up a large swap/dump volume, the swap/dump
volume can become the primary swap volume. This is done to ensure the dump volume is
within the first 2 GB boundary of the disk. A future version of Ignite-UX will likely add the
ability to specify which swap volume is primary, in addition to the ability to specify swap
priorities for each swap volume.
• If you set some of the "final" system parameters (also known as set_parms information), but
not all of them, your system will come up, but will not automatically run set_parms and you
will have to take explicit action to enter the new data.
The most common case is when you have entered the final host name and IP, but have not
yet entered the time zone or root password.
Workarounds are as follows:
◦ make sure you enter all information at Ignite-UX time, or
◦ enter no information at Ignite-UX time (so set_parms will run), or
◦ make the remaining changes manually after the system comes up by using the following:
/sbin/set_parms initial
• Ignite-UX does not handle large size quantities. For example, close to, equal to, or greater
than 2 TiB (2^31). In some cases, storagerelated software may significantly further limit
maximum sizes (failures for sizes greater than 1 TiB have been observed). This means that
Ignite- UX can not install or recover content to or from disks, volumes, file systems or other
storage units of larger sizes. In most cases these large disks will be hidden from Ignite-UX
interfaces and will not be available for install. In some cases large disks may be listed but use
General issues 23