Specific Installation Errors

Error: Unknown client "host_name"

Reason Error Occurred	How to Fix the Problem
The host_name argument in the add_install_client command must be a host in the name service.	Add the host host_name to the NIS or NIS+ name service. (Either update the NIS maps or populate the NIS+ tables.) Try executing the add_install_client command again.

le0: No carrier - transceiver cable problem

Reason Error Occurred	How to Fix the Problem
This system is not connected to the network.	If this is a non-networked system, ignore this message. If this is a networked system, make sure the Ethernet cabling is attached securely.

No network boot server. Unable to install the system. See installation instructions.

Reason Error Occurred	How to Fix the Problem
This error occurs on a system that you are attempting to install using custom JumpStart. The system could not find a local Solaris CD or an install server on the network.	The system administrator must set up an install server to be used for custom JumpStart installation (see "Creating an Install Server" on page 24). Otherwise, you must do an interactive installation, as documented in Chapter 8, "Booting and Installing Solaris: Interactive."

prom_panic: Could not mount filesystem

Reason Error Occurred	How to Fix the Problem
This error occurs when you are doing a network installation, but the boot software cannot locate the Solaris installation image (either the Solaris CD or a copy of the Solaris CD on the install server).	Make sure that the installation software is mounted and shared. If installing from the install server's CD-ROM drive, make sure the Solaris CD is inserted in the CD-ROM drive, is mounted, and shared in the /etc/dfs/dfstab file. If installing from a copy of the Solaris CD on the install server's disk, make sure the directory path to the copy is shared in the /etc/dfs/dfstab file.

The file just loaded does not appear to be executable

Reason Error Occurred	How to Fix the Problem
This message cannot find the proper media for booting.	Verify that you are using the correct boot command for your system. If installing from a CD-ROM drive, make sure the Solaris CD is in the CD-ROM drive and that the CD-ROM drive is mounted. See the table for boot commands on page 136.

Timeout waiting for ARP/RARP packet...

Reason Error Occurred	How to Fix the Problem
The client is trying to boot over the network, but it cannot find a system that knows about it.	Verify the system's host name is in the NIS or NIS+ name service. Also, verify the bootparams search order in the /etc/nsswitch.conf file. For example, the following line in the /etc/nsswitch.conf file indicates the software will first look in the NIS maps for bootparams information. If not found there, software will look in the /etc/bootparams file. bootparams: nis files

WARNING: clock gained xxx days -- CHECK AND RESET DATE!

Reason Error Occurred	How to Fix the Problem
This is an informational message.	Ignore the message and continue with the installation.

General Installation Problems

Problem	How to Fix the Problem
The system boots over the network, but from a system other than the specified install server.	On the name server, update the /etc/bootparams entry for the system being installed. The entry should conform to the following syntax: install_system root=boot_server:path install=install_server:path

Problem	How to Fix the Problem
After you set up an install server and configure the system to install over the network, the system still does not boot.	Be sure the tftpd daemon is running on the install server. Type the following command and press Return: ps -ef | grep tftpd If this command does not return a line indicating the tftpd daemon is running, edit the /etc/inetd.conf file and remove the comment (#) character from the following line: #tftp dgram udp wait root/usr/sbin/in.tftpd in.tftpd -s /tftpboot After making this change, try booting the system again.

Problem	How to Fix the Problem
OpenWindows is not available to diskless and dataless clients.	The /usr/openwin may be on a separate, mounted file system. This directory is not automatically shared by admintool. The /usr/openwin file system must be manually added to the server's /etc/dfs/dfstab file and the file system must be shared. The entry looks like this: share -F nfs /usr/openwin Also, an explicit mount of the file system must be made in the client's /etc/vfstab file using the following: server_name:/usr/openwin - /usr/openwin nfs - yes -

Problem	How to Fix the Problem
Several processes that normally run when booting the system are not run when the system boots from the CD. (This is done to enable the system to boot and the Solaris installation program to run with only 16 Mbytes of memory.)	To boot from the CD to do disaster recovery (that is, restoring the root file system), you need to add functionality normally provided when booting. To provide this functionality, a script is provided, /sbin/setup_cd, which can be run to perform the additional setup that might be needed to do disaster recovery. setup_cd does the following tasks: - Finishes setting up the device file system for tapes and ports - Enables routing - Enables multicast - Invokes the statd(1M) daemon - Invokes the lockd(1M) daemon - Starts the automounter Note that if setup_cd is run on a 16 Mbyte system, it may not be possible to run suninstall or other programs that need more memory. If a disk with a swap partition is available, the system administrator could avoid this problem by using the swap(1M) command to add swap space to the system before invoking setup_cd. When booting from the CD during disaster recovery, it is possible to boot the system in single user mode from the CD. For example: boot cdrom -s

Problem	How to Fix the Problem
An installation using the upgrade option fails for reasons beyond your control, such as a power failure or a network connection failure. The system may be in an unbootable state.	1. Reboot the system from the Solaris CD or from the network. 2. Choose the upgrade option for installation. The Solaris installation program will determine if the system has been partially upgraded and will continue the upgrade.