le0: No carrier - transceiver cable 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

The system cannot find the proper media for booting. 

Verify that the system has been set up properly to install 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 Solaris CD, make sure the Solaris CD on the install server is mounted and accessible.  

boot: cannot open /kernel/unix

SPARC-based systems only. 

This error occurs when you override the boot file location by explicitly setting it to /kernel/unix. In the Solaris 2.6 release, the kernel no longer resides in /kernel/unix, but in /platform/<arch>/kernel/unix.

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

Can't boot from file/device                                   

The installation program can't find the Solaris CD in the system's CD-ROM drive. 

Make sure: 

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

• The Solaris CD is inserted into the CD-ROM drive

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

SPARC-based systems only.  

This is an informational message. 

Ignore the message and continue with the installation. 

No upgradeable disks

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:

• All swap files and slices on disks not being upgraded

• Swap files that are no longer present

• Any unused swap slices

The upgrade fails because the installation program could not mount metadevices on the system. 

Metadevices cannot be upgraded automatically. For instructions, see Appendix B, "Upgrading to Other Solaris Versions," in the Solstice DiskSuite Reference Guide.

Bug ID: 1170953 

The upgrade option is not presented even though there is a version of Solaris software that's upgradable on the system. 

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.

The upgrade fails for reasons beyond your control, such as a power failure or a network connection failure, and the system is left in an unbootable state.

1. Reboot the system from the Solaris CD or from the network.

2. Choose the upgrade option for installation.

The Solaris Interactive Installation program will determine if the system has been partially upgraded and will continue the upgrade. 

The upgrade fails because the installation program could not mount a file system. During an upgrade, the installation program 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 program 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 may cause the problem, so the 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.

There is not enough space on the system for the upgrade. See if you can fix this problem without using auto-layout to rearrange space, by checking the following reasons for the space problem:

Reason 1: Since the automounter is not active during an upgrade, the installation program installs any package's files or directories that are symbolic links to automounted file systems. If a symbolic link is overwritten, the upgrade may fail because of insufficient disk space.

The /var/mail and /var/news directories, which usually reside 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 will create files or directories on the automounted file systems. Then the installation program will not overwrite the symbolic link with a package's files or directories.

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 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 you don't want.