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.