LXC Rootfs - can't migrate to a remote disk I choose

V

voarsh

Member
Nov 20, 2020
218
19
23
28
When i migrate an LXC I get:
ERROR: migration aborted (duration 00:00:00): storage 'Seagate1TBDriveThree' is not available on node 'pve'

Why can't I not choose a disk on remote?
 
Normaly you can. What Proxmoxversion did you use?
Code: 
pveversion -v
 
fireon said:
Normaly you can. What Proxmoxversion did you use?
Code: 
pveversion -v
Click to expand...
Hmm. Not working on 6.4-8.
1627130696086.png

Code: 
proxmox-ve: 6.4-1 (running kernel: 5.4.119-1-pve)
pve-manager: 6.4-8 (running version: 6.4-8/185e14db)
pve-kernel-5.4: 6.4-3
pve-kernel-helper: 6.4-3
pve-kernel-5.4.119-1-pve: 5.4.119-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-6
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
 
Last edited:
In fact, at LXC this seems to be different. Also on 7.0 the target storage must exist. On KVM you can choose the disk.

To test this, create a storage with the same name on the target machine. Then it should work.
Test it with another type of storage. It would be interesting to see if it is automatically converted. E.g. from ZFS to LVM-Thin, or other combinations.
 
fireon said:
To test this, create a storage with the same name on the target machine. Then it should work.
Click to expand...
How would I do this? I need to have a spare disk lying around?
Create an NFS/SMB store, of of the disk I wish to migrate to on the target server node? - won't work
Can someone at Proxmox chime in on this issue?
 
Last edited:
You must log in or register to reply here.
Top Bottom