[SOLVED] Storage is missing from the dropdown menu in WebUI, unless I access it from the node \ storage tab

Wukong

New Member
Nov 24, 2025
3
1
3
Hello,

I have a strange issue with one of the storages. I have the storage shared on only one node:

From /etc/pve/storage.cfg

Code:
dir: storage
    path /storage
    content iso,images,vztmpl
    nodes node
    prune-backups keep-all=1
    shared 0

The storage is mounted and accesibile and I can even create VMs on it, but only if I click CreateVM while on the node tab or on the storage tab.

Code:
root@node:~# pvesm status
Name                Type     Status           Total            Used       Available        %
storage             dir     active     19325261824      3029699088     16295562736   15.68%
root@node:~# ls -ld /storage/
drwxr-xr-x 4 root root 36 Aug 21 11:33 /storage/
root@node:~# df -h | grep storage
/dev/mapper/vgdata-lvdata   18T  2.9T   16T  16% /storage

I have checked even with an account that has Administrator Role on \ (to establish that it's not a permission issue).

The thing is I am using different pools for different users and I want them to be able to have the storage option when trying to create a VM from one of the pools. The storage does not appear regardless if it's added as a member of those pools.


Is there anything else I can check?

Thank you
 
Is this a single node or a cluster?


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
This is a two-node cluster, each with its own separate storage. With the admin account if I click on Create VM anywhere, I only get the storage from one node, but not the other. The second storage I can only get it in the WebUI, only if I start it from the correct node \ or from the storage.
 
The second storage I can only get it in the WebUI, only if I start it from the correct node \ or from the storage.
Have you selected the correct node in the General tab? I.e. the second node if you want to place the VM on the second storage.

Local storages are only visible on the node they actually reside on, naturally.
 
Have you selected the correct node in the General tab? I.e. the second node if you want to place the VM on the second storage.

Local storages are only visible on the node they actually reside on, naturally.
Omg, I can't believe this was it. That makes perfect sense. Sorry for the silly post!

Because I started troubleshooting this from an account with NoAccess to the other hypervisor, I assumed it was defaulting on the correct one even though the other one was showing in the column. I know that this is a feature that may be implemented in future versions. Thank you once again!
 
  • Like
Reactions: cheiss