HP (Hewlett-Packard) 10 Manual De Usuario

 

 

Troubleshooting 37 

 

 

 

JumpStart reverts to interactive configuration 

If a JumpStart profile and a sysidcfg(4) file are provided, but the Solaris installation begins prompting you 
for information, then it either cannot find one of the files, one of the files has a syntax error, or the 

configuration is incomplete. 
To resolve this issue: 

1. 

Verify network connectivity to the JumpStart server. 

2. 

Verify the NFS pathnames in one of the following locations, as appropriate: 

○ 

add_install_client(1M) (if you are using PXE) 

○ 

GRUB (if you are using a custom ISO) 

○ 

Create Boot Environment task script (if you are using Rapid Deployment Pack) 

3. 

Verify that those paths can be mounted on the target server. Ensure that the directory specified by the 

sysid_config

 parameter contains a file named 

sysidcfg

. 

4. 

Verify the syntax of 

rules.ok

 and the profile file. The 

check

 script included on the Solaris media 

verifies 

rules

 and any profile files it specifies, and creates 

rules.ok

. 

5. 

Verify the syntax of 

sysidcfg

 and verify that all required information is provided. The example 

provided in this guide is complete for those Solaris releases to which this guide applies. 

Installation succeeds but server fails to boot 

If the system is not booting to GRUB, verify the standard boot order and boot controller order in RBSU. If 
booting from Smart Array, the Solaris root disk must be SCSI target 0, LUN 0 (that is, 

cxt0d0

). 

If the system is booting to GRUB, but reboots shortly after the Solaris copyright banner appears, then 

verify that the 

CPQary3

 package was installed to the disk during installation (for more information, see 

“JumpStart preparation”). Another symptom of this problem is the kernel debugger showing that Solaris is 
panicking with “cannot mount root.” 

Installation succeeds but no network availability after reboot 

If Solaris is unable to configure network interfaces after the post-installation reboot, see “Network 
configuration fails during interactive installation.” 
In addition, verify that all required NIC drivers were installed to the disk during installation. For more 

information, see “JumpStart preparation.”