wrong fs type, bad option, bad superblock on /dev/mapper/vgfirstdisk-lvhome


I was attempting to install AntergOS to an lv container I setup in my lvm. The installer AntergOS created uses the ‘wipefs’ utility, which instead of wiping that specific container and installing to it, wiped my entire disk. Now I’m trying to recover and need help (and no I don’t have a backup because I’m an idiot.)

I’ve come a long way in the recovery so please see the following link for progress:

The latest (and seemingly last) hurdle is a bad superblock error. See below for the output of e2fsck -n on the lvhome container:

$ sudo e2fsck -n /dev/mapper/vgfirstdisk-lvhome
e2fsck 1.42.12 (290Aug-2014)
ext2fs_open2: Bad magic number in super-block
es2fsck: Superblock invalid, trying backup blocks...
/dev/mapper/vgfirstdisk-lvhome was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
{a lot of numbers started scrolling by very quickly}
{following line repeated for every group}
Free inodes count wrong for group #933 (8192, counted=5891).
Fix? no

Free inodes count wrong for group #934 (8192, counted=6498).
Fix? no

Free inodes count wrong (7659509, counted=4229979).
Fix? no

/dev/mapper/vgfirstdisk-lvhome: ********** WARNING: Filesystem still has errors **********

/dev/mapper/vgfirstdisk-lvhome: 11/7659520 files (8554.5% non-contiguous), 528739/30617600 blocks

This mailing list is for the LLVM compiler, not for the Logical Volume
Manager (LVM).
I think you want to try posting to this mailing list: