Failed Starwind converstion, LVM nearly full

[daleharris]

Hello,
I attempted to convert a physical PC into a VM using the Starwind converter.

Unfortunately, the process failed because of space limitations, but it left behind a partial conversion.

I had to clear all the ISOs from my Proxmox node to ensure it could function correctly. For context, I have two identical nodes: Node 1 is at 87% storage capacity, while Node 2 is at 31%.

Is there a safe way to remove this partial conversion?

[yaroslav (staff)]

Yes, you can delete it from the underlying storage.

[Meilin]

I’ve run into a similar issue when a Starwind conversion failed on my Proxmox setup. What worked for me was manually checking the storage directory (usually /var/lib/vz/images/) and cleaning up any half-created VM disks. Once I deleted the leftover .qcow2 files, my node went back to normal. Just make sure you double-check the VM ID before removing anything so you don’t delete the wrong image.

[yaroslav (staff)]

Nice point.
Thanks for sharing!

[olivianaylor]

Good

[Joseph]

Hello,
I attempted to convert a physical PC into a VM using the Starwind converter.

Unfortunately, the process failed because of space limitations, but it left behind a partial conversion.

I had to clear all the ISOs from my Proxmox node to ensure it could function correctly. For context, I have two identical nodes: Node 1 is at 87% storage capacity, while Node 2 is at 31%.
crossy road
Is there a safe way to remove this partial conversion?

o address the issue of the partial conversion left behind, have you checked if there are any specific logs or temporary files created by the Starwind converter that you can safely delete?