HP DL785 Sun Solaris 10 Deployment Guide for HP ProLiant Servers - Page 46

• 252-The sol.sh script was unable to copy multiboot and/or x86.miniroot to the temporary disk partition. • 253-The sol.sh script was unable to mount the temporary disk partition. • 254-The $dist parameter was not specified in the Create Boot Environment task script. Verify the setting in the task script. Installation terminates prematurely If installation is reporting No disks found, verify that the CPQary3 package is installed in the miniroot (for more information, see "Miniroot preparation") and use ORCA to verify that at least one logical drive has been created. If installation is reporting Unable to configure network interface, verify that any necessary NIC drivers have been installed in the miniroot. If using JumpStart or a custom ISO, verify that your deployment configuration includes or targets the correct miniroot on the GRUB module line. If using Rapid Deployment Pack or booting a custom ISO, verify that the HPQnetstrategy package is installed in the miniroot, and that a netstrategy parameter has been given on the GRUB kernel line. For more information, see "Miniroot preparation" and "GRUB preparation." If booting a JumpStart installation from iLO virtual media using a custom ISO, and installation is reporting an error similar to Could not preserve type 79 fdisk partition (c0t0d0), but has selected a different root disk, then the partition that is causing the error (c0t0d0 in this case) is most likely the virtual media. Add a dontuse keyword to the JumpStart profile to cause the installation to ignore the virtual media partition. 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. For more information, see "JumpStart preparation." Troubleshooting 46