e2fsck -b 8193 /dev/sda1

[Tammy Liang]

I got bad magic number in supper-block after
I run "e2fsck -b 8193".
Any help is appreciated...

[Ivan Ferreira]

It's not a must that the superblock copy will be in 8193. It depends of the file system block size or partition/volume size.

You always should have a copy of dumpe2fs "before" the FS dies.

[Tammy Liang]

I tried 8193, 16384 and 23768. None of them
work. I can log in, however I have issue with file system read-only due to it is corrupt. Any other suggestion?

Thanks.

[George Liu_4]

which fs is it?
ext2 or ext3?

[Tammy Liang]

It is virtual disk space in VM guest with
RedHat ES4.

/dev/sda2 14 6527 52323705 8e Linux LVM
[root@englvm72 ~]#

[Stuart Browne]

No, that's a LVM partition, which doesn't have any sort of filesystem on it (directly).

You need to access the LVM volumes on it, using the /dev/mapper/ or /dev// device node structures.

Do you know what logical volumes you've created?

Use 'vgdisplay' and 'lvscan' to list all the logical volume groups and device nodes. Then you can do the fsck on the filesystems.