After hard crash of QubesOS 4.3: Check of pool qubes_dom0/vm-pool failed

User Support General
1

I am running a QubesOS 4.3 setup with a MooltiPass hardware password manager integrated with the CTAP proxy. Works like a charm, but occasionally the system hard crashes when unplugging the MooltiPass. Until yesterday that was just inconvenient and rebooting brought everything back up.

Following a crash/reboot cycle yesterday, dom0 boots and the GUI is rudimentarily functional, but qubesd and all sys-* appVMs fail to start.

qubes is stuck in a restart loop that systemctl start/stop can overcome.

Using systemctl to start the appVM services, however, fails with

Error: Check of pool qubes_dom0/vm-pool failed (status:64). Manual repair required!

I attempted the repair unsing

PROMPT:# lvchange -an /dev/qubes_dom0/vm*
PROMPT:# lvconvert --repair qubes_dom0/vm-pool

That, unfortunately produces the error

Transaction ID 341668 from poom "qubes_dom0/vm-pool" does not match repaired transaction id 341667 from /dev/qubes_dom0/lvoll_pmspare.

Is that fixable and if yes, how?

Thank you for any pointers.

2

When you get your system working again, can you share the journal of the last boot of dom0 and sys-usb?

On dom0:

sudo journalctl -b -1

And for sys-usb, still on dom0, the file:

/var/log/xen/console/guest-sys-usb.log

I don’t know.

3

Search the forum for "repaired transaction id", e.g.