Phantom Disk

[graytonio]

I am trying to migrate a vm back to its indended node and I get the following error.

2022-04-03 19:34:33 starting migration of VM 102 to node 'kratos' (10.0.0.61)
2022-04-03 19:34:33 replicating disk images
2022-04-03 19:34:33 start replication job
2022-04-03 19:34:33 guest => VM 102, running => 1925
2022-04-03 19:34:33 volumes =>
2022-04-03 19:34:34 (remote_prepare_local_job) no volumes specified
2022-04-03 19:34:34 end replication job with error: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=kratos' root@10.0.0.61 -- pvesr prepare-local-job 102-0 --last_sync 0' failed: exit code 255
2022-04-03 19:34:34 ERROR: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=kratos' root@10.0.0.61 -- pvesr prepare-local-job 102-0 --last_sync 0' failed: exit code 255
2022-04-03 19:34:34 aborting phase 1 - cleanup resources
2022-04-03 19:34:34 ERROR: migration aborted (duration 00:00:02): command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=kratos' root@10.0.0.61 -- pvesr prepare-local-job 102-0 --last_sync 0' failed: exit code 255
TASK ERROR: migration aborted

After some searching I found that for some reason there was a local vm disk on the local zfs storage target even though the vm has its disks on a nfs share over the network.



There is no file on the disk with this vm disk on it and I cannot migrate the vm because this disk image exists. I'm not sure what to do?

 

[fiona]

Hi,
please post the output of pveversion -v. Likely the disk was on ZFS in the past? The log also suggests there is a replication job configured, but if the VM is not actively using the disk on ZFS, the job can be deleted. The same is true for the orphaned disk itself, but I'd check what's on it first (e.g. fdisk -l /dev/zvol/rpool/data/vm-102-disk-0 and then mount with the appropriate command).

 

[graytonio]

pveversion -v

proxmox-ve: 7.1-1 (running kernel: 5.13.19-6-pve)
pve-manager: 7.1-12 (running version: 7.1-12/b3c09de3)
pve-kernel-helper: 7.1-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-11
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.4.157-1-pve: 5.4.157-1
pve-kernel-5.4.143-1-pve: 5.4.143-1
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-7
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-5
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-7
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-6
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

I did have a replication job that I had forgot about, removing it allowed the vm to be migrated. I'm still unable to delete the vm disk it directs me to the vm hardware screen to delete it but it's not on the hardware screen.

 

[fiona]

I did have a replication job that I had forgot about, removing it allowed the vm to be migrated. I'm still unable to delete the vm disk it directs me to the vm hardware screen to delete it but it's not on the hardware screen.

You can use qm rescan --vmid 102 from the CLI. Then the disk should show up as unused in the Hardware section.