This chapter contains a list of specific error messages and general problems you might encounter when installing Solaris 8 software and explains how to fix the problems. Start by using this list of sections in this chapter to determine where in the installation process the problem occurred.
Error: Unknown client “host_name” |
Problem |
How to fix the problem |
---|---|
The host_name argument in the add_install_client command is not a host in the name service. |
Add the host host_name to the NIS or NIS+ name service and execute the add_install_client command again. |
le0: No carrier - transceiver cable problem |
Problem |
How to fix the problem |
---|---|
The 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. |
The file just loaded does not appear to be executable |
Problem |
How to fix the problem |
---|---|
The system cannot find the proper media for booting. |
Verify that the system has been set up properly to install Solaris 8 over the network from an install server. For example, make sure you specified the right platform group for the system when you set it up. Also, if you did not copy the images of the CDs labeled Solaris 8 Software 1 of 2, Solaris 8 Software 2 of 2, and Solaris 8 Languages to the install server, make sure the CD labeled Solaris 8 Software 1 of 2 is mounted and accessible on the install server. |
boot: cannot open /kernel/unix |
Can't boot from file/device |
WARNING: clock gained xxx days -- CHECK AND RESET DATE! |
Problem |
How to fix the problem |
---|---|
SPARC based systems only This is an informational message. |
Ignore the message and continue with the installation. |
Not a UFS filesystem |
Problem |
How to fix the problem |
---|---|
IA based systems only When Solaris 8 software was installed (either through the Solaris 8 Interactive Installation Program or custom JumpStart), the default boot drive was not selected. When an alternate boot disk is selected, you must use the diskette labeled Solaris 8 Device Configuration Assistant Intel Platform Edition to boot the system from that point on. |
Insert the diskette labeled Solaris 8 Device Configuration Assistant Intel Platform Edition into the system's boot diskette drive (usually the A: drive). |
Problem |
How to fix the problem |
---|---|
IA based systems only The IDE BIOS primary drive on your system was not detected by the Solaris 8 Device Configuration Assistant during the pre-booting phase. |
|
Problem |
How to fix the problem |
---|---|
IA based systems only The IDE disk or CD-ROM drive on your system was not found by the Solaris 8 Device Configuration Assistant in the pre-booting phase. |
|
Problem |
How to fix the problem |
---|---|
IA based systems only The system hangs before displaying the system prompt. |
See the Solaris 8 (Intel Platform Edition) Hardware Compatibility List. |
WARNING: getfile: RPC failed: error 5 (RPC Timed out). |
No network boot server. Unable to install the system. See installation instructions. |
Problem |
How to fix the problem |
---|---|
SPARC based systems only This error occurs on a system that you are attempting to install over the network. The system is not set up correctly. |
Make sure you correctly set up the system to install over the network (see Adding Systems to Be Installed From the Network). |
prom_panic: Could not mount filesystem |
Problem |
How to fix the problem |
---|---|
SPARC based systems only This error occurs when you are installing Solaris 8 over a network, but the boot software cannot locate the Solaris 8 Software 1 of 2 CD image (either the CD labeled Solaris 8 Software 1 of 2 or a copy of the Solaris 8 Software 1 of 2 CD image on the install server). |
Make sure that the installation software is mounted and shared. If you are installing Solaris 8 from the install server's CD-ROM drive, make sure the CD labeled Solaris 8 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 8 Software 1 of 2 CD image on the install server's disk, make sure the directory path to the copy is shared in the /etc/dfs/dfstab file. |
Timeout waiting for ARP/RARP packet... |
ip: joining multicasts failed on tr0 - will use link layer broadcasts for multicast |
Requesting Internet address for Ethernet_Address |
Problem |
How to fix the problem |
---|---|
IA based systems only The client is trying to boot over the network, but it cannot find a system that knows about the client. |
Verify the system's host name is listed in the NIS or NIS+ 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... |
Still trying to find a RPL server... |
Problem |
How to fix the problem |
---|---|
IA based systems only The system is trying to boot over the network, but the server is not set up to boot this system. |
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. |
Problem |
How to fix the problem |
||
---|---|---|---|
IA based systems only After setting up an install server and configuring 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 Enter:
If this command does not return a line indicating the rpld daemon is running, execute the following command:
After making this change, try booting the system again. |
/cdrom/Solaris_2.x/SUNWxxxx/reloc.cpio: Broken pipe |
Problem |
How to fix the problem |
---|---|
Bug ID: 1212370 This error message does not affect the installation. |
Ignore the message and continue with the installation. |
WARNING: CHANGE DEFAULT BOOT DEVICE |
Problem |
How to fix the problem |
---|---|
IA based systems only The default boot device set in the system's BIOS might be set to a device that requires your using the Solaris 8 Device Configuration Assistant Intel Platform Edition diskette to boot the system. This is an informational message. |
Continue with the installation and, if necessary, change the system's default boot device specified in the BIOS after you install the Solaris software to a device that does not require the Solaris 8 Device Configuration Assistant Intel Platform Edition diskette. |
Problem |
How to fix the problem |
---|---|
IA based systems only IDE disk drives do not automatically map out bad blocks like other drives supported by Solaris software. Before installing Solaris 8 on an IDE disk, you might want to perform a surface analysis on the disk. |
To perform surface analysis on an IDE disk, follow this procedure:
IDE drives do not include a target number. The IDE drive naming convention is cxdy, where cx is the controller number and dy is the device number. |
|
|
No upgradeable disks |
Problem |
How to fix the problem |
---|---|
Bug ID: 1191792 A swap entry in the /etc/vfstab file is causing the upgrade to fail. |
Comment out the following lines in the /etc/vfstab file:
|
Problem |
How to fix the problem |
---|---|
The upgrade fails because the Solaris installation program could not mount metadevices on the system. |
Metadevices cannot be upgraded automatically. Instructions are provided in Solstice DiskSuite 4.2 Reference Guide. |
Problem |
How to fix the problem |
---|---|
Bug ID: 1170953 The upgrade option is not presented even though there is a version of Solaris software that's upgradable on the system. The following specific reasons might cause this problem: | |
Reason 1: The /var/sadm directory is a symlink or it is mounted from another file system. |
Solution for Reason 1: Move the /var/sadm directory into the root (/) or /var file system. |
Reason 2: The /var/sadm/softinfo/INST_RELEASE file is missing. |
Solution for Reason 2: Create a new INST_RELEASE file by using the following template: OS=Solaris VERSION=2.x REV=0 where x is the version of Solaris software on the system. |
Problem |
How to fix the problem |
---|---|
The upgrade fails for reasons beyond your control, such as a power failure or a network connection failure, and the system cannot be soft-booted. |
The Solaris installation program determines if the system has been partially upgraded and continues the upgrade. |
Problem |
How to fix the problem |
---|---|
The upgrade fails because the Solaris installation program cannot mount a file system. During an upgrade, the script attempts to mount all the file systems listed in the system's /etc/vfstab file on the root (/) file system being upgraded. If the installation script cannot mount a file system, it fails and exits. |
Make sure all file systems in the system's /etc/vfstab file can be mounted. Comment out any file systems in the /etc/vfstab file that can't be mounted or that might cause the problem so the Solaris 8 Interactive Installation Program doesn't try to mount them during the upgrade. Any system-based file systems that contain software to be upgraded (for example, /usr) cannot be commented out. |
Problem |
How to fix the problem |
---|---|
There is not enough space on the system for the upgrade. Check the following reasons for the space problem and see if you can fix it without using auto-layout to reallocate space: | |
Reason 1: Since the automounter is not active during an upgrade, the Solaris installation program installs any files or directories in a package that are symbolic links to automounted file systems. If a symbolic link is overwritten, the upgrade might fail because of insufficient disk space. The /var/mail and /var/news directories, which are usually located on an automounted file system, are not affected by an upgrade. |
Solution for Reason 1: During the upgrade, delete software packages in the Customize Software screen that create files or directories on the automounted file systems. Then the Solaris 8 Interactive Installation Program does not overwrite the symbolic link with the files or directories in the package. |
Reason 2: New software has been added to the software group that you are upgrading or some of the existing software has increased in size. During an upgrade, the Solaris 8 Interactive Installation Program installs any new software that is part of the software group previously installed on the system, and it also upgrades any existing packages on the system. |
Solution for Reason 2: During the upgrade, delete software packages in the Customize Software screen that install into the file systems that need more space. Especially look for any new packages that have been added to the Solaris release that the system doesn't need. |
Problem |
How to fix the problem |
---|---|
During an upgrade, a message is displayed regarding some of the packages (including SUNWolrte, SUNWoldcv, SUNWoldte, SUNWolaud). An example of this message is: Doing pkgadd of SUNWolrte to / |
This message indicates an attempt to install the same architecture and version of a package that is already installed. Installation of SUNWolrte was successful... No action is required; this message is informational only. |