[SOLVED] Migration failure due to ISO storage

n01k

Member
Nov 13, 2019
12
1
23
39
Ontario Canada
tweakmyskills.it
Hello everyone, I have seem to run into an issue that I cannot recovery from at this time.

Last week, I wanted to migrate a VM from one host to another. I tried to do so but was abrulplly told that it cannot happen due to the following:

Used shared storage 'QNAPISO' is not online on source node!
2021-02-19 14:47:27 starting migration of VM 105 to node 'PROXHOST' (10.16.61.104)
2021-02-19 14:47:27 ERROR: Failed to sync data - storage 'QNAPISO' is not online
2021-02-19 14:47:27 aborting phase 1 - cleanup resources
2021-02-19 14:47:27 ERROR: migration aborted (duration 00:00:01): Failed to sync data - storage 'QNAPISO' is not online
TASK ERROR: migration aborted



Used shared storage 'QNAPISO' is not online on source node!
2021-02-19 14:57:51 starting migration of VM 105 to node 'PROXHOST' (10.16.61.104)
2021-02-19 14:57:52 starting VM 105 on remote node 'PROXHOST'
2021-02-19 14:57:53 [PROXHOST] storage 'QNAPISO' is disabled
2021-02-19 14:57:53 ERROR: online migrate failure - remote command failed with exit code 255
2021-02-19 14:57:53 aborting phase 2 - cleanup resources
2021-02-19 14:57:53 migrate_cancel
2021-02-19 14:57:55 ERROR: migration finished with problems (duration 00:00:04)
TASK ERROR: migration problems



Now I realize that the QNAPISO shared storage was a problem so I tried to remove it and this is what I was left with:

ProxIssue2.PNG



I have tried to remove the CD/DVD Drive but it won't remove. I have removed the QNAPISO path from the storage view.


I have gone and deleted the lock for file 105 but I can't the VM to shut down or anything.

ProxIssue.PNG






root@PROXHOST:/var/lock/qemu-server# cd /run/lock/qemu-server/
root@PROXHOST:/run/lock/qemu-server# ls
lock-104.conf lock-105.conf lock--1.conf
root@PROXHOST:/run/lock/qemu-server# rm lock-105.conf
root@PROXHOST:/run/lock/qemu-server# ls
lock-104.conf lock--1.conf




Any ideas or suggestions on how I can get this VM to shutdown?

I cannot enable QNAPISO anymore.



Thank you
 
Last edited:
qm unlock 105 then qm shutdown 105 should do the trick. For best results, don't go around deleting random lock files ;)

I have tried to remove the CD/DVD Drive but it won't remove. I have removed the QNAPISO path from the storage view.
IDE CD drives are not hotpluggable, which is why they require a full VM reboot. After that, migration should be working.
 
  • Like
Reactions: n01k
qm unlock 105 then qm shutdown 105 should do the trick. For best results, don't go around deleting random lock files ;)


IDE CD drives are not hotpluggable, which is why they require a full VM reboot. After that, migration should be working.


Thank you Stefan for the reply.

I will not delete random files anymore, I was just going based on some search results.

I just tried the above command and my putty session just sat there after I ran qm shutdown 105

oot@PROXHOST:~# qm unlock 105
root@PROXHOST:~# qm shutdown 105
^CVM quit/powerdown failed
root@PROXHOST:~#
 
Last edited:
I've found my own solution to this and am able to have my VMs functional now. For anybody coming across this post in the future, this worked for me.

Seeing as I was getting an error regarding the following that I tried to remove:

ide2: QNAPISO:iso/virtio-win-0.1.171.iso,media=cdrom,size=363020K

I have tried qm unlock 105 and qm shutdown 105 without success.

I tried to run QM shutdown 105 but it failed.

root@CALNPROXM01:~# qm shutdown 105
VM quit/powerdown failed


I found a discussion regarding the VM configuration file located at:

/etc/pve/qemu-server/<VMID>.conf

So I read the config file for VM 105 and found the ide2 line, which was pointing to a QNAP source that is no longer existent.

I removed the the line for ide2 and saved my configuration.

I ran qm stop "VMID"

Immediatly, the VM powered off.
I powered it back on and it's up and functional now.


My only concern with proxmox is that if IDE drives are not Hot-Swappable, the system should error out when the user tries to remove it from the system. This was my fault but I was not aware of such.


Anyways, thank you.
 
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!