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 correct platform group for the system when you set it up. 

Also, if you did not place an image of the Solaris 8 Installation English Intel Platform Edition or Solaris 8 Installation Multilingual Intel Platform Edition CD on the install server, make sure the Solaris 8 Installation English Intel Platform Edition or Solaris 8 Installation Multilingual Intel Platform Edition CD is mounted and accessible on the install server. 

Can't boot from file/device 

The installation program cannot find the Solaris 8 Installation English Intel Platform Edition or Solaris 8 Installation Multilingual Intel Platform Edition CD in the system's CD-ROM drive. 

Make sure: 

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

• The Solaris 8 Installation English Intel Platform Edition or Solaris 8 Installation Multilingual Intel Platform Edition CD is inserted into the CD-ROM drive

Not a UFS filesystem 

When Solaris software was installed (either through the interactive or custom JumpStart method), the default boot drive was not selected. When an alternate boot disk is selected, you must use the Solaris 8 Device Configuration Assistant to boot the system from that point on. 

Insert the diskette labeled Solaris 8 Device Configuration Assistant Intel Platform Edition or the CD labeled Solaris 8 Software 1 of 2 Intel Platform Edition into the system's boot diskette drive (usually the A: drive) or the CD-ROM drive, respectively. 

System hangs or panics when non-memory PC cards are inserted. 

Non-memory PC cards cannot use the same memory resources used by other devices. To correct this, use a DOS debugger to identify device memory usage, then manually reserve memory resources for the PC card device using the following instructions. 

1. Boot the system using the Solaris 8 Device Configuration Assistant.

2. When the Solaris Device Configuration Assistant screen is displayed, select F2_Continue.

   The Bus Enumeration screen is displayed, followed by the Scanning Devices screen. The system is scanned to identify system hardware. When scanning is finished, the Identified Devices screen is displayed.

3. Select F4_Device Tasks.

   The Device Tasks screen is displayed.

4. Select View/Edit Devices and then press F2_Continue.

   The View/Edit Devices screen is displayed.

5. Press F3_Add Device.

   The Add ISA Device screen is displayed.

6. Select Unsupported ISA device and then press F2_Continue.

   The Select Resource Types screen is displayed.

7. Select Memory and then press F2_Continue.

   The Specify Memory Resource screen is displayed.

8. Enter the address range to reserve (for example, CA800-CFFFF), and then press F2_Continue.

   The Select Resource Types screen is displayed.

9. Press F4_Add.

   The View/Edit Devices screen is displayed.

10. Press F2_Continue.

    The Device Tasks screen is displayed.

11. Select Save Configuration and then press F2_Continue.

    The Save Configuration screen is displayed.

12. Type the name you want to assign to the configuration and then press F2_Continue.

    The Device Tasks screen is displayed.

13. Press F3_Back.

    The Identified Devices screen is displayed.

14. Press F3_Back.

    The Solaris Device Configuration Assistant screen is displayed.

15. Press F2_Continue to continue booting your system.

The BIOS primary IDE drive on your system was not detected by the Solaris Device Configuration Assistant during the pre-booting phase. 

• The drive might be unsupported. Check the Solaris 8 (Intel Platform Edition) Hardware Compatibility List.

• Make sure the ribbon and power cables are plugged in 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, jumper one as master (or as master operating with a slave), and the second as slave.

• If one drive is a hard disk and the second a CD-ROM drive, designate the drive as the slave by setting jumpers. Any drive can be plugged into any connection on the cable.

• If there are persistent problems with two drives on a single controller, attach one drive at a time to verify that each works. Jumper the drive as master or single master and use the drive connector at the end of the IDE ribbon cable to attach the drive. Verify that each drive works, then jumper the drives back into 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 correctly configured. Some BIOS software automatically detects a drive type.

• If the drive is a CD-ROM drive, use the BIOS setup utility to configure the drive type as CD-ROM, if possible.

• If MS-DOS does not recognize the drive, there is probably a hardware or BIOS configuration problem. For many systems, IDE CD-ROM drives are only recognized by MS-DOS if an MS-DOS CD-ROM driver has been installed.

The IDE disk or CD-ROM drive on your system was not found by the Solaris Device Configuration Assistant in the pre-booting phase. 

• If IDE disks are disabled in the BIOS, use the Solaris Device Configuration Assistant to boot from the hard disk.

• If the system has no IDE disks, it might be a diskless client.

System hangs before displaying the prompt. 

See the Solaris 8 (Intel Platform Edition) Hardware Compatibility List.

IDE disk drives do not automatically map out bad blocks like other drives supported by Solaris software. Before installing Solaris on an IDE disk, you might want to perform a surface analysis on the disk.

To perform a surface analysis on an IDE disk: 

1. Start the Solaris 8 Interactive Installation Program. You interact with the program through a character user interface (CUI) or a graphical user interface (GUI) if your monitor supports it.

2. When the Solaris Interactive Installation dialog box is displayed, click Exit.

   A Warning dialog box is displayed.

3. Click Exit.

4. If you are using the GUI installation program, open a Command Tool window for the remaining steps. If you are using the CUI installation program, use the system shell for the remaining steps in this procedure.

5. Type format to start the format program.

6. Select the IDE disk drive on which you want to perform a surface analysis.

   ---

   Note -

   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.

   ---

7. At the format> prompt, type fdisk. Use the fdisk program to create a Solaris partition on the disk. (If a Solaris fdisk partition already exists, leave it alone.)

8. At the format> prompt, type analyze.

9. At the analyze> prompt, type config. This command shows you the current settings for a surface analysis. If you want to change any settings, type setup.

10. At the analyze> prompt, type read, write, or compare for the type of surface analysis to be performed. If format finds bad blocks, it will re-map them.

11. At the analyze> prompt, type quit.

12. Do you want to specify blocks to re-map? If yes, at the format> prompt, type repair. Otherwise, go to the next step.

13. Continue to type quit until you exit the format program to the system prompt.

14. Choose Restart Install from the Workspace menu to resume the GUI installation, or type suninstall to resume the CUI installation.

WARNING: CHANGE DEFAULT BOOT DEVICE

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. 

No upgradeable disks

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 Solaris Web Start cannot find an IA boot partition. Solaris Web Start consequently attempts to perform an initial upgrade. Ultimately, the message: 

Please choose another installation option, 
see the Solaris install Documentation for more 
details.
# 

You cannot use Solaris Web Start to upgrade to Solaris 8 from Solaris 7 or earlier versions of the Solaris operating environment because it uses a different method to install Solaris software (a separate 10-Mbyte IA boot partition).

You must instead use the Solaris 8 Interactive Installation Program, which is described in more detail in "Using the Solaris 8 Interactive Installation Program" in Solaris 8 Advanced Installation Guide.

If your system's BIOS supports the changing of the default boot device from one device to another: 

1. Add a second disk to the system and manually create a Solaris fdisk partition and IA boot partition greater than or equal to 10 Mbytes on the second disk.

    

   ---

   Note -

   The second disk must either be LBA enabled (logical block address enabled--that is, sectors on the disk are mapped and addressed linearly) or contain fewer than 1024 cylinders. To determine if the second disk is LBA enabled or CHS enabled (cylinder/head/sector enabled--that is, addressing of the disk is by cylinder, head, and sector number), type:

   # prtconf -pv | grep lba

   If lba-access-ok is displayed, the second disk is LBA enabled. If lba-access-ok is not displayed, the second disk is CHS enabled.

   ---

2. Use your system's BIOS setup tool to identify the second disk as the default boot device.

3. Format the Solaris partition so that it contains a swap slice that is large enough to hold the Solaris software (a minimum of 256 Mbytes is required, but 512 Mbytes is recommended; a minimum of 320 Mbytes is required for Solaris 8 Installation Multilingual Intel Platform Edition).

4. Upgrade the Solaris software on the first disk by booting from the second disk.

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

Metadevices cannot be upgraded automatically. Instructions are included in the "Upgrading to Other Solaris Versions" in the Solstice DiskSuite 4.2 Reference Guide.

The upgrade option is not presented even though there is a version of Solaris software that can be upgraded on the system. 

Reason 1: The /var/sadm directory is a symbolic link 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 8 Installation English Intel Platform Edition or Solaris 8 Installation Multilingual Intel Platform Edition CD, or from the network.

2. Choose the upgrade option for installation.

Solaris Web Start determines if the system has been partially upgraded and will continue the upgrade where it left off. 

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 cannot be mounted or that might 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 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 usually reside on an automounted file system, are not affected by an upgrade.

Solution for Reason 1: During the upgrade, delete software packages that will create files or directories on the automounted file systems. Then the 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 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 that are installed in the file systems that need more space. Especially look for any new packages that have been added to the Solaris software that you don't need.