Dom0 update fail over tor

[WhiteShadow]

Hey,
While running dom0 update via whonix-gw as updateVM recieve next error:

Checking for dom0 updates...
Unable to detect release version (use '--releasever' to specify release version)
Unable to detect release version (use '--releasever' to specify release version)
           - Curl error (6): Coudn't resolve host name for https://yum.qubes-os.org/r4.3/current/host/fc41/repodata/repomd.xml.metalink [Could not resolve host: yum.qubes-os.org]
Error: failed to download metadata for repo 'qubes-dom0-current': Cannot prepare internal mirrorlist: Curl error (6): Coudn't resolve host name for https://yum.qubes-os.org/r4.3/current/host/fc41/repodata/repomd.xml.metalink [Could not resolve host: yum.qubes-os.org]
Failed to check for dom0 updates

After reboot any qubes start with next error:

Sudo lvremove qubes_dom0/vm-sys-net-private-snap

device-mapper: message ioctl on (252:9) failed: File exists
Failed to process message "create_snap 182 22":
Thin pool qubes_dom0-vm--pool-tpool. (252:9) already contain thin device with device:id 182.
Manual intervention may be required to remove device dev_id=182 in thin pool metadata.
Optoonally new thin volume with device_id=182 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.
Failed to update pool qubes_dom0/vm-pool.

`xl list
Name       ID   Mem    VCPUs   State  Time(s)
Domain-0 0     4080    16           r-----   50.1

I never tried to set dom0 16vCPU (shocked).

Another indicator:

sudo lvm lvs
vm-sys-net-private-snap   qubes_dom0  Vwi-a-tz--  2.00g  vm-pool  vm-default-dvm-private  0.00

How to handle that?

Found same issue appeared at 4.2.4:

Logical Volume "vm-sys-<vm-name>-root-snap" already exists in volume group "qubes_dom0"

My sys-usb and sys-net machines aren’t booting, and when I try a manual restart I get the error in the title. I know there’s a thread about this on GitHub, and would post there, but I don’t have an account and really don’t want one.

No VMs starting on Boot, "Logical Volume Already Exists in dom0", lvremove not working

I have been troubleshooting this for the past 2 hours to no avail… time to make a forum post. After Qubes froze on me, I hardware reset and then I was unable to type in my user password, but my LUKS encryption I could type in. I disabled my autostart for my USB Qube and now I am able to login. When I go to start a qube, I get hit with these errors. Qube Status: sys-net (also duplicate errors for sys-firewall, sys-whonix) Qube sys-net has failed to start: Logical Volume “vm-sys-net-root-snap…

[WhiteShadow]

@unman
Found that you handle few support requests in same situation from another users. May I ask you for advice how to handle that issue?

I can keep broken dom0 in that state for few days, in case more evidence of issue requested.

[WhiteShadow]

Perform clean installation after 2 days without any comment.
After ring of updates for clean system, shutdown and boot in full updates system:

[dom0] error starting Qube!
Logical volume "vm-sys-net-private-snap" already exist into volume group qubes_dom0"

Solved by command:
sudo lvremove qubes_dom0/vm-sys-net-private-snap.

• This time *-volatile image exist.
• Before last shutdown sys-net start from reboot by updater with issue, of qrexec timeout.