Migration failed - Error: migration aborted

U

unassassinable

New Member
Nov 16, 2023
26
0
1
I can interact with my VM fine in console, but I cannot migrate it to another node in the cluster. Other VMs I do not have such problem.

Task log shows
Code: 
task started by HA resource agent
2023-12-15 10:49:35 starting migration of VM 106 to node 'cobra-s-pm01' (10.1.0.10)
2023-12-15 10:49:36 found local disk 'SAN-VMStorage:vm-106-disk-3' (attached)
2023-12-15 10:49:36 found generated disk 'SAN-VMStorage:vm-106-disk-4' (in current VM config)
2023-12-15 10:49:36 found local disk 'SAN-VMStorage:vm-106-disk-5' (attached)
2023-12-15 10:49:36 can't migrate local disk 'SAN-VMStorage:vm-106-disk-4': can't get size of '/dev/VMStorage/vm-106-disk-4':   Failed to find logical volume "VMStorage/vm-106-disk-4"
2023-12-15 10:49:36 ERROR: Problem found while scanning volumes - can't migrate VM - check log
2023-12-15 10:49:36 aborting phase 1 - cleanup resources
2023-12-15 10:49:36 ERROR: migration aborted (duration 00:00:02): Problem found while scanning volumes - can't migrate VM - check log
TASK ERROR: migration aborted

Likewise when I shutoff the VM, HA fails to start it up with the following error:
Code: 
TASK ERROR: can't activate LV '/dev/VMStorage/vm-106-disk-4':   Failed to find logical volume "VMStorage/vm-106-disk-4"

qm start 106
Code: 
service 'vm:106' in error state, must be disabled and fixed first
command 'ha-manager set vm:106 --state started' failed: exit code 255

I'm not sure where to look for this...It should be noted that is VM is just a fresh install of the OS. Not critical. I already have a new VM spinning up as a replacement incase it's the VM that's screwed. I would like to know if it is the storage in case I should expect this problem again with a future VM.
 
Last edited:
Hi,
unassassinable said:
I can interact with my VM fine in console, but I cannot migrate it to another node in the cluster. Other VMs I do not have such problem.

Task log shows
Code: 
task started by HA resource agent
2023-12-15 10:49:35 starting migration of VM 106 to node 'cobra-s-pm01' (10.1.0.10)
2023-12-15 10:49:36 found local disk 'SAN-VMStorage:vm-106-disk-3' (attached)
2023-12-15 10:49:36 found generated disk 'SAN-VMStorage:vm-106-disk-4' (in current VM config)
2023-12-15 10:49:36 found local disk 'SAN-VMStorage:vm-106-disk-5' (attached)
2023-12-15 10:49:36 can't migrate local disk 'SAN-VMStorage:vm-106-disk-4': can't get size of '/dev/VMStorage/vm-106-disk-4':   Failed to find logical volume "VMStorage/vm-106-disk-4"
2023-12-15 10:49:36 ERROR: Problem found while scanning volumes - can't migrate VM - check log
2023-12-15 10:49:36 aborting phase 1 - cleanup resources
2023-12-15 10:49:36 ERROR: migration aborted (duration 00:00:02): Problem found while scanning volumes - can't migrate VM - check log
TASK ERROR: migration aborted

Likewise when I shutoff the VM, HA fails to start it up with the following error:
Code: 
TASK ERROR: can't activate LV '/dev/VMStorage/vm-106-disk-4':   Failed to find logical volume "VMStorage/vm-106-disk-4"
Click to expand...
you can list your logical volumes with lvs. It sounds like the generated cloudinit disk is not there. Did you do any changes to the cloundinit settings? Please share the output of pveversion -v and qm config 106 --current.

unassassinable said:
qm start 106
Code: 
service 'vm:106' in error state, must be disabled and fixed first
command 'ha-manager set vm:106 --state started' failed: exit code 255
Click to expand...
You need to set the HA state to disabled first: https://pve.proxmox.com/pve-docs/chapter-ha-manager.html#ha_manager_error_recovery

unassassinable said:
I'm not sure where to look for this...It should be noted that is VM is just a fresh install of the OS. Not critical. I already have a new VM spinning up as a replacement incase it's the VM that's screwed. I would like to know if it is the storage in case I should expect this problem again with a future VM.
Click to expand...
Did you already boot it successfully after installation or was this the first start attempt?
 
lvs
Code: 
root@cobra-s-pm04:~# lvs
  LV            VG          Attr       LSize  Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  vm-105-disk-0 FileStorage -wi-a----- 32.00g                                                    
  vm-100-disk-0 VMStorage   -wi-a----- 20.00g                                                    
  vm-101-disk-3 VMStorage   -wi-a-----  4.00m                                                    
  vm-101-disk-4 VMStorage   -wi-a-----  4.00m                                                    
  vm-101-disk-5 VMStorage   -wi-a----- 80.00g                                                    
  vm-102-disk-0 VMStorage   -wi-a----- 50.00g                                                    
  vm-102-disk-2 VMStorage   -wi-a----- 50.00g                                                    
  vm-102-disk-3 VMStorage   -wi-a----- 50.00g                                                    
  vm-103-disk-0 VMStorage   -wi-a-----  4.00m                                                    
  vm-103-disk-1 VMStorage   -wi-a-----  4.00m                                                    
  vm-103-disk-2 VMStorage   -wi-a----- 80.00g                                                    
  vm-104-disk-0 VMStorage   -wi-a-----  4.00m                                                    
  vm-104-disk-1 VMStorage   -wi-a-----  4.00m                                                    
  vm-104-disk-2 VMStorage   -wi-a----- 80.00g                                                    
  vm-105-disk-3 VMStorage   -wi-a-----  4.00m                                                    
  vm-105-disk-4 VMStorage   -wi-a-----  4.00m                                                    
  vm-105-disk-5 VMStorage   -wi-a----- 80.00g                                                    
  vm-106-disk-3 VMStorage   -wi-a-----  4.00m                                                    
  vm-106-disk-5 VMStorage   -wi-a----- 80.00g                                                    
  vm-107-disk-3 VMStorage   -wi-ao----  4.00m                                                    
  vm-107-disk-4 VMStorage   -wi-ao----  4.00m                                                    
  vm-107-disk-5 VMStorage   -wi-ao---- 80.00g                                                    
  vm-108-disk-0 VMStorage   -wi-a-----  4.00m                                                    
  vm-108-disk-1 VMStorage   -wi-a-----  4.00m                                                    
  vm-108-disk-2 VMStorage   -wi-a----- 80.00g                                                    
  vm-109-disk-0 VMStorage   -wi-------  4.00m                                                    
  vm-109-disk-1 VMStorage   -wi-------  4.00m                                                    
  vm-109-disk-2 VMStorage   -wi------- 80.00g                                                    
  vm-110-disk-0 VMStorage   -wi-------  4.00m                                                    
  vm-110-disk-1 VMStorage   -wi-------  4.00m                                                    
  vm-110-disk-2 VMStorage   -wi------- 80.00g                                                    
  data          pve         twi-a-tz-- 65.32g             0.00   1.60                            
  root          pve         -wi-ao---- 43.77g                                                    
  swap          pve         -wi-ao----  8.00g
[/code

pveversion -v
[code]
root@cobra-s-pm04:~# pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve)
pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.2-1
proxmox-backup-file-restore: 3.1.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-2
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.4
pve-qemu-kvm: 8.1.2-4
pve-xtermjs: 5.3.0-2
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1

qm config 106 --current
Code: 
root@cobra-s-pm04:~# qm config 106 --current
bios: ovmf
boot: order=virtio0;ide0;ide2;net0
cores: 2
cpu: host
efidisk0: SAN-VMStorage:vm-106-disk-3,efitype=4m,pre-enrolled-keys=1,size=528K
ide0: none,media=cdrom
ide2: none,media=cdrom
machine: pc-q35-8.1
memory: 4096
meta: creation-qemu=8.1.2,ctime=1702500528
name: cobra-s-dns01
net0: virtio=BC:24:11:2D:83:BB,bridge=vmbr1,tag=300
numa: 0
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=cccc2c65-ec85-4094-88a8-3a3dfaab1d9e
sockets: 2
tpmstate0: SAN-VMStorage:vm-106-disk-4,size=4M,version=v2.0
vga: qxl
virtio0: SAN-VMStorage:vm-106-disk-5,iothread=1,size=80G
vmgenid: e6c35407-97f6-4d97-b673-7eda72844850

Did you already boot it successfully after installation or was this the first start attempt?
Click to expand...
Yes, I had just installed and booted successfully at least once. Note that this is a windows server with BIOS: OVMF (UEFI). It has an EFI storage disk and a TPM storage disk. I mention this because when you asked me to run lvs above, I only see one 4MB disk. All my ohter servers have two (one for EFI and one for TPM). I did not remove it!
 
unassassinable said:
Code: 
tpmstate0: SAN-VMStorage:vm-106-disk-4,size=4M,version=v2.0
Click to expand...
Ah, because of the found generated disk in the log I had thought it would be a cloudinit disk, but we also print that for TPM states.

unassassinable said:
Yes, I had just installed and booted successfully at least once. Note that this is a windows server with BIOS: OVMF (UEFI). It has an EFI storage disk and a TPM storage disk. I mention this because when you asked me to run lvs above, I only see one 4MB disk. All my ohter servers have two (one for EFI and one for TPM). I did not remove it!
Click to expand...
Please check /run/qemu-server/106-swtpm.log and also check the system logs/journal for mentions of the disk.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom