Wanted to test out my backups. I have 1 LXC that fails almost immediately when attempting restore via the web GUI. The failure message in the status window is: "TASK ERROR: unable to detect disk size - please specify mp0 (size)". The syslog contains the following:
Jan 01 08:50:00 vmhost01 systemd[1]: Starting Proxmox VE replication runner...
Jan 01 08:50:01 vmhost01 systemd[1]: Started Proxmox VE replication runner.
Jan 01 08:50:42 vmhost01 pvedaemon[17854]: <root@pam> starting task UPID:vmhost01:00003A2E:0274772D:5C2B7032:vzrestore:509:root@pam:
Jan 01 08:50:43 vmhost01 pvedaemon[14894]: unable to detect disk size - please specify mp0 (size)
Jan 01 08:50:43 vmhost01 pvedaemon[17854]: <root@pam> end task UPID:vmhost01:00003A2E:0274772D:5C2B7032:vzrestore:509:root@pam: unable to detect disk size - please specify mp0 (size)
Found thread with similar problem, but different workflow/use case: https://forum.proxmox.com/threads/moving-from-ext4-storage-raw-to-thick-provisioned-lvm.43508
"Show Configuration" output for this CT is:
arch: amd64
cores: 1
hostname: storage01
memory: 512
mp0: lxcdata:subvol-100-disk-2,mp=/media,backup=1
mp1: lxcdata:subvol-100-disk-3,mp=/torrents,backup=1
net0: name=eth0,bridge=vmbr0,gw=192.168.20.254,hwaddr=5A:52:E3:4C:83:17,ip=192.168.20.6/24,type=veth onboot: 1
ostype: debian
rootfs: lxcdata:subvol-100-disk-1,size=1G
startup: order=2
swap: 1024
pveversion -v output is as follows:
proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.3-6 (running version: 5.3-6/37b3c8df)
pve-kernel-4.15: 5.2-12
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.13.16-1-pve: 4.13.16-46
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: not correctly installed
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-43
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-34
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-5
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-31
pve-container: 2.0-31
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-16
pve-firmware: 2.0-6
pve-ha-manager: 2.0-5
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-43
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1
Jan 01 08:50:00 vmhost01 systemd[1]: Starting Proxmox VE replication runner...
Jan 01 08:50:01 vmhost01 systemd[1]: Started Proxmox VE replication runner.
Jan 01 08:50:42 vmhost01 pvedaemon[17854]: <root@pam> starting task UPID:vmhost01:00003A2E:0274772D:5C2B7032:vzrestore:509:root@pam:
Jan 01 08:50:43 vmhost01 pvedaemon[14894]: unable to detect disk size - please specify mp0 (size)
Jan 01 08:50:43 vmhost01 pvedaemon[17854]: <root@pam> end task UPID:vmhost01:00003A2E:0274772D:5C2B7032:vzrestore:509:root@pam: unable to detect disk size - please specify mp0 (size)
Found thread with similar problem, but different workflow/use case: https://forum.proxmox.com/threads/moving-from-ext4-storage-raw-to-thick-provisioned-lvm.43508
"Show Configuration" output for this CT is:
arch: amd64
cores: 1
hostname: storage01
memory: 512
mp0: lxcdata:subvol-100-disk-2,mp=/media,backup=1
mp1: lxcdata:subvol-100-disk-3,mp=/torrents,backup=1
net0: name=eth0,bridge=vmbr0,gw=192.168.20.254,hwaddr=5A:52:E3:4C:83:17,ip=192.168.20.6/24,type=veth onboot: 1
ostype: debian
rootfs: lxcdata:subvol-100-disk-1,size=1G
startup: order=2
swap: 1024
pveversion -v output is as follows:
proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.3-6 (running version: 5.3-6/37b3c8df)
pve-kernel-4.15: 5.2-12
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.13.16-1-pve: 4.13.16-46
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: not correctly installed
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-43
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-34
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-5
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-31
pve-container: 2.0-31
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-16
pve-firmware: 2.0-6
pve-ha-manager: 2.0-5
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-43
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1
