Filesystem seems to have taken a hit

From: Mark Adams (madams9_at_junodot.com)
Date: 12/27/04 

Date: Mon, 27 Dec 2004 15:45:14 -0700

Mandrake Linux 9.2 on a PC.

I was attempting to set up a SAMBA server on another machine and
twiddled the fstab on this desktop. For some reason my next reboot
screeched to a halt with this message:

"Checking root filesystem
fsck.ext2/:
The superblock could not be read or does not describe the correct ext2
filesysem. 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 trying to open /
Failed to check filesystem. Do you want to repari the errors (Y/N)
(beware you can lose data)"

I press Y and some activity occurs, then I get a repeat of the previous
message

"The superblock could not be read or does not describe the correct ext2
filesysem. 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 trying to open /"

and a big, fat, red "[FAILED]" followed by:

"*** An error occurred during the file system check
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.

Give root password for maintenance
(or type Control-D for normal startup):"

Attempting to use the alternate superblock does not help.

Fsck.ext3 says everything is clean. When booted into Rescue Mode, I can
see the partitions with lparts, I can mount them and browse them, but
how can I get this thing to boot Linux again?

This desktop is configured for a dual boot with Mandrake and WinXP Pro.
  I went to XP and fired up Partition Magic. I can see that all of the
partitions are intact. I can browse the Linux partitions. I tried
replacing the fstab with a backup, but it didn't make any difference --
boot process still halted with the bad superblock message.

All the partitions and data therein are intact. I'd hate to wipe this
stuff unnecessarily if there is a way to get it back.

Any suggestions?

Mark

Relevant Pages

  • Re: Filesystem seems to have taken a hit
    ... > filesystem, then the superblock ... Maybe try removing SAMBA as a boot service (try removing symlink from ... > partitions are intact. ...
    (comp.os.linux.hardware)
  • Re: Failure to Mount
    ... > fstab says that hdb has 3 primary partitions, ... Filesystem magic number: 0xEF53 ... Couldn't find ext2 superblock, trying backup blocks... ... Couldn't find valid filesystem superblock.# ./tune2fs ...
    (comp.os.linux.misc)
  • Re: how to boot or access problem file system
    ... Do you mean the filesystem's superblock? ... in PC parlance) or the freebsd partitions? ... To check a UFS filesystem, ... how can I use it if I can't boot or access the file system? ...
    (freebsd-questions)
  • Re: how to boot or access problem file system
    ... Do you mean the filesystem's superblock? ... in PC parlance) or the freebsd partitions? ... boot sector is not part of any filesystem. ... To check a UFS filesystem, ...
    (freebsd-questions)
  • Re: Disk partitioning - Suse 10.2
    ... And recovering Linux partitions is very, ... I did set the mount point to /mnt as you suggested. ... You do not *need* to partition a block device - you may put a filesystem ...
    (uk.comp.os.linux)