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

Hello,

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:
https://redd.it/3mjqcd

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

----------

e2fsck -p compained about superblocks

----------

e2fsck: Bad magic number in super-block while trying to open
/dev/vgfirstdisk/lvhome
/dev/vgfirstdisk/lvhome:
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
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>
 or
    e2fsck -b 32768 <device>

dump2fs output for superblocks:

-------------

$ sudo dumpe2fs /dev/sdd
dumpe2fs 1.42.13 (17-May-2015)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sdd
Couldn't find valid filesystem superblock.
┌[14:01:47]─[arra]
└ $ sudo dumpe2fs /dev/vgfirstdisk/lvhome
dumpe2fs 1.42.13 (17-May-2015)
dumpe2fs: Bad magic number in super-block while trying to open
/dev/vgfirstdisk/lvhome
Couldn't find valid filesystem superblock.



I hope someone can help me recover from this. Please and thank you!

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151011/6f4ebc50/attachment.html>

On Sun, Oct 11, 2015 at 2:36 PM, R A via llvm-dev <llvm-dev at
lists.llvm.org>
wrote:
> Hello,
>
> I was attempting to install AntergOS to an lv container I setup in my lvm.
>
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:
https://www.redhat.com/mailman/listinfo/linux-lvm

--
Craig
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151011/18f74477/attachment.html>