HP Model 745 - VME Workstation Owner's Manual page 165

Dealing With Problems
Recovering from a System Panic
If the reason your system panicked was because of a corrupted file system,
fsck will report the errors and any corrections it makes. If the problems were
associated with your root file system, fsck will ask you to reboot your sys-
tem when it's finished. When you do this on an HP-UX system, use the fol-
lowing command:
reboot -n
The -n option tells reboot not to sync the file system before rebooting.
Since fsck has made all the corrections on disk, you do not want to undo the
changes by writing over them with the corrupt memory buffers.
Step 4: Monitoring the System
If your system successfully boots, there is a good chance that you can
resume normal operations. Many system panics are isolated events and are
unlikely to reoccur. Check your applications to ensure that they are running
properly and monitor the system closely. For a day or so, you might want to
do backups more frequently until you are confident that the system is func-
tioning properly.
For More Information
Refer to HP-UX System Administration Tasks for further information on
operating-system related problems.
9-11