NonStop S-Series Hardware Installation and FastPath Guide (G06.29+)

Troubleshooting
HP NonStop S-Series Hardware Installation and FastPath Guide—541880-002
D-11
System Load Fails
System Load Fails
If a system load is not successful or if the system halts:
1. Check the following locations for halt code or event messages:
•
The Processor Status dialog box of the TSM Low-Level Link
•
The System Status and Detailed Status boxes in the System Startup dialog box
•
The OSM or TSM Event Viewer
•
The startup TACL window
•
The startup event stream window
2. Record any event messages or halt codes. See the appropriate documentation for
recovery information.
•
If possible, look up event messages in the EMS logs ($0 and $ZLOG). For the
cause, effect, and recovery procedures for these events, see the
documentation appropriate for your system among the TSM Event Viewer
online help, the OSM User’s Guide, and the Operator Messages Manual. (If
you configured your processor to print event messages to a printer, you might
be able to retrieve messages sent while the system was going down.)
•
For the cause and recovery procedures, look up the halt code in the Processor
Halt Codes Manual.
3. Perform a processor dump, if needed. See Dumping Processor Memory on
page D-16. Do not prime or reset the processor before performing the dump.
4. Correct any problems shown in the dump, or contact your service provider.
5. Load the system again.
You can also try loading the system using one of the following methods:
1. Load the system from an earlier version of the system configuration database by
specifying a saved version of the CONFIG file if one is available. You can use this
method to recover from a configuration change that caused a problem:
a. Load the system from a system console, specifying a saved version of the
system configuration file in the form xx.yy. For example, the CONF0205 file
would be specified as 02.05 or 2.5.
b. When the system starts and displays a TACL prompt, log on and start the rest
of the system applications.
Caution. Performing a tape load from a system image tape (SIT) to restore the system image
files to the $SYSTEM disk (SYSnn and CSSnn subvolumes) is generally not recommended.
Perform a tape load only with the advice of the GCSC or your service provider. Loading
from a tape reinitializes the disk directory, overlays the disk directory with the directory from the
tape, and destroys all files on the disk. Many additional steps are required to restore your
system to working order because the SIT does not contain all the files that were on the
$SYSTEM disk, including almost all important system configuration information.