Starting VM 102 failed: no such logical volume pve/vm-102-disk-0

[sopyak]

Hello,
pls, help to how to start vm with error : Starting VM 102 failed: no such logical volume pve/vm-102-disk-0
before restart VM 102 running normal, but after restart VM 102 can't start, when i saw at datacenter harddisk show at another node.
syslog :
Apr 12 08:16:53 node2 pve-ha-lrm[1213]: starting server
Apr 12 08:16:53 node2 pve-ha-lrm[1213]: status change startup => wait_for_agent_lock
Apr 12 08:16:53 node2 systemd[1]: Started pve-ha-lrm.service - PVE Local HA Resource Manager Daemon.
Apr 12 08:16:53 node2 systemd[1]: Starting pve-guests.service - PVE guests...
Apr 12 08:16:53 node2 pve-guests[1215]: <root@pam> starting task UPID:node2:000004C0:00000C0C:69DAF285:startall::root@pam:
Apr 12 08:16:53 node2 pve-guests[1216]: <root@pam> starting task UPID:node2:000004C1:00000C0E:69DAF285:qmstart:102:root@pam:
Apr 12 08:16:53 node2 pve-guests[1217]: start VM 102: UPID:node2:000004C1:00000C0E:69DAF285:qmstart:102:root@pam:
Apr 12 08:16:53 node2 pvesh[1215]: Starting VM 102
Apr 12 08:16:53 node2 pvesh[1215]: trying to acquire lock...
Apr 12 08:16:53 node2 pvesh[1215]: OK
Apr 12 08:16:55 node2 pve-guests[1217]: no such logical volume pve/vm-102-disk-0
Apr 12 08:16:55 node2 pvesh[1215]: Starting VM 102 failed: no such logical volume pve/vm-102-disk-0
Apr 12 08:16:55 node2 pvesh[1215]: Starting VM 115
Apr 12 08:16:56 node2 pve-guests[1216]: <root@pam> starting task UPID:node2:000004CA:00000CD7:69DAF287:qmstart:115:root@pam:
Apr 12 08:16:56 node2 pve-guests[1226]: start VM 115: UPID:node2:000004CA:00000CD7:69DAF287:qmstart:115:root@pam:
Apr 12 08:16:56 node2 systemd[1]: Created slice qemu.slice - Slice /qemu.
Apr 12 08:16:56 node2 systemd[1]: Started 115.scope.
Apr 12 08:16:56 node2 kernel: tap115i0: entered promiscuous mode
---------



regards,
sopyak

 

[psalkiewicz]

Hi,

The hard disk is on another node. The local-lvm datastore is local to the host - not a shared storage. So when a virtual machine failed on one host it cannot be restarted on the other. You have to move the virtual machine back to the other host or migrate the disk to this particular node.

 

[d.oishi]

Based on the screenshot, VM102 exists on node2, but the issue is that the VM disk vm-102-disk-0 exists on local-lvm of Server3.

I am not sure why vm-102-disk-0, which should originally have been on local-lvm of node2, was moved. However, in this state, it should not be possible to move the VM or its storage using Proxmox features such as VM migration or storage migration.

If you want to move the VM, move /etc/pve/nodes/Servername/qemu-server/vmid.conf to the node where the storage exists.
If you want to move the storage, move vm-102-disk-0 to the node where the VM exists.

 

[sopyak]

Based on the screenshot, VM102 exists on node2, but the issue is that the VM disk vm-102-disk-0 exists on local-lvm of Server3.

I am not sure why vm-102-disk-0, which should originally have been on local-lvm of node2, was moved. However, in this state, it should not be possible to move the VM or its storage using Proxmox features such as VM migration or storage migration.

If you want to move the VM, move /etc/pve/nodes/Servername/qemu-server/vmid.conf to the node where the storage exists.
If you want to move the storage, move vm-102-disk-0 to the node where the VM exists.

thank you very much for the idea, now i can start my vm
love you,