Ignite-UX (IUX) Document for Frequently Asked Questions (FAQ) (762793-001, March 2014) (Edition: 3)

9 Archive installation (Golden images)
Frequently asked questions
Following are the frequently asked questions in archiving the installation (Golden images), which
is a compilation of all the available feedback from the users.
What does the following gunzip error indicate? gunzip: stdin: unexpected
end of file pax_iux: The archive is empty. ERROR: Cannot load
OS archive (HP-UX Core Operating System Archives)
It appears that the NFS mount succeeded, but the file was not accessible from the client. Check
the following possibilities:
• The file has a different name so check your configuration files for errors.
• The file has the wrong permissions such that it is not readable, so check your /etc/exports
file.
The /etc/nsswitch.conf and /etc/resolv.conf files from my archive do
not end up on the client. Why?
There are certain files which Ignite-UX modifies during the configuration process, among them are
resolv.conf and nsswitch.conf files. To end up with the archive versions of these modified
files on your clients, Ignite-UX provides two scripts called os_arch_post_l and os_arch_post_c
to aid you. These scripts are delivered in the /opt/ignite/data/scripts directory.
Modification of only os_arch_post_l file is sufficient to retrieve the file. Copy this file to a new
name in the same directory and then edit it searching on resolv.conf and nsswitch.conf
for instructions regarding what must be changed.
After the script has been changed, modify your configuration file that describes the archive so that
it points to the new script.
What do these errors mean pax_iux: X: Cross-device link, pax_iux:
X: File exists, or pax_iux: X : Device busy?
Both of these errors might occur when installing a client from an archive that does not have the
same file system partitioning as the client on which the archive was created.
The first error, pax_iux: X: Cross-device link, is caused when two files exist as hard
links in the archive, and if these two files reside in separate file systems. For example, if you create
an archive on a client that did not use LVM, the root file system is all one file system and the files
/usr/local/bin/f1 and /opt/myprod/bin/f2 are hard linked. If an archive of such client
is created, then try to apply it to a client that uses LVM and has /usr and /opt as separate file
systems this error occurs.
The second and third errors, pax_iux: X: File exists and pax_iux: X : Device
busy, can occur when the archive has a symbolic link (symlink), or regular file that is named the
same as a directory or mount point that exists when the archive is installed. For example, if the
original client on which the archive was made has a symlink like /opt/myprod -> /extra/
space, and when you are installing a client from the archive you decide to create a mounted file
system as /opt/myprod. The pax command fails to create the symlink because a directory exists
in its place.
You can recover from this failure when the error occurs because, on the client's console, you are
asked if you want to push a shell. Enter yes, and then enter exit 2 from the shell you can ignore
the error and continue the installation.
Once the client is up, you can easily determine what to do with the paths that created the errors.
Frequently asked questions 37