欢迎加入IT云增值在线QQ交流群：342584734
分类：
2006-09-02 12:58:26
le0: No carrier - transceiver cable problem
Cause: The system is not connected to the network.
Solution: If this is a non-networked system, ignore this message. If this is a networked system, ensure that the Ethernet cabling is attached securely.
The file just loaded does not appear to be executable
Cause: The system cannot find the proper media for booting.
Solution: Verify that the system has been set up properly to install the Solaris 9 software from the network from an install server. For example, ensure that you specified the correct platform group for the system when you set it up.
Or, if you did not copy the images of the Solaris DVD or Solaris Software 1 of 2, Solaris Software 2 of 2, and Solaris Languages CDs to the install server, ensure the Solaris DVD or Solaris Software 1 of 2 CD is mounted and accessible on the install server.
boot: cannot open /kernel/unix(SPARC based systems only)
Cause: This error occurs when you override the location of the boot - file by explicitly setting it to /kernel/unix.
Solution: Reset the boot -file in the PROM to " " (blank).
Ensure that the diag-switch is set to off and to true.
Can't boot from file/device
Cause: The installation media cannot find the bootable media.
Solution: Ensure that the following conditions are met:
The DVD-ROM or CD-ROM drive is installed properly and turned on.
Solaris DVD or the Solaris Software 1 of 2 CD is inserted into the drive.
The disc is free of damage or dirt.
WARNING: clock gained xxx days -- CHECK AND RESET DATE! (SPARC based systems only)
Description: This is an informational message.
Solution: Ignore the message and continue with the installation.
Not a UFS file system (x86 based systems only)
Cause: When Solaris 9 software was installed (either through the Solaris suninstall program or custom JumpStart), no boot disk was selected. You now must use the Solaris Device Configuration Assistant x86 Platform Edition diskette or edit the BIOS to boot the system.
Solution: Insert the Solaris Device Configuration Assistant x86 Platform Edition diskette into the system's boot diskette drive (usually drive A). For information on accessing the Solaris Device Configuration Assistant x86 Platform Edition diskette, see .
If you cannot use the bootable media, go into the BIOS and select the BIOS to boot. See your BIOS documentation for instructions.
The Solaris Installer could not find a disk that meets the criteria found in the Install documentation. Please see the documentation for more info. (x86 based systems only)
Cause: You've tried to boot from the Solaris x86 Platform Edition Installation CD. The system does not support logical block addressing (LBA) and the Solaris Installation CD cannot be used.
Solution: Use a net image of the CD, a DVD, or the Solaris Software 1 of 2 x86 Platform Edition CD to install.
The system does not boot.
Description: When initially setting up a custom JumpStart server, you might encounter boot problems that do not return an error message. To verify information about the system and how the system is booting, run the boot command with the -v option. When you use the -v option, the boot command displays verbose debugging information on the screen.
Note - If this flag is not given, the messages are still printed, but the output is directed to the system logfile. For more information, see syslogd(1M).
Solution: For SPARC based systems, at the ok prompt, type the following command.
For x86 based systems, when the installation program prompts you to "Select type of installation," type the following command.
Boot from DVD media fails on systems with Toshiba SD--M 1401 DVD-ROM
If your system has a Toshiba SD-M1401 DVD-ROM with firmware revision 1007, the system cannot boot from the Solaris DVD.
Solution: Apply patch 111649-03, or later version, to update the Toshiba SD-M1401 DVD-ROM drive's firmware. Patch 111649-03 is included on the Solaris 9 Supplement CD.
The installation fails after booting. (x86 based systems only)
Cause: If you are installing from the Solaris Installation CD, the Solaris 9 root slice must be located within the first 1024 cylinders of the disk.
Solution: The BIOS and SCSI driver for the default boot disk must support logical block addressing (LBA). LBA enables the machine to boot beyond the 1024-cylinder limit and across Solaris disk slices. To determine if your system supports LBA, see . If your system does not support LBA, boot from a net image rather than the CD.
The system hangs or panics when non-memory PC cards are inserted. (x86 based systems only)
Cause: Non-memory PC cards cannot use the same memory resources used by other devices.
Solution: To correct this problem, see the instructions for your PC card and check for the address range.
The IDE BIOS primary drive on your system was not detected by the Solaris Device Configuration Assistant x86 Platform Edition diskette during the pre-booting phase. (x86 based systems only)
Solution: If you are using old drives, they might be unsupported. Check your hardware manufacturer's documentation.
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 does not matter which drive is connected to which drive connection on the cable.
If problems persist with two drives on a single controller, attach one drive at a time to verify that each drive 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 to 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.
For many systems, IDE CD-ROM drives are only recognized by MS-DOS if an MS-DOS CD-ROM driver has been installed. Try another drive.
