test

Solaris 9 Installation Guide

Problems With Booting a System

Booting From Media, Error Messages


le0: No carrier - transceiver cable problem

Cause:

The system is not connected to the network.

Solution:

If this is a non-networked system, ignore this message. If this is a networked system, ensure that the Ethernet cabling is attached securely.


The file just loaded does not appear to be executable

Cause:

The system cannot find the proper media for booting.

Solution:

Verify that the system has been set up properly to install the Solaris 9 software from the network from an install server. For example, ensure that you specified the correct platform group for the system when you set it up.

Or, if you did not copy the images of the Solaris 9 DVD or Solaris 9 Software 1 of 2, Solaris 9 Software 2 of 2, and Solaris 9 Languages CDs to the install server, ensure the Solaris 9 DVD or Solaris 9 Software 1 of 2 CD is mounted and accessible on the install server.


boot: cannot open /kernel/unix

Cause:

This error occurs when you override the location of the boot - file by explicitly setting it to /kernel/unix.

Solution:

  • Reset the boot -file in the PROM to " " (blank).

  • Ensure that the diag-switch is set to off and to true.


Can't boot from file/device

Cause:

The installation media cannot find the bootable media.

Solution:

Ensure that the following conditions are met:

  • The DVD-ROM or CD-ROM drive is installed properly and turned on.

  • Solaris 9 DVD or the Solaris 9 Software 1 of 2 CD is inserted into the drive.

  • The disc is free of damage or dirt.


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

Description:

This is an informational message.

Solution:

Ignore the message and continue with the installation.

Booting From Media, General Problems


The system does not boot.

Description:

When initially setting up a custom JumpStart server, you might encounter boot problems that do not return an error message. To verify information about the system and how the system is booting, run the boot command with the -v option. When you use the -v option, the boot command displays verbose debugging information on the screen.

Note -

If this flag is not given, the messages are still printed, but the output is directed to the system logfile. For more information, see syslogd(1M).

Solution:

At the ok prompt, type the following: ok boot net -v - install.


Boot from DVD media fails on systems with Toshiba SD-M 1401 DVD-ROM

If your system has a Toshiba SD-M1401 DVD-ROM with firmware revision 1007, the system cannot boot from the Solaris 9 DVD.

Solution:

Apply patch 111649-03, or later version, to update the Toshiba SD-M1401 DVD-ROM drive's firmware. Patch 111649-03 is included on the Solaris 9 Supplement CD.

Booting From the Network, Error Messages


WARNING: getfile: RPC failed: error 5 (RPC Timed out).

Description:

This error occurs when you have two or more servers on a network responding to an install client's boot request. The install client connects to the wrong boot server, and the installation hangs. The following specific reasons might cause this error to occur:

Cause:

Reason 1:/etc/bootparams files might exist on different servers with an entry for this install client.

Solution:

Reason 1: Ensure that servers on the network do not have multiple /etc/bootparams entries for the install client. If they do have multiple entries, remove duplicate client entries in the /etc/bootparams file on all install servers and boot servers except the one you want the install client to use.

Cause:

Reason 2: Multiple /tftpboot or /rplboot directory entries might exist for this install client.

Solution:

Reason 2: Ensure that servers on the network do not have multiple /tftpboot or /rplboot directory entries for the install client. If they do have multiple entries, remove duplicate client entries from the /tftpboot or /rplboot directories on all install servers and boot servers except the one you want the install client to use.

Cause:

Reason 3: An install client entry might exist in the /etc/bootparams file on a server and an entry in another /etc/bootparams file that enables all systems to access the profile server. Such an entry resembles the following: 

* install_config=profile_server:path

A line that resembles the previous entry in the NIS or NIS+ bootparams table can also cause this error.

Solution:

Reason 3: If a wildcard entry is in the name service bootparams map or table (for example, * install_config=), delete it and add it to the /etc/bootparams file on the boot server.


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

Cause:

This error occurs on a system that you are attempting to install from the network. The system is not set up correctly.

Solution:

Ensure that you correctly set up the system to install from the network. See "Adding Systems to Be Installed From the Network".


prom_panic: Could not mount file system

Cause:

This error occurs when you are installing Solaris 9 from a network, but the boot software cannot locate the following:

  • Solaris 9 DVD, either the DVD or a copy of the DVD image on the install server

  • Solaris 9 Software 1 of 2 CD image, either the Solaris 9 Software 1 of 2 CD or a copy of the Solaris 9 Software 1 of 2 CD image on the install server

Solution:

Ensure that the installation software is mounted and shared.

  • If you are installing Solaris 9 from the install server's DVD-ROM or CD-ROM drive, ensure that the Solaris 9 DVD or Solaris 9 Software 1 of 2 is inserted in the CD-ROM drive, is mounted, and is shared in the /etc/dfs/dfstab file.

  • If installing from a copy of the Solaris 9 DVD image or Solaris 9 Software 1 of 2 CD image on the install server's disk, ensure that the directory path to the copy is shared in the /etc/dfs/dfstab file.

See the man page, install_server.


Timeout waiting for ARP/RARP packet...

Cause:

Reason 1: The client is trying to boot from the network, but it cannot find a system that knows about the client.

Solution:

Reason 1: Verify the system's host name is in the NIS or NIS+ name service. Also, verify the bootparams search order in the boot server's /etc/nsswitch.conf file.

For example, the following line in the /etc/nsswitch.conf file indicates that JumpStart or the Solaris suninstall program first looks in the NIS maps for bootparams information. If the program does not find any information, the JumpStart program or the Solaris suninstall program looks in the boot server's /etc/bootparams file.

bootparams: nis files
Cause:

Reason 2: The client's Ethernet address is not correct.

Solution:

Reason 2: Verify that the client's Ethernet address in the install server's /etc/ethers file is correct.

Cause:

Reason 3: In a custom JumpStart installation, the add_install_client command specifies the platform group that uses a specified server as an install server. If the wrong architecture value is used when using the add_install_client, this problem occurs. For example, the machine you want to install is a sun4u, but you used sun4m instead.

Solution:

Reason 3: Rerun add_install_client with the correct architecture value.

Booting From the Network, General Problems


The system boots from the network, but from a system other than the specified install server.

Cause:

An /etc/bootparams and perhaps /etc/ethers entry exist on another system for the client.

Solution:

On the name server, update the /etc/bootparams entry for the system that is being installed. The entry should conform to the following syntax: 

install_system root=boot_server:path install=install_server:path

Also, ensure that only one bootparams entry is on the subnet for the install client.


After you set up an install server and configure the system to install Solaris 9 from the network, the system still does not boot.

Cause:

The tftpd might not be running on the install server.

Solution:

Be sure the tftpd daemon is running on the install server. Type the following command: 


# ps -ef | grep tftpd

If this command does not return a line that indicates that 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.