Troubleshooting 35
To enable the Solaris debugger, add -k to the GRUB kernel line. When the debugger has assumed
control following the occurrence of a significant error, the ::msgbuf command displays the kernel
message buffer, the end of which contains the panic string, if any. The ::quit command reboots the
system.
Common problems
This section describes some symptoms encountered frequently during implementation of a deployment
environment, along with the possible causes of each. Use this section to determine where troubleshooting
efforts must be focused.
System does not boot to GRUB
If PXE booting, verify network connectivity and dhtadm(1M) usage, or the DHCP/TFTP server
configuration. Verify that the DHCP service is available on the same subnet. Also, verify using RBSU that
the correct NIC port is used for PXE boot and the correct Ethernet MAC address was given to
add_install_client(1M) and dhtadm. For more information, see “DHCP/PXE preparation.”
If booting from a custom ISO, verify mkisofs(8) usage and that stage2_eltorito is on the media. For
more information, see “Custom bootable ISO image creation.”
If booting from Smart Array, verify the boot controller order in RBSU. If installation is complete, verify that
the Solaris root disk is SCSI target 0, LUN 0 (that is, cxt0d0).
GRUB does not display a menu
Most likely, GRUB is unable to find its configuration file menu.lst.
If booting from PXE, verify add_install_client(1M) and dhtadm(1M) usage. The Ethernet MAC address
given to add_install_client is significant. For more information, see “DHCP/PXE preparation.”
If booting from a custom ISO, verify that the configuration file is in the proper location on the media (such
as /boot/grub/menu.lst). For more information, see “Custom bootable ISO image creation.”
GRUB cannot boot Solaris
To boot Solaris, GRUB must be able to access the multiboot program and the miniroot.
If booting from PXE, verify add_install_client(1M) usage. For more information, see “DHCP/PXE
preparation.”
If booting from a custom ISO, verify that multiboot and the miniroot are on the media and that the correct
pathnames are given to GRUB.
If booting a ProLiant server blade from a USB drive attached directly to the blade and GRUB is reporting
Cannot mount selected partition, verify that the drive in use is supported for use with blades.
