Sharing the Jumpstart Installation image with write permissions causes corruption to the image and errors on Jumpstart clients
Last updated on SEPTEMBER 22, 2014
Applies to:Solaris SPARC Operating System - Version: 8.0
Sharing with Read/Write permissions will cause jumpstart installation errors and corruption to the installation image.
While the jumpstart directory is shared Read/Write, jumpstart installations may appear to be successful but the reboot may show a "bad address" message while configuring the network interface (See Example 1 below for details). Also, the /etc/hosts file may be missing the loghost entry (See Example 2 below for details).
Corruption to the etc/path_to_inst file may cause various low level boot problems. Theses could occur just after the OBP banner through to single or multiuser.
When using a Solaris[TM] Volume Manager (SVM) installation profile with Solaris[TM] 9 4/04 or later, the initial reboot of the client will panic (See Example 5 below).Sharing the jumpstart image directory back as read only (share -F nfs -o ro,anon=0 /filesystem) is not the complete solution. The jumpstart image has been corrupted. There is corruption to the etc directory structure but may not be limited to etc. The links to the hosts and netmasks files within etc/inet directory were removed and replaced by hard coded files from the jumpstart client installation.
See the Examples below for more details.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms