Option 'type' (zfspool) does not match existing storage configuration 'lvm' (500)

[nemolancerso]

can anyone tell me what the heck this means? there *IS* no existing storage configuration, as there is no storage configured, so I cant parse this at all.
the only references I find to this seem to be about moving VM's, but Im not doing that... as there is *no local storage* to move any VM's to....since it wont let me make any storage due to the storage that doesnt exist being lvm? im so confused.
it will let me make single disk zfs pools, but not anything else.
i should be able to manually create the topology I want by starting with a single disk, but id rather find out why proxmox wont let me use the UI.

(ignore the smart failures and weird disk sizes and consumer disks etc. this is not any kind of production and has nothing important - it mights become a plex host but im doing a whole bunch of promox experimenting right now)

 

[fabian]

please provide the contents of /etc/pve/storage.cfg and the output of "pveversion -v", thanks!

 

[nemolancerso]

actually it looks like it was the clustering i was experimenting with. when i started up other nodes it would work, and I would have had to really hack the quorum setting to get anything close to what I wanted so ..... ive nuked the whole cluster setup.
other nodes in the cluster did have lvm, so my current hypothesis is that's what it was objecting to, im just not sure why, because I have yet to encounter a "cluster storage config" location. and at the time it was objecting there was both lvm AND zfs in the cluster, so why it picked lvm i dont know. it also seems weird that it would allow zfs stripe, and not mirrors, if it thinks the cluster should only have lvm.
I like the way you can migrate within the cluster but it's just not worth the other hassles clustering adds for me.
this means i nuked the configuration that would have let me get useful results soooo unfortunately i cant do much with this post. made the post a little too quickly, but maybe it will help someone in the future, or a dev can keep in it mind to make it a bit smoother.