I had (paying attention to the past time here) a Centos 6.7 host who was migrated using Vmware conversion tool from a HyperV cluster. Therefore, the final configuration of its disks was:
/ dev / sda1 -> BOOT / dev / sdb1 -> Physical Volume VG on / dev / sdb1 6 LVs on VG, root included
Time came and a logical volume was filled and VG did not have any free PEs to extend. So I made a ninja move and I extended
/dev/sdb and went (wrongly) to rewrite the partition table to grow the PV. After that, the VM did not boot again because the LVM metadata was overwritten.
I tried several scenarios, the most successful was
strings / dev / sdb | head -n 1000 where I found copies of the LVM information (from the auto backups it makes to each modification), created a file from what seemed to be the latest configuration, created a PV with uuid same as the original and
--restorefile the specified file. I continued with
vgchange -ay and all logical volumes became visible, but mount fails and I get the
bad superblock or wrong fs type error. I have the feeling that the boundaries of LVs are not correct and I have overlaps with the old structure, hence the problem with the filesystem during mount.
Has any of you seen anything like that? Can anybody suggest any solution?