Hello,

I am having a problem with my Linux Fedora core1 box. I hope someone can help me.
After loading the latest updates. I am getting the following message at the boot up screen then the system hangs.

************************************************************

Checking root file system
fsck.ext2/:

The super block could not be read or does not describe a correct ext2 file system. If the device is valid and it really contains an ext2 filesystem( and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

:Is a directory while to open /

<Failed>

***An error occurred during the filesystem check.***

************************************************************

After that, I tried running,
e2fsck -b 8193 /dev/hda1 where the root file system is named.

then I get this error,

****************************
e2fsck: Bad magic number in super-block
while trying to open /dev/hda1
****************************

Could one of you Linux gurus help me with this problem.

Thank you,
Mitsurughi

"I am having a problem with my Linux Fedora core1 box. I hope someone can help me.
After loading the latest updates. I am getting the following message at the boot up screen then the system hangs."

Your file system is broken. The Fedora boot script to fix this problem is horrible and may have made the problem worse by running the wrong version of fsck when Fedora tried to fix the problem. I can give you a generalized fix that will probably solve the problem. Try this:

Boot a rescue CD. There is a rescue CD mode on your Fedora install CD. Then run fsck against every Linux partition except swap. It is important that you tell fsck the correct file system type for each partition and you can find the file system types in /etc/fstab. So a fsck command would look something like:

fsck -t ext3 /dev/hda1

Answer yes to everything that fsck asks you. After fsck is finished look in each partition's lost+found to see if fsck put any lost files or file fragments in lost+found with a number for a name.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Thank you for your feedback. Turned out that the problem
was /etc/fstab entry which did not have /, file system on it
after it was accidentally modified. After /etc/fstab update,
I was able to get into the system fine.

Mitsurughi