Hi There,
Do you know about LVM Thin?

This particular case is that LVM repair is not possible. And the LVM Thin LVs cannot be activated.

We need to recover the VM Files.

Few details below.


# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 447.1G 0 disk
├─sda1 8:1 0 1M 0 part
├─sda2 8:2 0 256M 0 part
└─sda3 8:3 0 446.9G 0 part
├─pve-root 251:0 0 96G 0 lvm /
└─pve-swap 251:1 0 8G 0 lvm [SWAP]

# vgchange -a y pve
Check of pool pve/data failed (status:1). Manual repair required!
2 logical volume(s) in volume group "pve" now active

# lvchange -a y pve/data
Check of pool pve/data failed (status:1). Manual repair required!

#lvconvert --repair pve/data
bad checksum in superblock
Repair of thin metadata volume of thin pool pve/data failed (status:1). Manual repair required!

This is what happen when trying to FSCK from rescue boot

[liveuser@localhost —]$ sudo e2fsck -y /dev/sda3
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks…
e2fsck: Bad magic number in super-block while trying to open /dev/sda3

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

Then I tried backup block, but still not working

[liveuser@localhost —]$ sudo e2fsck -b 8193 /dev/sda3
e2fsck 1.42.9 (28-Dec-2013)
e2fsck: Bad magic number in super-block while trying to open /dev/sda3

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>



LVS -a is also not showing any percentage in data column

# lvs -a
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy %Sync Convert
data pve twi—tz-- 326.88g
[data_tdata] pve Twi------- 326.88g
[data_tmeta] pve ewi------- 84.00m
[lvol0_pmspare] pve ewi------- 84.00m
root pve -wi-ao---- 96.00g
swap pve -wi-ao---- 8.00g
vm-100-disk-1 pve Vwi—tz-- 10.00g data
vm-101-disk-1 pve Vwi—tz-- 10.00g data
vm-102-disk-1 pve Vwi—tz-- 32.00g data
vm-103-disk-1 pve Vwi—tz-- 30.00g data
vm-104-disk-1 pve Vwi—tz-- 32.00g data
vm-105-disk-1 pve Vwi—tz-- 32.00g data
vm-106-disk-1 pve Vwi—tz-- 32.00g data
vm-107-disk-1 pve Vwi—tz-- 32.00g data
vm-108-disk-1 pve Vwi—tz-- 32.00g data
vm-109-disk-1 pve Vwi—tz-- 32.00g data
vm-110-disk-1 pve Vwi—tz-- 160.00g data
vm-111-disk-1 pve Vwi—tz-- 60.00g data
vm-112-disk-1 pve Vwi—tz-- 60.00g data
vm-113-disk-1 pve Vwi—tz-- 60.00g data

To check the server I can provide TeamViewer to a computer with a terminal that is already login as root.