[SOLVED] Reimaged node showing original LVM name/unavailable

[arjones5]

I recently had a cascading disk failure that drove me to reimage one of my nodes. Everything went well with one small exception: the data volume (OS vs data) is showing up with the original name prior to reimaging. I wanted to rename the data volume so it was unique per node (learned that the hard way). While I can use the volume as expected, it shows as inactive but enabled in the interface. This would make sense if it was looking for the legacy volume "data-raid" but it's not seeing the "data-prod01" that was configured during reimage with the proverbial "no such logical volume data-raid/data-raid (500)" error.

My reimage method was delnode and start fresh, restoring images from backup. Did I miss a step specific to the volumes?

 

[arjones5]

cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content vztmpl,backup,iso

lvmthin: local-lvm
        thinpool data
        vgname pve
        content rootdir,images

lvm: data
        disable
        vgname data
        content images,rootdir
        nodes prox-prod01
        shared 0

lvmthin: data-raid
        thinpool data-raid
        vgname data-raid
        content rootdir,images
        nodes prox-prod01

 

[arjones5]

Fixed by correcting the storage.cfg file, renaming the lvmthin config to the correct/new volume label.

cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content vztmpl,backup,iso


lvmthin: local-lvm
        thinpool data
        vgname pve
        content rootdir,images


lvm: data
        disable
        vgname data
        content images,rootdir
        nodes prox-prod01
        shared 0


lvmthin: data-prod01
        thinpool data-prod01
        vgname data-prod01
        content rootdir,images
        nodes prox-prod01

Partial credit to this post for the breadcrumb I needed: https://forum.proxmox.com/threads/how-do-i-fix-this-local-lvm-no-such-logical-volume.152650/