HP 9000 300 Series Owner's Manual page 126

Step 4: Rebooting Your System
Once you have checked for and corrected any problems from Step 3, you are
ready to reboot your system. If your system has not gotten past the system
selection phase of the boot process, it is safe to turn it o and then back on to
initiate the boot sequence.
You will probably notice a few di erences in boot behavior as compared with
your normal boot sequence. Your controller might have saved a \core" le to
disk. This core le is a \snapshot" of the previously running kernel at the time
that it panicked. If necessary, this core le can be analyzed using special tools
to determine what caused the panic.
Note
If the reason your system panicked was because of a corrupted le system,
the
fsck
problems were associated with your root le system,
to reboot your system when it is nished. In this case, use the following
7
command:
reboot -n
The
-n
rebooting. Since
undo the changes by writing over them with the corrupt memory bu ers.
Step 5: Monitor the system closely
If your system successfully boots, you can resume normal operations. Many
system panics are isolated events and are unlikely to reoccur.
7-18 Dealing with Problems
Get user manuals: See SafeManuals.com
Core les are quite large and are saved to the directory
. If you feel you need to save these les for
/tmp/syscore
future analysis (something that isn't usually required), it is
best to save them to tape and remove them from your le
system in order to free up space. If you
panicked, you can delete the core les; it is unnecessary to keep
them. The core les are used in rare circumstances to diagnose
hard-to- nd causes of system panics.
utility will report the errors and any corrections it makes. If the
option tells the command
reboot
has made all the corrections on disk, you do not want to
fsck
know why your system
will return a message
fsck
not to sync the le system before