Results 1 to 2 of 2
Enjoy an ad free experience by logging in. Not a member yet? Register.
- Join Date
- Sep 2005
- Newark, DE
machine not booting - bad superblock
I am trying to fix our file server which will not boot. We're running Redhat with the 2.4 kernel. Upon booting up it goes through the normal things, then says the system appeared to be shutdown uncleanly or something to this effect. Then, upon checking the root filesystem it says:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the supergblock is corrup, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
The same message occurs when I try to run the e2fsck.
There is a lot of important data on this system. We have a RAID 5 (3+1) with a promise sx4000 controller with 4 IDE drives. The controller seems to be functioning properly since it recognizes all the drives during boot up and also reports the array is functioning. How can we get to the data? Help!
boot from live or system cd with rescue mode & save your data