Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


The Superblock could not be read

The Superblock could not be read

The Superblock could not be read


All of a sudden our Redhat 4.1.8 Server decided to restart (we think) and upon reboot we get the following error:

The superblock could not be read or does not describe a correct ext2 filesystem.  If the device is valid and it really contains an ext 2 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 - 8193 <device>

Fsck.ext 3: No such file or directory while trying to open /dev/VolGroup00/LVol0

The guy who maintained the linux system left 2 weeks ago and all that is left is Linux novices.  Please can someone help with an idiots guide to try and help us resolve this issue?



RE: The Superblock could not be read

What's the output of cat /etc/redhat-release?

What state is the system in right now?  Do you have a shell prompt?  Do all the hard drives appear to be spinning?

I don't think an fsck of any flavour will work at this stage due to the "No such file or directory while trying to open /dev/VolGroup00/LVol0" error, first we need to try and get the logical volume started.

Does vgdisplay -v display anything?


RE: The Superblock could not be read

Can you run system-config-lvm? If not, does it give the same error?

If not, you may be affected by an old bug in RH that has been fixed in Vers 5. Probably the old guy attempted a Volume resize (especially if shrinking Volumes on MD drives created with MDADM) that did not succeed. In that case I do not think there is a fix for it, just look for a good backup that you obviously have, am I right?

Restore, update your system, re-run MDADM (if needed), re-create your volume.

A good tip is to not do it with the graphic installer but instead, get yourself a good reference and leave all involved drives untouched at install time. Create your partitions, MD drives and volumes from command prompt; you will learn a lot about it and also have a greater control over the whole process.


If I could have sex each time I reboot my server, I would definitely prefer Windoz over Linux!

RE: The Superblock could not be read

Make sure that lvm support is loaded. Check the output of lsmod. Disregard obviously if other lvm filesystems are already mounted.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close