[SOLVED] Cloning/Restoring/Moving never finishes

[shaggyroo]

Hi!

I recently noticed some issues with my PVE when trying to move a CT. After some testing I also realized that there was an issue with restoring and cloning as well. The issue being that the jobs never complete. If I try to move a CT to a new disk the log window just says "no content" and does not finish after at least an hour ( for a 8gb volume). Cloning from a template or restoring from a backup gives some output but then stops and never completes:

I'm unsure how to debug this though as I am not seeing any obvious errors. So if anyone has an idea I would be very grateful for some input.

 

[shaggyroo]

The same is true in CLI

$ pct clone 104 113 --storage hdd-img --full true
create full clone of mountpoint rootfs (hdd-img:104/base-104-disk-0.raw)
Formatting '/mnt/data/hdd-img//images/113/vm-113-disk-1.raw', fmt=raw size=8589934592 preallocation=off
Creating filesystem with 2097152 4k blocks and 524288 inodes
Filesystem UUID: d0c623c9-0f26-49fe-b068-efa9ee04656a
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

 

[bbgeek17]

Check "dmesg" and "journalctl -f" during the clone. My guess is that your disk (hdd judging by the name?) chokes or is dyeing.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[shaggyroo]

Thank you for the answer! I did try looking through "dmesg" and "journalctl" but I couldn't see anything obvious. A clone actually just went though now after 2 hours for a 8gb template, so perhaps its just extremely slow? I tried moving the newly cloned CT and that was very fast, but other "older" containers are still slow. I'll give it some more time an keep checking "dmesg" and "journalctl -f", thanks!

 

[shaggyroo]

It seems the move also finished after around 5 hours so I guess I was just impatient. Although it feel like a really long time for 20gb.

Thank you for your time @bbgeek17 !