VM/CTs missing their volumes (which are on another host)

hotelrwanda

Member
Apr 20, 2022
16
2
8
I have two Proxmox hosts. One of them had some networking issues and I turned it off, brought in my office for troubleshooting, and it's now back up and running.
The problem now is that I have 2 containers and one vm that appear to be on the second host (shut down), but their associated disk volumes are on the "broken" host.
How can I "bring them together"? Can I move the volumes from px1 to px2 of the vm configs from px2 to px1 or something like that?

If I try to migrate them, I get this error:
Code:
2022-12-09 00:09:10 starting migration of CT 100 to node 'px1' (10.10.10.5)
2022-12-09 00:09:10 found local volume 'local-lvm:vm-100-disk-0' (in current VM config)
2022-12-09 00:09:11 ERROR: storage migration for 'local-lvm:vm-100-disk-0' to storage 'local-lvm' failed - no such logical volume pve/vm-100-disk-0
2022-12-09 00:09:11 aborting phase 1 - cleanup resources
2022-12-09 00:09:11 ERROR: found stale volume copy 'local-lvm:vm-100-disk-0' on node 'px1'
2022-12-09 00:09:11 start final cleanup
2022-12-09 00:09:11 ERROR: migration aborted (duration 00:00:01): storage migration for 'local-lvm:vm-100-disk-0' to storage 'local-lvm' failed - no such logical volume pve/vm-100-disk-0
TASK ERROR: migration aborted
 
Well, it was easier than expected.
I moved the config files from the host that had the configs to the one that had the volumes, so /etc/pve/nodes/px2/lxc/ and /etc/pve/nodes/px2/qemu-server/ to /etc/pve/nodes/px1/lxc/ and /etc/pve/nodes/px1/qemu-server/, respectively.
 
Hi,
glad you were able to solve the issue :)

Did you configure HA for the guests? That would explain why they were moved, but HA requires shared or replicated storage as a precondition.
Let's just say "there was an attempt" :)
I started setting up HA for the guests, but I stopped before being completely done with the settings. Thanks for the link, it makes sense, I didn't have shared storage set up for ct and vm volumes.