[SOLVED] qm remote migrate from single node to cluster from zfs storage to ceph storage getting error "...invalid bootorder: device 'sata0' does not exist'"

aluisell

Active Member
May 30, 2019
11
2
43
54
Hi folks,

I'm trying to manually migrate (live migration) of a VM from a single node proxmox to a proxmox cluster.
I have tried many different things, like checking the fingerprint, permission on the token, tried with vm online and offline, and many other but I can't get rid of the error device sata0 does not exist. Which by the way I also struggle to interprete. What it does refer to? I have also tried to backup and restore using PBS and that works with any problem.

Please find below the log of the error.

Any help would be much appreciated.

Regards

Andrea


vm configuration: Please note vmdatastore is zfs storage.
1753945430655.png


2025-07-31 08:25:05 remote: started tunnel worker 'UPID:pve-h1:00063BB2:006E4824:688B0C41:qmtunnel:406:root@pam!vmtransfer:'
tunnel: -> sending command "version" to remote
tunnel: <- got reply
2025-07-31 08:25:05 local WS tunnel version: 2
2025-07-31 08:25:05 remote WS tunnel version: 2
2025-07-31 08:25:05 minimum required WS tunnel version: 2
websocket tunnel started
2025-07-31 08:25:05 starting migration of VM 405 to node 'pve-h1' (192.168.0.1)
tunnel: -> sending command "bwlimit" to remote
tunnel: <- got reply
tunnel: -> sending command "bwlimit" to remote
tunnel: <- got reply
2025-07-31 08:25:05 found local disk 'vmdatastore:vm-405-disk-0' (attached)
2025-07-31 08:25:05 found local disk 'vmdatastore:vm-405-disk-1' (attached)
2025-07-31 08:25:05 mapped: net0 from OLan1_40GB to OLAN1_10GB
2025-07-31 08:25:05 Allocating volume for drive 'sata1' on remote storage 'oikisipiceph'..
tunnel: -> sending command "disk" to remote
tunnel: <- got reply
2025-07-31 08:25:05 volume 'vmdatastore:vm-405-disk-1' is 'oikisipiceph:vm-406-disk-0' on the target
2025-07-31 08:25:05 Allocating volume for drive 'efidisk0' on remote storage 'oikisipiceph'..
tunnel: -> sending command "disk" to remote
tunnel: <- got reply
2025-07-31 08:25:05 volume 'vmdatastore:vm-405-disk-0' is 'oikisipiceph:vm-406-disk-1' on the target
tunnel: -> sending command "config" to remote
tunnel: <- got reply
2025-07-31 08:25:06 ERROR: error - tunnel command '{"conf":"agent: 1\nbios: ovmf\nboot: order=sata0;sata1\ncores: 2\ncpu: x86-64-v2-AES\nefidisk0: oikisipiceph:vm-406-disk-1,format=raw,size=128K\nlock: migrate\nmachine: pc-i440fx-9.2+pve1\nmemory: 8196\nmeta: creation-qemu=9.2.0,ctime=1748541136\nname: Win10-3\nnet0: virtio=00:50:56:97:79:c0,bridge=OLAN1_10GB\nostype: win10\nsata1: oikisipiceph:vm-406-disk-0,format=raw,size=100G\nscsihw: virtio-scsi-single\nsmbios1: uuid=42170a4f-84e7-7b89-ff63-6050cf906f9b\nsockets: 2\nstartup: order=31\nvmgenid: 29ca23ce-25b9-4b75-a724-3ab60f36243e\n","cmd":"config","firewall-config":null}' failed - failed to handle 'config' command - invalid bootorder: device 'sata0' does not exist'
2025-07-31 08:25:06 aborting phase 1 - cleanup resources
tunnel: -> sending command "quit" to remote
tunnel: <- got reply
2025-07-31 08:25:07 ERROR: migration aborted (duration 00:00:02): error - tunnel command '{"conf":"agent: 1\nbios: ovmf\nboot: order=sata0;sata1\ncores: 2\ncpu: x86-64-v2-AES\nefidisk0: oikisipiceph:vm-406-disk-1,format=raw,size=128K\nlock: migrate\nmachine: pc-i440fx-9.2+pve1\nmemory: 8196\nmeta: creation-qemu=9.2.0,ctime=1748541136\nname: Win10-3\nnet0: virtio=00:50:56:97:79:c0,bridge=OLAN1_10GB\nostype: win10\nsata1: oikisipiceph:vm-406-disk-0,format=raw,size=100G\nscsihw: virtio-scsi-single\nsmbios1: uuid=42170a4f-84e7-7b89-ff63-6050cf906f9b\nsockets: 2\nstartup: order=31\nvmgenid: 29ca23ce-25b9-4b75-a724-3ab60f36243e\n","cmd":"config","firewall-config":null}' failed - failed to handle 'config' command - invalid bootorder: device 'sata0' does not exist'

TASK ERROR: migration aborted
 
Last edited:
your config is invalid -> change the bootorder to no longer reference a drive that doesn't exist, then it should work.
 
your config is invalid -> change the bootorder to no longer reference a drive that doesn't exist, then it should work.
Hi Fabian,

thanks so much, I went in the VM option and removed sata0 from the boot disks and that's worked. Sorry didn't noticed that it was not removed.
Regards

Andrea
 
  • Like
Reactions: fabian