cannot load OS archive

[heidi trafidlo_1]

I found a thread that speaks to the new problem I am having with ignite using a golden image archive. The process gets all the way thru "processing archive" and then aborts with the error: cannot load OS archive (image1: V11 S700 PS5.5). The thread that I found referenced a soft link for /opt/ignite/bin. The author overcame the issue by pushing a shell @ the client side when the error message appeared. My question is - how do you push a shell at that point?

[Steven E. Protter]

Most of the time this is caused by networking failure.

1) Yes, you should push a shell. You want to poke around and see what state the archive is in.

few tricks:

1) instl_adm -d
This will display networking. For this to work right, the networking must be correct at both ends and on any network switch ports between the bxoes.

To change instl_adm -d > file
vi the file make changes

instl_adm -f file

This will load the new changes.

In general this means 100 BaseT full duplex manual for 10/100 cards and 1000 baseT full duplex auto negotiate for 1000 and faster NIC. Note for the search engine(1000 BaseT is the fastest NIC at the time of this post).

2) If you have added recent pax patches to the system used for making a golden install image, there may be issues with files bigger than 2 GB in the archive. They may not be able to be unpacked by pax_iux the pax unpacker built into Ignite.

This issue dates back to Ignite 3.x and 4.x and I've not had occaision to test it since.


3) Make sure permissions are correct on the exports in NFS that Ignite is using. Make sure the /etc/exports file is not blocking access.

4) Report what you see when you push that shell.

Good Luck.
SEP

[Michael Roberts_3 · Accepted solution]

On the client console you should see something like:

* Completed 100% of archive
ERROR: Cannot load OS archive (English HP-UX B.11.11 64 Bit )

The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]): *

If you answer "y" at the prompt and type "exit 2" to
ignore, the install continues without further errors. However, it will
be neccessary to manually remove /opt/ignite/bin and recreate the
symbolic link to /opt/ignite/binpa or /opt/ignite/binia once the
install is complete.