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 about the screen.
If this flag is not given, the messages are still printed, but the output is directed to the system log file. For more information, see syslogd(1M).
For SPARC based systems, at the ok prompt, type the following command.
ok boot net -v - install
For x86 based systems, when the installation program prompts you to “Select type of installation,” type the following command.
b - -v install
Boot from DVD media fails on systems with Toshiba SD—M 1401 DVD-ROMDescription:
If your system has a Toshiba SD-M1401 DVD-ROM with firmware revision 1007, the system cannot boot from the Solaris 10 DVD.Solution:
Apply patch 111649–03, or later version, to update the Toshiba SD-M1401 DVD-ROM drive's firmware. The patch 111649–03 is available at sunsolve.sun.com.
The system hangs or panics when nonmemory PC cards are inserted. (x86 based systems only)Cause:
Nonmemory PC cards cannot use the same memory resources that are 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 10 3/05 Device Configuration Assistant diskette during the pre-booting phase. (x86 based systems only)Solution:
Follow these instructions:
If you are using old drives, they might be unsupported. Check your hardware manufacturer's documentation.
Make sure the ribbon and power cables are connected 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, designate one drive as the master by setting jumpers (or as a master operating with a slave), and set the second drive as a slave by setting jumpers.
If one drive is a hard disk and the second a CD-ROM drive, designate one drive as the slave drive by setting jumpers. You can designate either physical drive as the slave drive.
If problems persist with two drives on a single controller, attach one drive at a time to verify that each drive works. Designate the drive as master or single master by setting jumpers, and use the drive connector at the end of the IDE ribbon cable to attach the drive. Verify that each drive works, then set the jumpers for 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.
The IDE disk or CD-ROM drive on your system was not found by the Solaris 10 3/05 Device Configuration Assistant diskette during the pre-booting phase. (x86 based systems only)Solution:
Follow these instructions:
For the Solaris 10 3/05 release, if disks are disabled in the BIOS, use the Solaris 10 3/05 Device Configuration Assistant diskette to boot from the hard disk. For information about accessing the Solaris 10 3/05 Device Configuration Assistant, see Solaris 10 3/05 for x86: Copying the Boot Software to a Diskette.
If the system has no disks, it might be a diskless client.
The system hangs before displaying the system prompt. (x86 based systems only)Solution:
You have hardware that is not supported. Check your hardware manufacturer's documentation.