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 nonnetworked 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
Express 5/07 software from the network from an install server. The following are
examples of checks you can make.
If you copied the images of the Solaris DVD or the Solaris Software CDs to the install server, ensure that you specified the correct platform group for the system when you set it up.
If you are using DVD or CD media, ensure that the Solaris DVD or Solaris Software - 1 CD is mounted and accessible on the install server.
boot: cannot open <filename> (SPARC based systems only)
Cause:
This error occurs when you override the location of the boot -file by
explicitly setting it.
Note - filename is a variable for the name of the file affected.
Solution:
Follow these instructions:
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 DVD or the Solaris Software - 1 CD is inserted into the drive.
The disc is free of damage or dirt.
WARNING: clock gained xxx days -- CHECK AND RESET DATE! (SPARC based systems only)
Description:
This is an informational message.
Solution:
Ignore the message and continue with the installation.
Not a UFS file system (x86 based systems only)
Cause:
When the current Solaris release was installed (either through the Solaris installation program
or custom JumpStart), no boot disk was selected. You now must edit the
BIOS to boot the system.
Solution:
Select the BIOS to boot. See your BIOS documentation for instructions.
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 about the screen.
Note - If this flag is not given, the messages are still printed, but the
output is directed to the system log file. For more information, see
syslogd(1M).
Solution:
For SPARC based systems, at the ok prompt, type the following command.
ok boot net -v - install
Boot from DVD media fails on systems with Toshiba SD-M 1401 DVD-ROM
Description:
If your system has a Toshiba SD-M1401 DVD-ROM with firmware revision 1007, the
system cannot boot from the Solaris DVD.
Solution:
Apply patch 111649–03, or later version, to update the Toshiba SD-M1401 DVD-ROM drive's
firmware. The patch 111649–03 is available at sunsolve.sun.com.
The system hangs or panics when nonmemory PC cards are inserted. (x86 based systems only)
Cause:
Nonmemory PC cards cannot use the same memory resources that are used by
other devices.
Solution:
To correct this problem, see the instructions for your PC card and check
for the address range.
The system hangs before displaying the system prompt. (x86 based systems only)
Solution:
You have hardware that is not supported. Check your hardware manufacturer's documentation.
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 naming 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.
(SPARC based systems only)
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 With a CD Image.
prom_panic: Could not mount file system (SPARC based systems only)
Cause:
This error occurs when you are installing Solaris from a network, but the
boot software cannot locate the following:
Solaris DVD, either the DVD or a copy of the DVD image on the install server
Solaris Software - 1 CD image, either the Solaris Software - 1 CD or a copy of the CD image on the install server
Solution:
Ensure that the installation software is mounted and shared.
If you are installing Solaris from the install server's DVD-ROM or CD-ROM drive, ensure that the Solaris DVD or Solaris Software - 1 CD 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 DVD image or Solaris Software - 1 CD image on the install server's disk, ensure that the directory path to the copy is shared in the /etc/dfs/dfstab file.
Use either the sharemgr utility or the share command as follows:
Using the share command, edit the /etc/dfs/dfstab file by adding the following entry.
# share -F nfs -o ro,anon=0 cdrom/xxx
Then, type shareall and press Enter.
Using the sharemgr utility, enter the following commands:
# sharemgr add-share -s /cdrom/xxx default
# sharemgr set -P nfs -S sys -p ro="*" -s /cdrom/xxx default
# sharemgr set -P nfs -p anon=0 -s /cdrom/xxx default
Timeout waiting for ARP/RARP packet...(SPARC based systems only)
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+ naming
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 installation program first looks in the NIS maps for bootparams
information. If the program does not find any information, the installer 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 i86pc instead.
Solution:
Reason 3: Rerun add_install_client with the correct architecture value.
ip: joining multicasts failed on tr0 - will use link layer broadcasts for
multicast (x86 based systems only)
Cause:
This error message is displayed when you boot a system with a token
ring card. Ethernet multicast and token ring multicast do not work the same
way. The driver returns this error message because an invalid multicast address was
provided to it.
Solution:
Ignore this error message. If multicast does not work, IP uses layer broadcasts
instead and does not cause the installation to fail.
Requesting Internet address for Ethernet_Address (x86 based systems only)
Cause:
The client is trying to boot from the network, but it cannot find
a system that knows about the client.
Solution:
Verify the system's host name is listed in the naming service. If the
system's host name is listed in the NIS or NIS+ naming service, and
the system continues to print this error message, try rebooting.
RPC: Timed out No bootparams (whoami) server responding; still trying... (x86 based systems only)
Cause:
The client is trying to boot from the network, but it cannot find
a system with an entry in the /etc/bootparams file on the install server.
Solution:
Use add_install_client on the install server. Using this command adds the proper entry
in the /etc/bootparams file, enabling the client to boot from the network.
Still trying to find a RPL server... (x86 based systems only)
Cause:
The system is trying to boot from the network, but the server is
not set up to boot this system.
Solution:
On the install server, execute add_install_client for the system to be installed.
The add_install_client command sets up an /rplboot directory, which contains the necessary network boot
program.
CLIENT MAC ADDR: FF FF FF FF FF FF (network installations with DHCP only)
Cause:
The DHCP server is not configured correctly. This error might occur if the
options or macros are not correctly defined in the DHCP Manager software.
Solution:
In the DHCP Manager software, verify that the options and macros are correctly
defined. Confirm that the Router option is defined, and that the value of
the Router option is correct for the subnet you are using for the
network installation.
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 an /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.
The system does not boot from the network (network installations with DHCP only).
Cause:
The DHCP server is not configured correctly. This error might occur if the
system is not configured as an installation client on the DHCP server.
Solution:
In the DHCP manager software, verify that installation options and macros are defined
for the client system. For more information, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).
