Golden Image install failing

[KPS]

Hi,

I'm pushing a Golden Image from my Ignite-UX Server to a client. This is failing and I'm not sure why? I'm not sure what actions I need to take for this problem? Right now, the client is at the ISL Boot Main Menu...

Here is what the logfile on the Ignite Server reveals:

* Download_mini-system: Complete



* Loading_software: Begin

* Installing boot area on disk.
* Enabling swap areas.
* Backing up LVM configuration for "vg00".
* Processing the archive source (11i DigVSM Image).
* Fri Sep 24 16:27:34 EDT 2004: Starting archive load of the source
(Recovery Archive).
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 (Recovery Archive)

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



* Loading_software: Error


======= 09/24/04 19:57:30 EDT Installation complete: Failure

NOTE: Search for the word "ERROR" in the log file for details:
on a server: /var/opt/ignite/clients/0x00306E4B1A17/install.log
on a client: /var/opt/ignite/local/install.log
NOTE: Rebooting system.

[Steven E. Protter]

I would check permissions on the archive and the conditions under which the archive was generated.

Was the Core OS that was built into the arhive match the OS of the archive. The key to solving this issue may be in one of two places:

1)
on a server: /var/opt/ignite/clients/0x00306E4B1A17/install.log
on a client: /var/opt/ignite/local/install.log

2) The log of the creation of the .gz archvie file.

SEP

[Sridhar Bhaskarla · Accepted solution]

Hi,

I have seen these issues before because of various reasons like NFS mount available anymore etc., You can look at install.log on the ignite server for more details. Since the archive loading is 100% complete, you may proceed with pushing the shell (y) and then ignore the error by exiting the shell with 2.

-Sri

[Michael Roberts_3]

The problem is caused by the location SYSCMDS places print_manifest, and is indicated by the 'File exists' message:

* Fri Sep 24 16:27:34 EDT 2004: Starting archive load of the source
(Recovery Archive).
pax_iux: opt/ignite/bin : File exists
* Processed 10% of archive

This Ignite defect is fixed in the 'C' version of Ignite that will be available by Dec 2004.

There is a workaround attached.