Recovering backup: unable to restore CT XYZ for space reasons

K

Krulle

Member
Mar 12, 2023
6
0
6
Hey together,
I'm having serious problems with my Proxmox instance (although probably not everything can be attributed to Proxmox).

My setup includes 4 hard drives:
- NVMe with Proxmox itself
- SSD for the VM hosts (VG: storageVMs)
- 2xHDD RAID 1 as data storage

Long story short:
It started with storage errors on one of the RAID HDDs. The host and 5 VMs continued to run, then the problem spread to the SSD until I finally reacted, shut down the VMs, and disabled the rolling backups (backups are stored on the NVMe and transferred to another server weekly).
Now I'm trying to get the broken hard drives up and running again, VM by VM. fsck found and repaired some errors, and I'm currently stuck on the error message mentioned above.
When I try to restore a VM, I get the following error message:
Code: 
recovering backed-up configuration from 'local:backup/vzdump-lxc-102-2025_08_11-01_04_54.tar.zst' WARNING: Thin pool storageVMs/storageVMs has unexpected transaction id 214, expecting 213. TASK ERROR: unable to restore CT 102 - lvcreate 'storageVMs/vm-102-disk-1' error: Cannot create new thin volume, free space in thin pool storageVMs/storageVMs reached threshold.

lvs print out:
Code: 
:~# lvs
  LV                                      VG         Attr       LSize    Pool       Origin                                  Data%  Meta%  Move Log Cpy%Sync Convert                           
  snap_vm-102-disk-0_GitLab_first_steps   storageVMs Vri---tz-k   15.00g storageVMs                                                                               
  snap_vm-102-disk-0_GitLab_install_ready storageVMs Vri---tz-k   15.00g storageVMs                                                                                                                                                            
  storageVMs                              storageVMs twi-aotz-- <467.28g                                                    17.58  0.94                           
  vm-100-disk-0                           storageVMs Vwi-a-tz--   32.00g storageVMs                                         97.27                                 
  vm-101-disk-0                           storageVMs Vwi-a-tz--   20.00g storageVMs                                         0.00                                   
  vm-102-disk-0                           storageVMs Vwi---tz--   30.00g storageVMs snap_vm-102-disk-0_GitLab_install_ready                                       
  vm-103-disk-0                           storageVMs Vwi-a-tz--   16.00g storageVMs snap_vm-103-disk-0_BlankDebian          35.36                                 
  vm-104-disk-0                           storageVMs Vwi-a-tz--    8.00g storageVMs                                         99.39                                 
  vm-106-disk-0                           storageVMs Vwi-a-tz--    2.00g storageVMs                                         52.76


I don't really know much about (thin)lvm, but it looks fine and I think it's due to the thin pool or the metadata.
Proxmox has now deleted VM 102, but the partitions are still there ( vm-102-disk-0) and I can't create a new partition (it seems).
Does anyone have any ideas what else I could try to fix the problem?

Thanks a lot
 
You must log in or register to reply here.
Top Bottom