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 executableCause:
The system cannot find the proper media for booting.Solution:
Verify that the system has been set up properly to install the Solaris 10 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 10 DVD or the Solaris 10 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 10 DVD or Solaris 10 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.
filename is a variable for the name of the file affected.
Follow these instructions:
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/deviceCause:
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 10 DVD or the Solaris 10 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 Solaris 10 software was installed (either through the Solaris installation program or custom JumpStart), no boot disk was selected. You now must use the Solaris 10 3/05 Device Configuration Assistant diskette or edit the BIOS to boot the system.Solution:
Follow these instructions:
For the Solaris 10 3/05 release, insert the Solaris 10 3/05 Device Configuration Assistant diskette into the system's boot diskette drive (usually drive A). For information about accessing the Solaris 10 3/05 Device Configuration Assistant diskette, see Solaris 10 3/05 for x86: Copying the Boot Software to a Diskette.
Starting with the Solaris 10 1/06 release, select the BIOS to boot. See your BIOS documentation for instructions.
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.
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).
For SPARC based systems, at the ok prompt, type the following command.
ok boot net -v - install
For x86 based systems, when the installation program prompts you to “Select type of installation,” type the following command.
b - -v install
Boot from DVD media fails on systems with Toshiba SD—M 1401 DVD-ROMDescription:
If your system has a Toshiba SD-M1401 DVD-ROM with firmware revision 1007, the system cannot boot from the Solaris 10 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 IDE BIOS primary drive on your system was not detected by the Solaris 10 3/05 Device Configuration Assistant diskette during the pre-booting phase. (x86 based systems only)Solution:
Follow these instructions:
If you are using old drives, they might be unsupported. Check your hardware manufacturer's documentation.
Make sure the ribbon and power cables are connected correctly. Check the manufacturer's documentation.
If only one drive is attached to the controller, designate the drive as the master drive by setting jumpers. Some drives have different jumper settings for a single master, as opposed to a master operating with a slave. Connect the drive to the connector at the end of the cable to reduce signal ringing that occurs when an unused connector is dangling at the end of the cable.
If two drives are attached to the controller, designate one drive as the master by setting jumpers (or as a master operating with a slave), and set the second drive as a slave by setting jumpers.
If one drive is a hard disk and the second a CD-ROM drive, designate one drive as the slave drive by setting jumpers. You can designate either physical drive as the slave drive.
If problems persist with two drives on a single controller, attach one drive at a time to verify that each drive works. Designate the drive as master or single master by setting jumpers, and use the drive connector at the end of the IDE ribbon cable to attach the drive. Verify that each drive works, then set the jumpers for the drives back to a master and slave configuration.
If the drive is a disk drive, use the BIOS setup utility to ensure that the drive type (which indicates the number of cylinders, heads, and sectors) is configured correctly. Some BIOS software might have a feature that automatically detects the drive type.
If the drive is a CD-ROM drive, use the BIOS setup screen to configure the drive type as a CD-ROM drive, provided the BIOS software offers this capability.
For many systems, IDE CD-ROM drives are only recognized by MS-DOS if an MS-DOS CD-ROM driver has been installed. Try another drive.
The IDE disk or CD-ROM drive on your system was not found by the Solaris 10 3/05 Device Configuration Assistant diskette during the pre-booting phase. (x86 based systems only)Solution:
Follow these instructions:
For the Solaris 10 3/05 release, if disks are disabled in the BIOS, use the Solaris 10 3/05 Device Configuration Assistant diskette to boot from the hard disk. For information about accessing the Solaris 10 3/05 Device Configuration Assistant, see Solaris 10 3/05 for x86: Copying the Boot Software to a Diskette.
If the system has no disks, it might be a diskless client.
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.
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:
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. (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 10 DVD, either the DVD or a copy of the DVD image on the install server
Solaris 10 Software - 1 CD image, either the Solaris 10 Software - 1 CD or a copy of the CD image on the install server
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 10 DVD or Solaris 10 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 10 DVD image or Solaris 10 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.
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+ 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 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 filesCause:
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 name service. If the system's host name is listed in the NIS or NIS+ name 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:
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.
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.
An /etc/bootparams and perhaps an /etc/ethers entry exist on another system for the client.Solution:
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).