[SOLVED] PVE 5.4: Second local lvm-thin storage?

[marsian]

Hi,
we recently added another node to a cluster, based on PVE 5.4 . The difference between that new node and the existing ones is, that because of its capabilties it has a second RAID array included, that provides another logical storage to the system (/dev/sdb).

We now wanted to add that second storage via the GUI, and while it shows up in "Disks" (sda & sdb), we also added it via "LVM-Thin" as another Thin-Pool (data2), but which did not show up anywhere as a storage target at all (not in the storage view in the system tree nor when adding a new VM as a target etc.).

After deleting it via CLI it has been removed from the "LVM-Thin" view, we can't add it again as e.g. Thinpool because the system says "No Disks unused".

Having to reinstall the PVE in worst-case, what would be the corrent way to add another LVM-thin storage to the system, as the way we thought to do it via the GUI looks like it's not the right one?

Thanks!

 

[dcsapak]

there are two layer to this,
1. the LVM-Thin Gui shows the configured thin pools on the disks of the node -> you need this for step 2 to work
2. in Datacenter->Storage you can add a 'lvmthin' storage -> this is what you need to see it when creating a vm, etc.

normally creating a lvm thinpool via the gui (step 1) has a checkbox where it does step 2 automatically...

 

[marsian]

Thanks for the information.

In our case we might have missed that Checkbox, but let's see if we can follow up based on that information.

As it currently looks like the deletion of the thinpool via CLI has removed the thinpool but did not "free" the drives itself to create another pool, what's your recommendation on this? Recreate the tinpool via CLI with the same name again or is there some other process you would propose?

 

[dcsapak]

Recreate the tinpool via CLI with the same name again

that is what i would do

 

[marsian]

Thanks, it worked!