This is good news. I also thank @passing_clouds - it has been a pleasure to watch their patient help.
@logicalvolume : do you know what happened before you had the problem?
Was it loss of power, flat battery during laptop standby, or some other thing that matches with observations of @marcos-morar ?
+1
Bookmarked
Definitely has something to do with battery
Update VG metadata;
vgck --updatemetadata qubes_dom0
Update pool metadata;
lvconvert --repair qubes_dom0/vm-pool
this solution isn’t working for me.
i think this:
Backup metadata;
vgcfgbackup qubes_dom0 -f /etc/lvm/backup/qubes_dom0
Edit your backup config file - search for transaction ID number and replace with correct ID, eg. change 21472 to 21471 and save;
sudo nano /etc/lvm/backup/qubes_dom0
might work for me but i don’t know which line to modify.
please help!
I’ll paste relevant info below.
lvm vgchange -ay from emergency console
returns 
Error Check of pool qubes_dom0/vm-pool failed (status:64) Manual repair required!
lvconvert --repair qubes_dom0/vm-pool in dom0 and dracut emergency concole. got this output:
Transaction id 19379 from pool 'qubes_dom0/vm-pool" does not maatch repaired transaction id 19378 from dev/qubes_dom0/lvo12_pmspare
LV VG Attr LSie Pool Origin Data Meta
[lvol12_pmspare] qubes_dom0 ewi 148.00m 34.86
root qubes_dom0 Vwi-a-tz 20.00g root-pool 34.86 16.37
root-pool qubes_dom0 twi-aotz 20.00g
root-pool_tdata qubes_dom0 Twi-aotz 20.00g
root-pool_tmeta qubes_dom0 ewi-ao 40.00m
swap qubes_dom0 wi-a <3.93.g
vm-alt_work-private qubes_dom0 Vwi–tz-- 2.00g vm-pool
vm-debian-13-dev-private qubes_dom0 Vwi–tz-- 2.00g vm-pool vm-debian-13-dev-private-#######-back
vm-debian-13-dev-private-#######-back qubes_dom0 Vwi–tz-- 2.00g vm-pool
vm-debian-13-dev-root qubes_dom0 Vwi–tz-- 20.00g vm-pool vm-debian-13-dev-root-#######-back
vm-debian-13-dev-root-#######-back qubes_dom0 Vwi–tz-- 20.00g vm-pool
vm-debian-13-dev-root-#######-back qubes_dom0 Vwi–tz-- 20.00g vm-pool vm-debian-13-dev-root-#######-back
vm-debian-13-dev-root-#######-back qubes_dom0 Vwi–tz-- 20.00g vm-pool vm-debian-13-dev-root-#######-back
vm-debian-13-dev-volatile qubes_dom0 Vwi–tz-- 10.00g vm-pool
vm-debian-13-xfce-private qubes_dom0 Vwi–tz-- 2.00g vm-pool
vm-debian-13-xfce-root qubes_dom0 Vwi–tz-- 20.00g vm-pool
vm-default-dvm-private qubes_dom0 Vwi–tz-- 2.00g vm-pool
vm-default-mgmt-dvm-private qubes_dom0 Vwi–tz-- 2.00g vm-pool
vm-file-transfer-private qubes_dom0 Vwi–tz-- 2.00g vm-pool
vm-pool qubes_dom0 twi—tz- 425.99g
vm-pool_meta0 qubes_dom0 ri-a-- 104.00m
vm-pool_meta1 qubes_dom0 ri-a-- 148.00m
[vm-pool_tdata] qubes_dom0 twi-- 425.99g
[vm-pool_tmeta] qubes_dom0 ewi-- 148.00m
vm-sys-net-private qubes_dom0 Vwi–tz-- 2.00g vm-pool vm-sys-net-private-#######-back
vm-sys-net-private-#######-back qubes_dom0 Vwi–tz-- 2.00g vm-pool
vm-sys-net-private-#######-back qubes_dom0 Vwi–tz-- 2.00g vm-pool vm-sys-net-private-#######-back
vm-sys-net-private-#######-back qubes_dom0 Vwi–tz-- 2.00g vm-pool vm-sys-net-private-#######-back
vm-sys-usb-private-snap qubes_dom0 Vwi–tz-- 2.00g vm-pool vm-default-dvm-private
vm-sys-usb-root-snap qubes_dom0 Vwi–tz-- 20.00g vm-pool
vm-sys-usb-volatile qubes_dom0 Vwi–tz-- 12.00g vm-pool
vm-sys-whonix-private qubes_dom0 Vwi–tz-- 2.00g vm-pool
vm-vault-private qubes_dom0 Vwi–tz-- 400.00g vm-pool vm-vault-private-#######-back
vm-vault-private-#######-back qubes_dom0 Vwi–tz-- 400.00g vm-pool
vm-whonix-gateway-18-private qubes_dom0 Vwi–tz-- 2.00g vm-pool
vm-whonix-gateway-18-root qubes_dom0 Vwi–tz-- 20.00g vm-pool
vm-work-private qubes_dom0 Vwi–tz-- 50.00g vm-pool vm-vault-work-#######-back
vm-work-private-#######-back qubes_dom0 Vwi–tz-- 50.00g vm-pool
vm-work-private-#######-back qubes_dom0 Vwi–tz-- 50.00g vm-pool vm-vault-work-#######-back
I found the appropriate line to modify by searching for the transaction ID
Update VG metadata;
vgck --updatemetadata qubes_dom0
Update pool metadata;
lvconvert --repair qubes_dom0/vm-pool
was not required in my case