<div dir="ltr"><span style="color:rgb(35,38,41);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI Adjusted","Segoe UI","Liberation Sans",sans-serif;font-size:15px">Good afternoon, I'm asking for help in recovering damaged metadata after a 220V drop on the server, when the power was restored and the server booted up, I got an error in the Proxmox panel</span><br><div><span style="color:rgb(35,38,41);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI Adjusted","Segoe UI","Liberation Sans",sans-serif;font-size:15px"><br></span></div><div>Check of pool pve/data failed (status:1). Manual repair required!<span style="color:rgb(35,38,41);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI Adjusted","Segoe UI","Liberation Sans",sans-serif;font-size:15px"><br></span></div><div><br></div><div><span style="color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px">then booted from LiveCD debian mounted corrupted metadata and tried to repair</span><br style="box-sizing:border-box;color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px"></div><div><span style="color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px"><br></span></div><div>root@debian:/home/user# lvchange -ay /dev/pve/data_tdata<br> Do you want to activate component LV in read-only mode? [y/n]: y<br> Allowing activation of component LV.<br>root@debian:/home/user# lvs<br> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert<br> vm-102-disk-0 local-hdd-volume1-pve1 -wi-a----- 50.00g<br> vm-103-disk-0 local-hdd-volume1-pve1 -wi-a----- 250.00g<br> vm-104-disk-0 local-hdd-volume1-pve1 -wi-a----- 150.00g<br> vm-108-disk-0 local-hdd-volume1-pve1 -wi-a----- 20.00g<br> vm-109-disk-0 local-hdd-volume1-pve1 -wi-a----- 160.00g<br> vm-110-disk-0 local-hdd-volume1-pve1 -wi-a----- 20.00g<br> base-101-disk-0 pve Vri---tz-k 20.00g data<br> base-105-disk-0 pve Vri---tz-k 15.00g data<br> data pve twi---tz-- <858.97g<br> root pve -wi-a----- 30.00g<br> snap_vm-106-disk-0_Installed pve Vri---tz-k 15.00g data<br> snap_vm-106-disk-0_Installed_CspAndVipnet pve Vri---tz-k 15.00g data<br> swap pve -wi-a----- 8.00g<br> vm-100-disk-0 pve Vwi---tz-- 20.00g data<br> vm-100-disk-1 pve Vwi---tz-- 60.00g data<br> vm-102-disk-0 pve Vwi---tz-- 20.00g data<br> vm-103-disk-0 pve Vwi---tz-- 30.00g data<br> vm-104-disk-0 pve Vwi---tz-- 25.00g data<br> vm-106-disk-0 pve Vwi---tz-- 15.00g data snap_vm-106-disk-0_Installed_CspAndVipnet<br> vm-107-disk-0 pve Vwi---tz-- 20.00g data<br> vm-108-disk-0 pve Vwi---tz-- 30.00g data<br> vm-109-disk-0 pve Vwi---tz-- 35.00g data<br> vm-110-disk-0 pve Vwi---tz-- 20.00g data<br><br>root@debian:/home/user# vgs<br> VG #PV #LV #SN Attr VSize VFree<br> local-hdd-volume1-pve1 1 6 0 wz--n- 3.27t <2.64t<br> pve 1 17 0 wz--n- <930.50g <16.00g<br><br>root@debian:/home/user# ls -la /dev/mapper/ | grep -v vm<br>total 0<br>drwxr-xr-x 2 root root 240 Mar 29 17:48 .<br>drwxr-xr-x 19 root root 3700 Mar 29 17:48 ..<br>crw------- 1 root root 10, 236 Mar 29 17:35 control<br>lrwxrwxrwx 1 root root 7 Mar 29 17:48 pve-data_tdata -> ../dm-2<br>lrwxrwxrwx 1 root root 7 Mar 29 17:35 pve-root -> ../dm-1<br>lrwxrwxrwx 1 root root 7 Mar 29 17:35 pve-swap -> ../dm-0<br><br>root@debian:/home/user# thin_dump --repair /dev/mapper/pve-data_tdata > repaired.xml<br>The following field needs to be provided on the command line due to corruption in the superblock: transaction id<br><br>root@debian:/home/user# thin_check /dev/mapper/pve-data_tdata<br>examining superblock<br> superblock is corrupt<br> bad checksum in superblock, wanted 2018675394<span style="color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px"><br></span></div><div><br></div><div><span style="color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px">however, I don’t know how to specify the transaction id and, most importantly, what id - where to find it</span><br style="box-sizing:border-box;color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px"><br style="box-sizing:border-box;color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px"><span style="color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px">Kernel Version: Linux 5.15.30-2-pve #1 SMP PVE 5.15.30-3 (Fri, 22 Apr 2022 18:08:27 +0200)</span><br style="box-sizing:border-box;color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px"><span style="color:rgb(20,22,24);font-family:"Open Sans",Roboto,-apple-system,BlinkMacSystemFont,"Segoe UI",Oxygen,Ubuntu,Cantarell,"Fira Sans","Droid Sans","Helvetica Neue",sans-serif;font-size:14px">PVE Manager Version: pve-manager/7.2-3/c743d6c1</span><br></div></div>