Owner`s manual

If you need to load a boot primitive before booting, see Appendix E. If the
boot procedure fails, check through the steps shown in Figure 6–9.
1. Enter the BOOT command.
Was the console terminal in console mode? If you are using a nickname
(a stored BOOT command), did you use a valid nickname? You can
check the nickname by using the SHOW command (see Section 5.19).
2. System response?
If the system did not respond, check the power to the system. Turn
the system off and on again. Check the power indicator lights (see
Section 3.5) and console terminal connections. Check that the console
terminal is in console mode.
If the system still does not respond, try forcing a boot processor (see
Section 6.10).
3. Self-test completes.
You receive self-test printout. See Section 6.2 through Section 6.7 for a
full explanation of the self-test results.
4. System pass self-test?
If the system did not pass self-test, identify the modules that failed. If
the failed module is your designated boot processor and your terminal is
in console mode, use the SET CPU /NOPRIMARY command to reassign
the boot processor, and reboot.
If all system modules passed self-test, check your boot primitive.
5. Boot primitive works?
If the boot primitive is working, then the boot primitive program reads
the bootblock into memory and the system should boot. If the boot
primitive fails, the boot primitive program is not able to reach the boot
device. The console program displays several error messages. (Error
messages are explained in Appendix H and Appendix I.) Check to see
if the boot device passed self-test. Is the boot device connected to the
system? Is it powered up?
6. System boots?
If the system does not boot, check the boot device for malfunctioning.
See the disk or tape drive manual for the specific boot device. There
may also be a software failure. Check the boot device to be certain that
the bootblock is on the boot device.
If these steps fail, call your customer service engineer.
System Self-Test and Troubleshooting 6–19