I have 2x 4TB HDDs that were put in an LVM group last year, ended up not really using this server due to huge issues around installing nextcloud. At some point it started giving me boot problems so I deleted the LVM Volume and Group.
Recently I've cleanly re-installed Ubuntu 18.04 on this system, but can't get these HDDs to work in LVM2 again. I'm using KVPM to make them LVM2 PVs, then Group and Volume. I cannot mount them as the final step.
sudo mke2fs -n /dev/mapper/lvmgroup-lvmvol mke2fs 1.44.1 (24-Mar-2018) Creating filesystem with 1953507328 4k blocks and 244191232 inodes Filesystem UUID: 278308bd-878e-4dde-8bac-420ddb858636 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848, 512000000, 550731776, 644972544, 1934917632
Some guides suggested that fsck could clear these blocks:
$ sudo e2fsck -b 32768 /dev/lvmVolGroup/lvmVGVol e2fsck 1.44.1 (24-Mar-2018) e2fsck: Bad magic number in super-block while trying to open /dev/lvmVolGroup/lvmVGVol 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> Found a gpt partition table in /dev/lvmVolGroup/lvmVGVol
but I've tried quite a few of the listed bad blocks and they all just complain about 8193 and 32768. Yes I've tried those exact blocks too, same message.
So I tried removing/deleting all LVM steps, and completely reformatting both drives using gparted, and starting over. This did not work and I still get the exact same issues.
There was some data transferred into the LVM last time to test it was working, and I don't really care about preserving any existing data because I have other backups. I just need the LVM to be functional again. The drives themselves should still be working because they were bought brand new and tested individually, then just left sitting in a system that's been shut off for half a year.
Does anyone know what I could do?