Cloning and recovery problems on LVM-thin

Shadow2091

Member
Sep 25, 2019
14
1
8
32
I use LVM-thin as the main storage and have repeatedly noticed that cloning VMs or recovering using proxmox often means that the VM is broken if LVM-thin is used as the target storage. In Windows 10, this means that after cloning, the VM boots only in recovery mode and does not see a drives. Today, HassOS stopped working for me and after recovering using Proxmox, I encountered the same problem: when I turn on the VM, it cannot boot, the partition table on the virtual disk is damaged. After a long brainstorm, I found out that the problem is in LVM-thin. When recovering to qcow2 or to zfs (which traditionally works painfully slow even on good hardware), the machines start up successfully from backup and continue to work normally even if later migrating disks to LVM-thin storage. I am sure that the problem is precisely software, but I could not find any similar topics.
proxmox-ve: 6.2-1 (running kernel: 5.4.41-1-pve) pve-manager: 6.2-4 (running version: 6.2-4/9824574a) pve-kernel-5.4: 6.2-2 pve-kernel-helper: 6.2-2 pve-kernel-5.3: 6.1-6 pve-kernel-5.0: 6.0-11 pve-kernel-5.4.41-1-pve: 5.4.41-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 pve-kernel-5.3.18-3-pve: 5.3.18-3 pve-kernel-5.3.18-2-pve: 5.3.18-2 pve-kernel-5.0.21-5-pve: 5.0.21-10 pve-kernel-5.0.15-1-pve: 5.0.15-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: not correctly installed ifupdown2: 2.0.1-1+pve8 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.15-pve1 libproxmox-acme-perl: 1.0.4 libpve-access-control: 6.1-1 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.1-2 libpve-guest-common-perl: 3.0-10 libpve-http-server-perl: 3.0-5 libpve-storage-perl: 6.1-8 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.2-1 lxcfs: 4.0.3-pve2 novnc-pve: 1.1.0-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.2-1 pve-cluster: 6.1-8 pve-container: 3.1-6 pve-docs: 6.2-4 pve-edk2-firmware: 2.20200229-1 pve-firewall: 4.1-2 pve-firmware: 3.1-1 pve-ha-manager: 3.0-9 pve-i18n: 2.1-2 pve-qemu-kvm: 5.0.0-2 pve-xtermjs: 4.3.0-1 qemu-server: 6.2-2 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-1 zfsutils-linux: 0.8.4-pve1
 
I use LVM-thin almost exclusively with both Windows and Linux (Ubuntu) VMs and have never had this problem with either cloning (which I do more often) or restoring (which I've only had to do on Windows this past week). I'll be following this thread in case anyone does offer a cause since I am so heavily LVM-thin dependent and don't want to run into it.
 
I also found out that the problem manifests itself exclusively with full cloning, linked-clone always works correctly.
 
I also found out that the problem manifests itself exclusively with full cloning, linked-clone always works correctly.
Oh, are you using templates? In case it changes anyone's logic into figuring out what the problem could be, I guess I should clarify that all of my clones are inherently full clones (since I don't use templates).
 
I have exactly the same problem. Linked clones work great. Full clone of debian system lands in uefi due to not discovering any drives.
 
I tried full cloning to a different storage pool with same results. I've got 'z' near every LV in my cluster and VMs are broken after full clone :(((((((((((
 

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!