Ignite: ERROR: Cannot load OS archive

[Chad Florian]

Trying to build an rp5470 from a make_sys_image "golden image". This has worked in the past, but on this archive I'm getting the error below. Is there some way to get more information? It's not clear ifthe file exists error is where the trouble starts as the chronology of the log would suggest that it continues on. But perhaps it's just bombing there and it only appears to continue? Any help is appreciated!

-Chad
--------------------------------------

* Loading_software: Begin

* Installing boot area on disk.
* Enabling swap areas.
* Processing the archive source (HP-UX Core Operating System Archives).
* Fri Apr 30 14:22:19 EDT 2004: Starting archive load of the source (SOE
HP-UX 11.11 2004.Q2.0 USM).
pax_iux: opt/ignite/bin : File exists
* Processed 10% of archive
* Processed 20% of archive
* Processed 30% of archive
* Processed 40% of archive
* Processed 50% of archive
* Processed 60% of archive
* Processed 70% of archive
* Processed 80% of archive
* Processed 90% of archive
* Completed 100% of archive
ERROR: Cannot load OS archive (SOE HP-UX 11.11 2004.Q2.0 USM)
ERROR: The configuration process has incurred an error. If you wish to push a
shell for debugging purposes, go to the target machine's console and
interact there. Otherwise, use the "Stop Install" action to reboot or
halt the target machine.

[generic_1]

Are you building this off of a tape? How are you installing the image?

[Steven E. Protter]

This seems to have been happening a lot on itrc lately.

As opposed to the last one I responded to, it would appear that the unpack process finished.

Did your core os include the product listed in the error?

I'd push a shell and carefully poke around to see where it died.

You might want to hang a tusc trace on the process created on the Ignite server that serves up the image. This can let you now exactly what died and why.

/usr/contrib/bin/tusc -o $TF -p $pid &

TF is the file -p is the pid -f I think collects data off of forks.

http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-7.5/

SEP

[Chad Florian]

I was able to push a shell and execute "exit 2" per the "troubleshooting / golden images" portion of the ignite docs. It appears that the only problem was the /opt/ignite/bin. On the source system it's a soft link to /opt/ignite/pabin. After I "exit 2", the process finished just fine but the soft link has to be recreated manually.

The TS doc mentions hard links when the target system splits the file systems. But this is just a doft link in the same directory...

I suspect that the image is trying to create the link and the directory already exists. Question is, why does it already exist? Does ignite lay this down prior to un-taring the image?

The only file in /opt/ignite/bin is a file called print_manifest which is a binary file.

Any ideas here? I can make it work, but it sure would be alot cleaner without this problem...

TIA,
-Chad

[Bharat Katkar]

Take a look at this doc:

http://docs.hp.com/cgi-bin/onlinedocs.py?mpn=B2355-90834&service=hpux&path=00/00/20&title=Ignite-UX%20Administration%20Guide,%20Edition%2015

all the best.

[heidi trafidlo_1]

oh my gosh! I am so *happy* I found this posting!!!!!!
it worked!
:-)
Sending a gazillion points!