Restarting
The Firewall
Last updated on 15th April 2005 by Buz
Barstow.
If the power fails, brachyura will switch off. When the power is
restored brachyura will restart. Normally it will report that its hard
drive has not been checked for a long time and will check it. After
this check everything should work fine.
However, if you can't get out of our subnet when the power's restored,
brachyura may not have restarted properly. Here's how to check.
- Turn on brachyura's monitor to see if it is displaying a login
screen. If it has, brachyura should be working.
- brachyura may have grumbled about /dev/hdb1 or /dev/hda3 or
similar.
Here's what's happened.
"Most of the time, any file system problems are minor ones caused by
file buffers not being written to the disk, such as deleted inodes
still marked in use. In the majority of cases, the file system check
will be able to detect and repair such anomolies automatically, and
upon completion the Linux boot process will continue normally.
Should a file system problem be more severe (such problems tend to be
caused by faulty hardware such as a bad hard drive or memory chip;
something to keep in mind should file system corruption happen
frequently), the file system check may not be able to repair the
problem automatically. This is usually, but not always, the case when
the root file system itself is corrupted. In this case, the Red Hat
boot process will display an error message and drop you into a shell,
allowing you to attempt file system repairs manually.
As the recovery shell unmounts all file systems, and then mounts the
root file system "read-only", you will be able to perform full file
system checks using the appropriate utilities. Likely you will be able
to run e2fsck on the corrupted file system(s) which should hopefully
resolve all the problems found."
Either use the e2fsck to fix it or call an expert.