<Hi, I need help recovering my thin pool after a power outage during a system update.
What happened: Power was lost mid-update. On reboot, all qubes fail to start with:
Check of pool qubes_dom0/vm-pool failed (status:64). Manual repair required!
dom0 boots fine (root pool is healthy). Only vm-pool is affected — all my qube data is in it.
What I’ve already done:
• sudo vgcfgbackup qubes_dom0 -f /tmp/VG_backup, edited the thin-pool transaction_id from 2699 to 2698, then sudo vgcfgrestore qubes_dom0 -f /tmp/VG_backup --force → succeeded (“Restored volume group qubes_dom0”).
• sudo lvchange -ay qubes_dom0/vm-pool → still fails with status:64.
• Tried to run thin_repair, but could not activate lvol0_pmspare — it says “Operation not permitted on hidden LV”.
• Current state: sudo lvs qubes_dom0/vm-pool shows twi—tz-- 815.11g (inactive).
Important: I have already made a full dd image of the entire disk to a second drive, so destructive suggestions are safe — I have a backup of the raw disk.
My goal: I do not need to save the whole system. I only need to activate the pool long enough to mount ONE private volume read-only and copy out a couple of files. Once the pool is active I know how to do the mount.
Could someone help me complete the metadata repair / swap so the pool will activate? I’ll attach the output of sudo lvs -a qubes_dom0. Thank you.!— Before asking, did you search first? Press 
at the upper right to search. ---->