Step 4: Rebooting Your System

Once you have checked for and corrected an y problems from Step 3, y ou are ready to reboot y our system. You can reboot y our system using the TOC button on the panel of the Model 742i. Otherwise, y ou can turn the system o￿ and then back on to initiate the boot sequence.

You will probably notice a few di￿erences in boot beha vior as compared with your normal boot sequence. Y our system migh t save a \core" ￿le to disk. This core ￿le is a \snapshot" of the previously running k ernel at the time that it panicked. If it becomes necessary , this core ￿le can be analyzed using special tools to determine more about what caused the panic.

Note Core ￿les are quite large and are sa ved to the directory /tmp/syscore . If you feel you need to save these ￿les for

future analysis (something that isn't usually required), it is best to save them to tape and remo ve them from your ￿le system in order to free up space. If y ou know why your system panicked, you can delete the core ￿les; it is unnecessary to k eep them. The core ￿les are used in rare circumstances to diagnose hard-to-￿nd causes of system panics.

If the reason your system panic ked was because of a corrupted ￿le system,

6

 

fsck will report the errors and an y corrections it mak es. If the problems w ere

 

associated with y our root ￿le system, fsck will ask you to reboot your system

 

when it's ￿nished. When y ou do this, use the command:

 

reboot -n

 

The -noption tells reboot not to sync the ￿le system before rebooting. Since

 

fsck has made all the corrections on disk, y ou do not want to undo the

 

changes by writing o ver them with the corrupt memory bu￿ers.

 

Dealing With Problems 6-13

FINAL TRIM SIZE : 7.0 in x 8.5 in