@Akavickas It's showing those entries for "Data" and "Data2" on the "ProxmoxGT" server because of how they're configured in the "Storage" part of the Datacenter err... level.
As an example, this is a screenshot of the Storage part of my homelab cluster:
If I double click on the "local-zfs" entry there, this window open up:
The "Nodes" entry there tells Proxmox what hosts/nodes the storage is supposed to appear on.
If you go to the Storage area in the Datacenter level for your cluster, you'll be able to double click on the "Data", and "Data2" entries, then remove ProxmoxGT from their Nodes list.
Trouble is that it does not show there. Storage data 2 on this server - data 2, vmdisks shows "could not activate storage 'Data2', zfs error: cannot import 'Data2': no such pool available (500)"
Trouble is that it does not show there. Storage data 2 on this server - data 2, vmdisks shows "could not activate storage 'Data2', zfs error: cannot import 'Data2': no such pool available (500)"
As @justinclift explained, the storage pool you are concerned about "Data2" is present on one node only. However, it's not marked as such in the configuration. At the Datacenter level, as shown in the screenshot you need to edit the storage pool configuration and limit it to one node only.
You can also edit "/etc/pve/storage.cfg" and add "nodes [node_where_Data2_exists]" line to the pool configuration.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.