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

GRUB cannot boot Solaris, JumpStart deployment ignores GRUB command line arguments - server error no video

Get HP DL785 - ProLiant - G5 PDF manuals and user guides
UPC - 883585262809
View all HP DL785 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

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. JumpStart deployment ignores GRUB command line arguments The installation setup script, add_install_client, has produced an invalid menu.lst. See "DHCP/PXE preparation" for resolution. 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 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 "Rapid Deployment Pack 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. Troubleshooting 45

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
Troubleshooting 45
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.
JumpStart deployment ignores GRUB command line arguments
The installation setup script,
add_install_client,
has produced an invalid
menu.lst
.
See
“DHCP/PXE preparation” for resolution.
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 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 “Rapid Deployment Pack 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.