Urgent help needed - lvm thin pool problems (no disk space problem)

User Support
2

Hi @Ruben12, I’m sorry you’ve encountered such a problem.

For me, depending on the importance of the data on the disk, I would
start by taking a full image of the disk - attach a usb storage device,
boot from a live iso, and then use dd to get the image.

Almost anything you do has the potential to trash those volumes, which
is why a disk image is an essential.

At least a plausible approach would be to try to fix the error.
You could try this, as root in dom0:

  1. Take a backup of the volume group configuration.
    vgcfgbackup qubes_dom0 -f /home/user/VG_backup
  2. Edit the new file, and look at the section under logical_volumes->vm-pool->segment1
    change the transaction_id to 10691.
  3. Save the edited file.
  4. Read the edited data back in:
    vgcfgrestore qubes_dom0 -f /home/user/VG_backup
  5. Activate the edited volume:
    lvchange -ay qubes_dom0

Another approach would be to try to repair the pool:

  1. Deactivate all qube volumes in the thin pool.
    lvchange -an /dev/qubes_dom0/vm*
  2. Try a repair on the thin pool:
    lvconvert --repair qubes_dom0/vm-pool
  3. Reactivate the qube volumes.

Note that it may be possible for you to extract the data directly
from the qube volumes.
In dom0, try mounting an image directly:
sudo mount -o ro /dev/qubes_dom0/vm-work-private /mnt
You may then be able to copy out the important data to another device.

Using these methods you do at least stand a chance of getting your data
back. I would take a disk image, try to extract the data manually, try
to repair the pool, then try to “fix” the error, in that order.
If you need help at any stage please follow up.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.