Proxmox 5.1 upgrade problem - lvm-thin disappears

[term]

When I upgraded from 4.4 to 5.1, I ran into a problem where the lvm-thin storage refused to start when the system was booting. I've forgotten the exact error code, but it was something along the lines of lvm2-activation.service error code 5.

This of course caused quite a panic, even though I had backups.

So, I'll leave this for the next guy, maybe it will be helpful. Stay calm and try the steps below.

lvconvert --repair pve/data  
Using default stripesize 64.00 KiB.  WARNING: recovery of pools without pool metadata spare LV is not automated.  WARNING: If everything works, remove pve/data_meta1 volume.  WARNING: Use pvmove command to move pve/data_tmeta on the best fitting PV.
lvchange -a y pve/data
lvs
systemctl status --full lvm2-activation.service
reboot

 

[Daniel P. Clark]

lvconvert --repair pve/data

doesn't work:

  WARNING: Not using lvmetad because config setting use_lvmetad=0.
  WARNING: To avoid corruption, rescan devices to make changes visible (pvscan --cache).
  Using default stripesize 64.00 KiB.
  Only inactive pool can be repaired.