topic e2fsck -b 8193 /dev/sda1 in Operating System - Linux

e2fsck -b 8193 /dev/sda1

Tammy Liang — Thu, 14 Dec 2006 16:22:05 GMT

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

Re: e2fsck -b 8193 /dev/sda1

Ivan Ferreira — Thu, 14 Dec 2006 16:31:22 GMT

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.

Re: e2fsck -b 8193 /dev/sda1

Tammy Liang — Thu, 14 Dec 2006 16:53:55 GMT

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.

Re: e2fsck -b 8193 /dev/sda1

George Liu_4 — Fri, 15 Dec 2006 12:38:35 GMT

which fs is it?
ext2 or ext3?

Re: e2fsck -b 8193 /dev/sda1

Tammy Liang — Fri, 15 Dec 2006 12:55:26 GMT

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

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

Re: e2fsck -b 8193 /dev/sda1

Stuart Browne — Sat, 16 Dec 2006 02:59:46 GMT

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.