Cannot Find Specified Archive
Errors: gunzip: stdin: unexpected end of file
pax_iux: The archive is empty.
ERROR: Cannot load OS archive (HP-UX Core Operating System
Archives) |
The NFS mount probably succeeded, but the file
was not accessible from the client. Check these possibilities:
File has a different name
(check your configuration files).
File has the wrong permissions
such that it is not readable. Check /etc/exports for HP-UX 11i v1 and 11i v2 systems, and /etc/dfs/dfstab for HP-UX 11i v3 systems.
Missing .conf Files
The /etc/nsswitch.conf and /etc/resolv.conf files from the archive do not end up on the installation client.
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 should be done with the paths it
complained about.
To avoid the error, the system that the archive is created from should not contain hard links
between directories that are likely to be created as separate file systems.
Printable version
