Linux box crash

[Eric]

If you look in /etc/rc.d/rc.S you'll see how the partitions are mounted
read write and read only.  After the root file system is mounted
read-only, the filesysem should be checked with

/sbin/fsck -A -a

If you crashed, fsck will actually do something, and probably find a lot
of errors on your disk. If you tried to 'recover' by using some
floppies, you should definately run fsck on all of your partitions
before you try to write to that partition!  If you run fsck without the
-A option, it will ask you to confirm a bunch of information.  

FYI /etc/rc.d/rc.S script started to fail when I replaced the link of
/bin/sh from bash to ash.  Changing back to bash 'seemed' to help, but I
didn't crash my machine again to fully test it.

-Eric.

Eric Jones writes:
 > Our Linux PC crashed while running a LDM program and appears to have 
 > corrupted some files. When loading it stops on 'read only file system'. 
 > It never gets to the next command which should say 'INIT: version 2.57b 
 > booting'. We booted off of floppies, mounted the hard drive and looked it 
 > the fstab file. It appears to be in good shape. Is the kernel corrupt and 
 > does it need recompiled? Or is there a simpler way to recovery. Thanks in 
 > advance.
 > 
 > 
 > Eric Jones
 > ejones at wave.tcs.tulane.edu
 > Phone: 504-641-4343
 > Fax: 504-643-1226