Why does a filesystem check fail with a message saying that the superblock cannot be read?
Issue
- Superblock error after upgrading the kernel.
- The following error was observed when rebooting into single user mode.
- Seeing the following error while installing a new kernel and booting from it:
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 superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
fsck.ext3: No such file or directory while trying to open /dev/sdb7
Environment
- Red Hat Enterprise Linux 4
- Red Hat Enterprise Linux 5
- Red Hat Enterprise Linux 6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.