Booting a System

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 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
 

SPARC based systems only

This error occurs when you override the location of the boot file by explicitly setting it to /kernel/unix. In Solaris 2.6 and subsequent releases, the kernel is no longer located in /kernel/unix, but in /platform/arch/kernel/unix.

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

Can't boot from file/device                                        
 

JumpStart or the Solaris 8 Interactive Installation Program can't find the CD labeled Solaris 8 Software 1 of 2 for your platform in the system's CD-ROM drive. 

Make sure the: 

• CD-ROM drive is installed properly and turned on

• CD labeled Solaris 8 Software 1 of 2 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. 

Not a UFS filesystem
 

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). 

IA based systems only

The Solaris 8 root slice must be located within the first 1024 cylinders of the disk. If it is not, the installation fails after booting.

If the first fdisk partition is primary DOS (PRI DOS), use the fdisk command to delete space from it. Try booting again. If the first fdisk partition is extended DOS (EXT DOS) or another operating system, use the fdisk command to delete it. Try booting again.

IA based systems only

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

Non-memory PCs cannot use the same memory resources used by other devices. To correct this problem, 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 diskette labeled Solaris 8 Device Configuration Assistant Intel Platform Edition.

2. Go to the Device Tasks menu.

3. Select Review/Edit Devices.

4. Select Add Device.

5. Select Define Device.

6. Enter a unique name following the EISA ID naming conventions (for example, ITD4001), and select Continue.

7. Select Memory Address from the list of resources, and select Continue.

8. Enter the address range to reserve (for example, CA800–CFFFF), and select Continue.

9. Return to the Device Tasks menu and select Save Configuration.

10. Reboot the system.

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. 

• If you are using old drives, they 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 drive as the master (or as a master operating with a slave), and jumper the second drive as a slave.

• If one drive is a hard disk and the second a CD-ROM drive, designate one drive as the slave drive by setting jumpers. It doesn't matter which drive is plugged into which drive 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 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.

• 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.

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. 

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

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

IA based systems only

The system hangs before displaying the system prompt. 

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