fsck error on LINUX

[Cliff Lim Kok Hwee]

Hi Forumers, encounter this error,

[/dev/mapper]fsck -a /dev/mapper/mpath0p1
fsck 1.35 (28-Feb-2004)
ext2fs_check_if_mount: Input/output error while determining whether /dev/mapper/mpath0p1 is mounted.
fsck.ext2: Bad magic number in super-block while trying to open /dev/mapper/mpath0p1
/dev/mapper/mpath0p1:
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

running e2fsck -b 819s is not helping too.

Wht is to be done?

Cliff

[Steven E. Protter]

Shalom Cliff,

fsck is saying there is no filesystem at the location you are checking.

Rules:
1) umount the fs before running fsck
2) Make sure there is a fileystem there first.

If the disk is totally lost, this would explain the results.

SEP

[Alan_152]

I would recommend booting into single user mode, unmounting any file systems that are on the physical device, then fsck'ing the raw device.

Of course, do all this AFTER making a backup of the device using dd or tar.