Filter
Top Products
Troubleshooting 36
System becomes unresponsive using remote console
Check for applicability of known issue iLO Boot Hang. For more information, see “iLO boot hang.”
If using a serial console (physical or virtual) and GRUB is not seen, verify that a splashimage is not
specified in menu.lst.
If using the browser-based iLO remote console, do not specify a tty console. The iLO remote console is the
server’s embedded video adapter.
Rapid Deployment Pack job fails
The sample Rapid Deployment Pack job for Solaris deployment is composed of multiple tasks, most of
which are common Rapid Deployment Pack tasks used in other types of deployments. The Create Boot
Environment task is unique to Solaris.
If the Create Boot Environment task is failing, use the reported error code or status value to determine the
cause. For additional information, see “RDP server preparation.”
Error codes include:
• 0—The task script completed successfully.
• 127—Occurs if the task script is unable to find the sol.sh script. Verify that sol.sh is available
on the deployment server.
• 250—The sol.sh script was unable to create the GRUB configuration file grub.conf.
• 251—The sol.sh script was unable to find multiboot and/or x86.miniroot in
...\osdist\$dist on the deployment server. Verify that these required files have been put on the
deployment server.
• 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 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.