Ignite-UX changes some files during the configuration process, including resolv.conf and nsswitch.conf. The Ignite-UX os_arch_post_l and os_arch_post_c scripts place these files on the client after the install.

These scripts are delivered in /opt/ignite/data/scripts/. You will probably only need to modify os_arch_post_l. Search on resolv.conf and nsswitch.conf for directions on what to change. After the script has been changed, modify your configuration file, which describes the archive to point to the new script.

pax_iux Errors

Errors resulting from pax_iux similar to the following:

pax_iux: X: Cross-device link

pax_iux: X: File exists

Both of these errors may occur when installing a system from an archive that does not have the same file system partitioning as the system from which the archive was created.

The Cross-device link error is caused when two files exist as hard links in the archive, and when the two files would end up in separate file systems. For example, if you created an archive on a system that did not use LVM, the root file system is all one file system. If you have two files, /usr/local/bin/f1 and /opt/myprod/bin/f2 as hard links, this error occurs if you make an archive of this system and try to apply it to a system that uses LVM and has /usr and /opt as separate file systems.

The File exists error may occur when the archive has a symlink or regular file that is named the same as a directory or mount point that exists when the archive is installed. This may happen, for example, if the original system that the archive was made from has a symlink like /opt/myprod -> /extra/space; then, when you are installing a system from the archive, you decide to create a mounted file system as /opt/myprod. The pax command will fail to create the symbolic link because a directory exists in its place.

When the error happens, you will be asked if you want to push a shell (on the client’s console). Answer yes, and from the shell enter exit 2 to ignore the error, and it will continue. Once the system is up, you can more-easily determine what needs to be done with the paths it complained about.

To avoid the error, the system that the archive is created from must not contain hard links between directories that are likely to be created as separate file systems.

Common network booting errors

Insufficient Response to PXE Boot Request

PXE-E16: Valid PXE offer not received

When the above error is seen during a PXE boot, one of the following may be true (this is not an exhaustive list) :

•The response from the DHCP server did not contain enough information to continue the PXE boot.

•No PXE boot response was received.

Additional errors may be printed after this PXE error to show what the problem is related to.

File size miscalculated

PXE-E05: Download buffer is smaller than requested file.

This problem is related to firmware in EFI on the HP Integrity rx1600/rx1620 systems. Upgrade the firmware on the system to a version that addresses the above message (system firmware 02.11 or later.)

When using a tftp server that does not support the tsize option, a file must be completely downloaded to determine its size. The file is then downloaded again into memory allocated based

234 Troubleshooting