| OpenBood 3.x Command Reference Manual |
|
| OpenBood 3.x Command Reference Manual |
|
| A P P E N D I X C |
Troubleshooting Guide |
What do you do if your system fails to boot properly? This appendix discusses some common failures and ways to alleviate them.
Familiarize yourself with the system power-on initialization messages. You can then identify problems more accurately because these messages show you the types of functions the system performs at various stages of system startup. They also show the transfer of control from POST to OpenBoot to the Booter to the kernel.
The example that follows shows the OpenBoot initialization sequence in a Sun Ultra TM 1 system. The messages before the banner appear on TTYA only if the diag-switch? parameter is true.
| Note - The actual OpenBoot initialization sequence is system dependent. The messages on your system may be different. |
Some OpenBoot systems provide the capability of commanding OpenBoot by means of depressing a combination of keys on the system's keyboard (i.e. a "keyboard chord").
describes the keyboard chords provided by SPARC-compatible systems. When issuing any of these commands, hold down the keys immediately after turning on the power to the SPARC system, and keep them pressed for a few seconds until the keyboard LEDs flash.
The sync command forces any information on its way to the hard disk to be written out immediately. This is useful if the operating system has crashed, or has been interrupted without preserving all data first.
sync actually returns control to the operating system, which then performs the data saving operations. After the disk data has been synchronized, the operating system begins to save a core image of itself. If you do not need this core dump, you can interrupt the operation with the Stop-A key sequence.
This section describes some common failures and how you can fix them.
Problem: Your system screen is blank and does not show any output.
Here are possible causes for this problem:
Refer to your system documentation.
If the keyboard is not plugged in, the output goes to TTYA instead. To fix this problem, power down the system, plug in the keyboard, and power on again.
Check the power cable on the monitor. Make sure the monitor cable is plugged into the system frame buffer; then turn the monitor on.
This means the NVRAM parameter output-device is set to ttya or ttyb instead of being set to screen . Connect a terminal to TTYA and reset the system. After getting to the ok prompt on the terminal, type: screen output to send output to the frame buffer. Use setenv to change the default display device, if needed.
If your system has several plugged-in frame buffers, or it has a built-in frame buffer and one or more plugged-in frame buffers, then it is possible that the wrong frame buffer is being used as the console device. See Setting the Console to a Specific Monitor .
Problem: Your system is supposed to boot from the disk; instead, it boots from the net.
There are two possible causes for this:
Interrupt the booting process with Stop-A . Type the following commands at the ok prompt:
The system should now start booting from the disk.
Interrupt the booting process with Stop-A . Type the following commands at the ok prompt:
Note that the preceding commands cause the system to boot from the disk defined as disk in the device aliases list. If you want to boot from another service, set boot-device accordingly.
Problem: Your system is booting from a disk instead of from the net.
Interrupt the booting process with Stop-A . Type the following commands at the ok prompt:
Problem: Your system is booting from the wrong disk. (For example, you have more than one disk in your system. You want the system to boot from disk2 , but the system is booting from disk1 instead.)
Interrupt the booting process with Stop-A . Type the following commands at the ok prompt:
Problem: Your system fails to boot from the net.
The problem could be one of the following:
Report the problem to your system administrator.
Plug in the ethernet cable. The system should continue with the booting process.
Report the problem to your system administrator.
Refer to the troubleshooting information in your system documentation. (Note: systems that do not have Twisted Pair Ethernet will not have the tpe-link-test parameter.)
Problem: You are booting from a disk and the system fails with the message: The file just loaded does not appear to be executable.
Problem: You are booting from a disk and the system fails with the message: Can't open boot device.
Turn on power to the disk, and make sure the SCSI cable is connected to the disk and the system.
Problem: Your system has more than one disk installed, and you get SCSI-related errors.
Note the target number and its corresponding unit number.
Plug in another disk and perform Step b again.
If you get an error, change the target number of this disk to be one of the unused target numbers.
Repeat Steps b, c, and d until all the disks are plugged back in.
Problem: You have more than one monitor attached to the system, and the console is not set to the intended monitor.
If you have more than one monitor attached to the system, OpenBoot always assigns the console to the frame buffer specified by the output-device NVRAM parameter. The default value of output-device is screen , which is an alias for one of the frame buffers found by the firmware.
A common way to change this default is to change output-device to the appropriate frame buffer:
Another way of setting the console to a specific monitor is to change the sbus-probe-list NVRAM parameter.
If the frame buffer that you are choosing as the console is in slot 2, change sbus-probe-list to probe slot 2 first:
If a non-SBus frame buffer is installed, this second method may not work.
| OpenBood 3.x Command Reference Manual | 806-1377-10 |
|