| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris 11 Express Automated Installer Guide Oracle Solaris 11 Express 11/10 |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris 11 Express Automated Installer Guide Oracle Solaris 11 Express 11/10 |
1. Automated Installer Overview
2. Setting Up an AI Install Server
4. Specifying Installation Instructions
5. Configuring the Client System
8. Automated Installations That Boot From Media
A. Troubleshooting Automated Installations
SPARC Network Booting Errors and Possible Causes
Timed out Waiting for BOOTP/DHCP Reply
Internal Server Error or WAN Boot Alert
Error Message 403: Forbidden or 404 Not Found
x86 Network Booting Errors and Possible Causes
No DHCP or Proxy DHCP Offers Were Received
TFTP Error or System Hangs After GATEWAY Message
System Hangs After GRUB Menu Entry is Selected
HTTP Request Sent Results in 403 Forbidden or 404 Not Found
Automated Installation Failed Message
Run Automated Installations in Debug Verbose Mode
Boot SPARC Systems in Debug Mode
Boot x86 Systems in Debug Mode
Boot the Install Environment Without Starting an Installation
Start Installation After Booting Without Initiating an Installation
This section suggests actions to take if a client installation fails.
If an installation to a client system failed, you can find the log at /tmp/install_log.
The install client needs to reach the IPS repository defined in the AI manifest in order to install the Oracle Solaris OS. In a normal configuration, the DHCP server sends the DNS information to the client. This DNS information is used to resolve the IPS repository name to an IP address.
A failed installation can result in an error message. See the following sample error message:
<OM Nov 2 06:56:32> Creating and configuring pkg(5) image area...
<TRANSFER_MOD Nov 2 06:56:32> pkg cmd: /usr/bin/pkg image-create
-f -F -p example.com=http://pkg.example.com/release /a
<TRANSFER_MOD_E Nov 2 06:56:35>
<TRANSFER_MOD_E Nov 2 06:56:35>
<TRANSFER_MOD_E Nov 2 06:56:35> pkg image-create: The URI
'http://pkg.example.com/release' does not appear to point to a valid pkg server.
<TRANSFER_MOD_E Nov 2 06:56:35> Please check the server's address and client's
network configuration.
<TRANSFER_MOD_E Nov 2 06:56:35> Additional details:
<TRANSFER_MOD_E Nov 2 06:56:35>
<TRANSFER_MOD_E Nov 2 06:56:35> Unable to contact valid package server
<TRANSFER_MOD_E Nov 2 06:56:35> Encountered the following error(s):
<TRANSFER_MOD_E Nov 2 06:56:35> Unable to contact any configured publishers.
This is likely a network configuration problem.
<TRANSFER_MOD_E Nov 2 06:56:35> Unable to initialize the pkg image area at /a
...
<AI Nov 2 06:56:36> Automated Installation failed in Transfer module
<AI Nov 2 06:56:36> Transferring the files from the source failed.
Please see previous messages for more details
This error indicates that the client could not resolve the name of the IPS repository. On the failed machine, try to reach the IPS repository. This output shows that the repository this client installation is trying to reach is http://pkg.example.com/release.
Check whether the client can ping the repository:
$ ping pkg.example.com
If the ping command returns the following output, the error might be a connectivity problem:
no answer from pkg.example.com
If the ping command returns the following output, the error might be a DNS problem:
ping: unknown host pkg.example.com
Check whether DNS is configured on your client by verifying that a non-empty /etc/resolv.conf file exists.
If /etc/resolv.conf does not exist or is empty, check that your DHCP server is providing DNS server information to the client:
# /sbin/dhcpinfo DNSserv
If this command returns nothing, the DHCP server is not set up to provide DNS server information to the client. Contact your DHCP administrator to correct this problem.
If an /etc/resolv.conf file exists and is properly configured, check for the following possible problems and contact your system administrator for resolution:
The DNS server might not be resolving your IPS repository server name.
No default route to reach the DNS server exists.
Review the following additional information about errors that occur when the client system is booting.
This section describes errors or problems you might see when booting a SPARC client over the network and possible causes.
If a DHCP server is not responding to a SPARC client's request, the following messages display:
... OpenBoot 4.23.4, 8184 MB memory available, Serial #69329298. Ethernet address 0:14:4f:21:e1:92, Host ID: 8421e192. Rebooting with command: boot net:dhcp - install Boot device: /pci@7c0/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up Timed out waiting for BOOTP/DHCP reply Timed out waiting for BOOTP/DHCP reply Timed out waiting for BOOTP/DHCP reply Timed out waiting for BOOTP/DHCP reply
The timeout message indicates that the client is sending a DHCP request, and no response has been made to that request. This error is probably caused by a DHCP configuration problem. Check whether your client is configured correctly in the DHCP server.
If the AI client starts downloading the boot_archive, but then fails with the error, “Boot load failed,” that indicates that the client DHCP information is configured incorrectly.
Rebooting with command: boot net:dhcp - install Boot device: /pci@7c0/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up HTTP: Bad Response: 500 Internal Server Error Evaluating: Boot load failed
This error could happen if another DHCP server is responding to the client. Check the DHCP configuration for this client. If the configuration appears to be correct, determine whether there is another DHCP server in the subnet. If you are running the Oracle Solaris DHCP server, you can run the DHCP daemon in debug mode with the command:
# /usr/lib/inet/in.dhcpd -dv
After the AI client has obtained the IP address and initial parameters to start downloading the boot archive, the client might be unable to find or download the boot_archive.
If the client cannot find the boot_archive, the following error is displayed.
Rebooting with command: boot net:dhcp - install
Boot device: /pci@7c0/pci@0/network@4:dhcp File and args:
1000 Mbps FDX Link up
<time unavailable> wanboot info: WAN boot messages->console
<time unavailable> wanboot info: Starting DHCP configuration
<time unavailable> wanboot info: DHCP configuration succeeded
<time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%)
<time unavailable> wanboot info: wanbootfs: Download complete
Tue Aug 5 20:46:43 wanboot alert: miniinfo: Request returned code 500
Tue Aug 5 20:46:44 wanboot alert: Internal Server Error \
(root filesystem image missing)If the AI client finds the boot_archive file but cannot access the file, then the following error is displayed.
Rebooting with command: boot net:dhcp - install
Boot device: /pci@7c0/pci@0/network@4:dhcp File and args:
1000 Mbps FDX Link up
<time unavailable> wanboot info: WAN boot messages->console
<time unavailable> wanboot info: Starting DHCP configuration
<time unavailable> wanboot info: DHCP configuration succeeded
<time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%)
<time unavailable> wanboot info: wanbootfs: Download complete
Tue Aug 5 20:53:02 wanboot alert: miniroot: Request returned code 403
Tue Aug 5 20:53:03 wanboot alert: ForbiddenFor both of these problems, fix the boot_archive file configured for this client. Check the path name and permissions of the boot_archive at $IMAGE/boot/boot_archive.
These messages, “ERROR 403: Forbidden” and “ERROR 404: Not Found” can be seen if the AI client successfully downloads the boot_archive and boots the Oracle Solaris kernel, but fails to get one of the image archives. An error message is displayed indicating which file is causing the problem. For example, in the following output, the solaris.zlib file does not exist or is not accessible at the specified location.
Rebooting with command: boot net:dhcp - install
Boot device: /pci@7c0/pci@0/network@4:dhcp File and args:
1000 Mbps FDX Link up
1000 Mbps FDX Link up
<time unavailable> wanboot info: WAN boot messages->console
<time unavailable> wanboot info: Starting DHCP configuration
<time unavailable> wanboot info: DHCP configuration succeeded
<time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%)
<time unavailable> wanboot info: wanbootfs: Download complete
Tue Aug 5 21:43:37 wanboot progress: miniroot: Read 165251 of 165251 kB (100%)
Tue Aug 5 21:43:38 wanboot info: miniroot: Download complete
SunOS Release 5.11 Version snv_151 64-bit
...
Hostname: solaris
Remounting root read/write
Probing for device nodes ...
Preparing automated install image for use
Downloading solaris.zlib archive
--15:40:37-- http://10.6.35.226:5555//export/home/images/ai_sparc_111/solaris.zlib
=> `/tmp/solaris.zlib'
Connecting to 10.6.35.226:5555... connected.
HTTP request sent, awaiting response... 403 Forbidden
15:40:37 ERROR 403: Forbidden.
FAILED
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
This problem can be caused by one of the following conditions.
The image path configured in WAN boot is not correct.
The image path does not exist or is incomplete.
Access is denied due to permission issues.
Check your DHCP configuration or the contents of the target directory you specified when you ran installadm create-service. Check your WAN boot configuration.
When installing the Oracle Solaris OS on your client system, you need to include the install argument when you boot, as follows, in order to initiate an installation.
ok> boot net:dhcp - install
If you booted without the install boot argument, the SPARC client boots into the automated installer boot image, but the installation does not start. The following message is displayed.
Auto-installer disabled. Enable the auto-installer service by running the following command: svcadm enable svc:/application/auto-installer:default
To start an automated installation, you can log in and enable the install service as shown in the message, or you can reboot your system using the command shown above with the install argument.
This section describes errors or problems you might see when booting an x86 client over the network and possible causes.
If a DHCP server is not responding to an x86 client's request, you see the following messages:
Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86) Copyright(C) 1997-2007, Intel Corporation CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400 DHCP......... No DHCP or ProxyDHCP offers were received PXE-MOF: Exiting Intel Boot Agent
The timeout message indicates that the client is sending a DHCP request and not getting a response. This issue is probably due to an error in the DHCP configuration. Check to see if your client is configured correctly in the DHCP server.
The DHCP server provides an IP address and a location of the initial boot program as part of the DHCP response.
If the boot program does not exist, then the AI client boot cannot proceed. The following message is displayed:
Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86)
Copyright(C) 1997-2007, Intel Corporation
CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400
CLIENT IP: 10.6.68.29 MASK: 255.255.255.0 DHCP IP: 10.6.68.49
GATEWAY: 10.6.68.1
TFTP.
PXE-T02: Access Violation
PXE-E3C: TFTP Error - Access violation
PXE-MOF: Exiting Intel Boot AgentIf the boot program exists, but it is an incorrect program, the AI client hangs after displaying this message:
Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86)
Copyright(C) 1997-2007, Intel Corporation
CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400
CLIENT IP: 10.6.68.29 MASK: 255.255.255.0 DHCP IP: 10.6.68.49
GATEWAY: 10.6.68.1If the client is able to do the initial boot, but the kernel cannot be booted, the system hangs after you select the entry from the GRUB menu.
On the install server, check whether the menu.lst file for this client is pointing to a valid boot archive. The boot directory of the image on the server should be loop-back mounted under the /tftpboot directory as shown in this sample excerpt from df -k:
/export/home/images/osol-1003-ai-x86/boot \ 60450439 21678071 38772368 36% /tftpboot/I86PC.Solaris-12
I86PC.Solaris-12 is a sample. The number might vary on your system.
If you know the name of the target directory that you used in the installadm create-service command, then you can use that information to determine whether that target directory is mounted. Also, check whether you can access the /tftpboot/I86PC.Solaris-12/boot_archive file.
On the install server, if one of the install programs is inaccessible or does not exist in the location specified in the menu.lst file under /tftpboot, then the client is able to boot, but is not able to download that file. An error message is displayed indicating which file is causing the problem. For example, in the following output, the solaris.zlib file does not exist at the specified location.
SunOS Release 5.11 Version snv_151 64-bit
...
Hostname: solaris
Remounting root read/write
Probing for device nodes ...
Preparing automated install image for use
Downloading solaris.zlib archive
--15:40:37-- http://10.6.35.226:5555//export/home/images/ai_x86_111/solaris.zlib
=> `/tmp/solaris.zlib'
Connecting to 10.6.35.226:5555... connected.
HTTP request sent, awaiting response... 403 Forbidden
15:40:37 ERROR 403: Forbidden.
FAILED
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Check the contents of the target directory that you specified when you ran the installadm create-service command.
When installing the Oracle Solaris OS on x86 client systems for installations that boot over the network, you must select the second entry in the GRUB boot menu to initiate an automated installation. Typically, the menu entries display as follows:
Oracle Solaris 11 Express boot image Oracle Solaris 11 Express Automated Install
If you selected the first GRUB menu entry, or allowed the prompt to time out, the system boots into the automated install boot image, but the installation does not start. The following message is displayed:
Auto-installer disabled. Enable the auto-installer service by running the following command: svcadm enable svc:/application/auto-installer:default
To start an automated installation, you can log in and enable the install service as shown in the message, or you can reboot your system and select the second menu entry.
The following errors are common to both SPARC and x86 installations.
If there is a failure during installation, then the following message is displayed:
Automated Installation failed. Please refer to /tmp/install_log file for details Apr 9 14:28:09 solaris svc.startd[7]: application/auto-installer:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
If there is a failure during installation, check the log file, /tmp/install_log. If the AI client could not access the package server for installing packages, you might see the following error messages:
installation will be performed from http://pkg.oracle.com/ (solaris)
list of packages to be installed is:
entire
babel_install
pkg: The URL 'http://pkg.oracle.com/' does not appear to point to a
valid pkg server.
Please check the server's address and client's network configuration.
Additional details:
Unable to contact valid package server: http://pkg.oracle.com/
Encountered the following error(s):
Transport errors encountered when trying to contact depot server.
Reported the following errors:
Could not retrieve versions from 'solaris'
URLError, reason: (8, 'node name or service name not known')
Unable to initialize the pkg image area at /a
The problem might be caused by one of the following issues:
The pkg_server is down. Try to access the pkg_server and check status.
If you are using DNS, check whether the AI client is set up with DNS. See Check DNS.
If one of the packages specified in the AI manifest cannot be located in the IPS repositories, then the installer fails before installing any packages on the disk. In the following example, the installer could not find the package, SUNWTestPkg, in the IPS repository. You might see the following error message in the install_log:
<AI Feb 12 20:15:40> installation will be performed from
http://pkg.oracle.com/solaris/release (solaris)
<AI Feb 12 20:15:40> list of packages to be installed is:
<AI Feb 12 20:15:40> entire
babel_install
<AI Feb 12 20:15:40> SUNWTestPkg
<OM Feb 12 20:15:40> Set zfs root pool device
<OM Feb 12 20:15:40> creating zpool
<OM Feb 12 20:15:43> /usr/sbin/zfs get -Hp -o value available rpool
<OM Feb 12 20:15:43> Creating swap and dump on ZFS volumes
<OM Feb 12 20:16:00> TI process completed successfully
<OM Feb 12 20:16:00> Transfer process initiated
<TRANSFERMOD Feb 12 20:16:59> IPS initialization finished
<TRANSFER_MOD Feb 12 20:52:33> pkg missing
<TRANSFERMOD Feb 12 20:52:33> IPS transfer failed
<TRANSFERMOD Feb 12 20:52:33> IPS transfer finished
<OM Feb 12 20:52:33> Transfer failed with error 15
<AI Feb 12 20:52:42> om_perform_install failed with error 114
<AI Feb 12 20:52:42> Auto install failed
Check whether the package in question is a valid package. If this package is available on a different IPS repository, add that IPS repository in the AI manifest by using the <source> tag.
|