Filesystem corrupt after VM lost it's VLAN
by Mavman from LinuxQuestions.org on (#4ZF5B)
I have a VMware VM running CentOS 5.11 (I know), where the ESXi host lost the VLAN for storage traffic, and now the VM dies on boot -
Code:EXT3-fs error (device dm-): ext3_lookup: unlinked inode 2424833 in dir #2
EXT3-fs error (device dm-): ext3_lookup: unlinked inode 2785281 in dir #2
exec of init (/sbin/init) failed!!!: No such file or directory
Kernel panic - not syncing: Attempted to kill init!This VM has one drive with two partitions. I grabbed the 5.11 CentOS rescue CD & booted into 'linux rescue' mode. fsck reports sda1 as /boot and clean, and I can mount it without issue. The second partition is an LVM with a few volumes, but is unable to detect anything on sda2-
Code:fsck 1.38 (30-Jun-2005)
fsck: WARNING: couldn't open /etc/fstab: No such file or directory
e2fsck 1.38 (30-Jun-2005)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: while trying to open /dev/sda2
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.ext2:So I grabbed the list of superblocks with -
Code:mke2fs -n /dev/sda2Then for each superblock I tried running -
Code:e2fsck -b <SuperBlock> /dev/sda2And every time it errored with -
Code:e2fsck 1.38 (30-Jun-2005)
e2fsck: while trying to open /dev/sda2
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>
e2fsck:So...Is it lost? Thanks for your time in advance.
Code:EXT3-fs error (device dm-): ext3_lookup: unlinked inode 2424833 in dir #2
EXT3-fs error (device dm-): ext3_lookup: unlinked inode 2785281 in dir #2
exec of init (/sbin/init) failed!!!: No such file or directory
Kernel panic - not syncing: Attempted to kill init!This VM has one drive with two partitions. I grabbed the 5.11 CentOS rescue CD & booted into 'linux rescue' mode. fsck reports sda1 as /boot and clean, and I can mount it without issue. The second partition is an LVM with a few volumes, but is unable to detect anything on sda2-
Code:fsck 1.38 (30-Jun-2005)
fsck: WARNING: couldn't open /etc/fstab: No such file or directory
e2fsck 1.38 (30-Jun-2005)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: while trying to open /dev/sda2
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.ext2:So I grabbed the list of superblocks with -
Code:mke2fs -n /dev/sda2Then for each superblock I tried running -
Code:e2fsck -b <SuperBlock> /dev/sda2And every time it errored with -
Code:e2fsck 1.38 (30-Jun-2005)
e2fsck: while trying to open /dev/sda2
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>
e2fsck:So...Is it lost? Thanks for your time in advance.