Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
A
@archw Ignore that entire post...user error. I have two networks that are spelled very close to the same thing and I was using the wrong one.
O
Can you write exactly what you would expect to be written as a "pre written" text?
@archw
Scratch that one.....I should have googled first. I saw that someone suggested deleting the cache.json.gz file. I did and ran it again and it worked.
@fesch
In the words of Ronald Reagan "I don't recall the answer to that question" 🙂
If I remember correctly (subject to the after effects of many happy hours since 5-12-24), I ended up rebooting the host that had that VM. It has never done it since.
Arch
Coalesce isn't instant, and yes, as soon you remove a snapshot, there's some work to do from the storage perspective 🙂
@Danp said in Backup fails with "VM_HAS_VUSBS" error:
@olivierlambert Could this be added as an option under the backup's Advanced settings area?
Probably, just taking care of telling people it will unplug the device for few seconds.
F
@archw said in Backup fails with "all targets have failed, step: writer.beforeBackup()":
@florent Where would I find that log? I assume its in /var/log but which file?
For a xoa it's in journalctl -u xo-server
from source, it depends how you did setup XO
If this specific VM is causing issue, you can fallback on Clonezilla or something similar 🙂