Hi, I haven’t used Qubes for a month. I booted today and my Qubes failed to start: sys-net, sys-usb, sys-whonix, sys-firewall. This is the error message I get:
device-mapper: message ioctl on (252:8) failed: File exists
Failed to process message “create_snap 6745 6744”.
Thin pool qubes_dom0-vm–pool-tpool (252:8) already contain thin device with device_id 6745
Manual intervention may be required to remove device dev_id=6745 in thin pool metadata.
Optionally new thin volume with device_id=6745 can be manually added into a volume group.
WARNING: When uncertain how to do this, contact support!
Failed to suspend qubes_dom0/vm-pool with queued messages.
I’m not sure what to do with “thin pool”, and the solutions I could find was to re-install Qubes. I’m hoping to find some other options first before I re-install Qubes.
It’s rarely the case that you need to re-install Qubes, despite many
people promoting that as a solution.
In this case, your pool that contains the volumes used by each qube is
somewhat confused. The “snap” volume is created to store changes in
the root and the private storage volumes.
Make sure that you have an up to date backup.
Start with sys-net. Try to start it using qvm-start sys-net, and note
any error message.
you can try to clean manually using something like this:
lvremove qubes_dom0/vm-sys-net-root-snap
Report back
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I have tried “qvm-start sys-net” and got the same message. I tried “sudo lvremove qubes_dom0/vm-sys-net-root-snap” and got the message “Failed to find logical volume “qubes_dom0/vm-sys-net-roots-snap””.
I may be wrong, but I don’t think unman can view these pics as an email user of the forum. if you add | tee output.txt to each command then you should be able to capture the standard output as text and share it in email readable form.
You are right - I cant see them. This is not because I am an email
user: other email users may be able to see them… @m.ajar - can you summarise what is shown in the images?
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I tried | tee output.txt, but the output came out empty. This is copy and pasted:
[user@dom0 Desktop]$ qvm-start sys-net
Error: device-mapper: message ioctl on (252:9) failed: File exists
Failed to process message “create_snap 6745 6744”.
Thin pool qubes_dom0-vm–pool-tpool (252:9) already contain thin device with device_id 6745.
Manual intervention may be required to remove device dev_id=6745 in thin pool metadata.
Optionally new thin volume with device_id=6745 can be manually added into a volume group.
WARNING: When uncertain how to do this, contact support!
Failed to suspend qubes_dom0/vm-pool with queued messages.
[user@dom0 Desktop]$ lvremove qubes_dom0/vm-sys-net-root-snap
WARNING: Running as a non-root user. Functionality may be unavailable.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.199 (2024-07-12) and kernel driver (unknown version).
/run/lock/lvm/V_qubes_dom0:aux: open failed: Permission denied
Can’t get lock for qubes_dom0.
Cannot process volume group qubes_dom0
Leaving this issue for now as I have other things to troubleshoot. Will back-up my Qubes VM, re-install QubesOS and restore my Qubes VM to see if this resolves the issue.
