HP OpenVMS 8.x Troubleshooting Procedures, If the System Does Not Boot, For Hardware Problems

For more information about the OPCCRASH program, see the HP OpenVMS System Manager's Manual, Volume 1: Essentials.

On cell-based Integrity servers, entering the OpenVMS RUN SYS$SYSTEM:OPCCRASH command results in the system dumping memory and then halting at the P00>>> prompt. To reset the nPartition following OPCRASH, access the nPartition console and press any key to reboot.

Using the MP tc command to reset an nPartition results in the system dumping memory and then automatically resetting the nPartition.

A.8 Troubleshooting Procedures

The following sections describe procedures that you can follow if you encounter problems with your system.

A.8.1 If the System Does Not Boot

If the system does not boot because a hardware problem occurs, a question mark (?) usually precedes the error message displayed on the console terminal. An example of a hardware problem is a read error on a disk. Another is a BIB condition in an nPartition on a cell-based server. You can use VFP to check the nPartition boot state. If VFP indicates that all cells in the nPartition are at BIB, the nPartition is inactive and you must use the MP bo command to boot the nPartition past BIB and make it active.

One way to get to the EFI Boot Manager to attempt to reboot is to use the MP rs command. For more information about using VFP and MP, see your hardware documentation.

A.8.1.1 For Hardware Problems

If you suspect a hardware problem, do the following:

1.Consult the hardware manual for your Integrity server.

2.Contact HP Customer Support.

A.8.1.2 For Software Problems

When the operating system is loaded into memory, a message similar to the following is displayed on the terminal screen:

SYSTEM job terminated at 27-JUL-2007 15:05:03.17

If the system does not display this message, a software problem has probably occurred. Do the following:

1.Turn off the system. Turn it back on and try to reboot.

2.Perform a conversational boot using the default system parameters or try one of the emergency boot procedures described in Section A.6.12 (page 181).

3.If the system boots, run the AUTOGEN procedure. For more information about the AUTOGEN procedure, see the HP OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.

A.8.2 Detecting and Responding to System Problems

If your system exhibits unexpected behavior, note the following:

•If the system displays a bugcheck message on the console terminal and shuts itself down, it means the system encountered a problem that made further operation impossible or dangerous. If the system does not reboot automatically, reboot the system manually as described in Section A.6.7 (page 178).

•If the system stops responding to your commands (that is, if the system hangs), there is a possible failure in a system software or hardware component or a possible power failure.

•If the system exhibits erratic behavior (it does not respond according to specifications), it indicates a possible failure in a system software or hardware component.

186 Configuring OpenVMS I64 Hardware Operation and Boot Operations, and Booting and Shutting Down Your System