Ignite-UX Frequently Asked Questions

there is enough free space for an installation or recovery.
Setting '_hp_ignore_sw_impacts' to 1 means that Ignite-UX will not
resize the file systems according to impacts to guarantee some free
space. If you set '_hp_ignore_sw_impacts' to 1, you must ensure that
there is some free space available in / and /usr during installation
or recovery (at least 20MB) to avoid file system full issues.
If you do not set '_hp_ignore_sw_impacts' to 1, you can ignore this
information. This issue is most likely to affect you if you create a
recovery archive in which you have set '_hp_ignore_sw_impacts' to 1
in the installation file system or config.local files and you have a
nearly full / or /usr file system.
===============================================================================
1.16
Q: What do I do when I get an error reading files greater than 2 GB in size?
A: The C.6.5.61 (December 2005) and newer versions of Ignite-UX contain
the B.11.23 patch PHKL_33110 which includes install kernels to
resolve an issue where files on ISO9660 media cannot be correctly
read if they are 2 GB or greater in size. When encountering this
problem the symptoms look like:
* Loading_software: Begin
* Installing boot area on disk.
* Formatting HP Service Partition.
* Enabling swap areas.
* Backing up LVM configuration for "vg00".
* Processing the archive source (hp client archives).
* Thu Nov 03 12:37:56 EST 2005: Starting archive load of the
source (B.11.23 client archive IA).
* Completed 0% of archive
gunzip: stdin: unexpected end of file
pax_iux: The archive is empty.
ERROR: Cannot load OS archive (B.11.23 client archive IA)
The configuration process has incurred an error, would you
like to push a shell for debugging purposes? (y/[n]):
Patch PHKL_33110 contains the defect fixes for JAGaf44970 and
JAGaf67476.
Ignite-UX version C.6.8 contains the equivalent fix for HP-UX 11.11.
===============================================================================
1.17
Q: Why is the network boot of my Itanium-based system slow?
A: To reduce the amount of time it takes to perform a network boot, you
should use an Ignite-UX server that is running a tftp daemon (tftpd)
which supports the "tsize" option.
When the firmware on an Itanium-based system is downloading a file
(i.e. booting), it first attempts to determine the size (in bytes)
of the file. If the tftp daemon (tftpd) on the server does not
support the "tsize" option, the client downloads the file using the
following steps:
1. download the entire file (not storing the data), counting the
bytes
2. allocate a buffer which is the exact size of the file
3. download the entire file (again) into the allocated buffer
The B.11.11 patch which enables the "tsize" feature is PHNE_32825
which was posted on 20-Mar-2006.
Note: HPVM requires this patch if you are installing a virtual
machine from an Ignite-UX server running B.11.11. Not having
this patch installed on the server will cause the network boot
to fail because of a firmware defect. No tftpd patch is
required for B.11.23 onwards as the tftpd daemon supports the
"tsize" option from first release.
===============================================================================
1.18
Q: How can I workaround recovery failure: 'ERROR: A conflict has been
detected while attempting to restore the prior device file names'?
A: This error is caused by the way that device special files are managed