VM failed to reboot after migration on HA - disk not found

Malozorus

New Member
Jul 25, 2023
3
0
1
hi, i've recently set up a VM on one node of a HA proxmox cluster. Added storage drive in lvm-thin format for both node on the cluster then set HA activate for my VM. Unfortunatly this morning my VM migrate from one node to another, leaving all the disk on the first node, trying to reboot on the second node where the storage drive is availble but not the vm disk thus failed and can't migrate back to the orginal node. This storage contain important log of a postgres DB, and i can't delete it, i need to recover the data and puting back all the service in work as soon as possible. FIrst i know i made major mistake in this configuration because i'm pretty new to proxmox and server management. Can someone please help me recover the data ?
 
Last edited:
hi, i've recently set up a VM on one node of a HA proxmox cluster. Added storage drive in lvm-thin format for both node on the cluster then set HA activate for my VM. Unfortunatly this morning my VM migrate from one node to another, leaving all the disk on the first node, trying to reboot on the second node where the storage drive is availble but not the vm disk thus failed and can't migrate back to the orginal node. This storage contain important log of a postgres DB, and i can't delete it, i need to recover the data and puting back all the service in work as soon as possible. FIrst i know i made major mistake in this configuration because i'm pretty new to proxmox and server management. Can someone please help me recover the data ?
LVM-Thin is not a shared storage, only if you use it on top of iSCSI. https://pve.proxmox.com/wiki/Storage So thats normal
You can take a look at /etc/pve/qemuserver at the current node (where the vm does not work) and move the file to the other node with mv. Example:

Code:
root@PMX4:/etc/pve/qemu-server# ls
103.conf  105.conf  107.conf  9000.conf
104.conf  106.conf  108.conf  9001.conf

root@PMX4:/etc/pve/qemu-server# mv 103.conf ../nodes/PMX
PMX4/ PMX5/ PMX6/

root@PMX4:/etc/pve/qemu-server# mv 103.conf ../nodes/PMX4/
config       lxc/         priv/        pve-ssl.pem
lrm_status   openvz/      pve-ssl.key  qemu-server/

root@PMX4:/etc/pve/qemu-server# mv 103.conf ../nodes/PMX5/qemu-server/

This will make your vm be available at the other node again, so it hopefully finds its storage again, so youll be able to start the vm.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!