Proxmox VE 9.1.1 - SMB/CIFS storage subdirectory field permanently greyed out

[Wayno58]

I'm adding a new SMB/CIFS storage pointing to a Synology NAS. The storage creates successfully, but the Subdirectory field is greyed out both during creation and when editing the storage afterwards.


My goal is to store vzdump backups in a subfolder (Home-Assistant/VM) rather than the root of the SMB share.


Is this expected behaviour in PVE 9.1.1, or is there a way to enable the field? If not, is editing storage.cfg with a subdir option the recommended approach?

 

[news]

check your rights on that samba share.

 

[anna_pve_berlin]

If the field is already greyed out before the storage is saved, I would not start by hand-editing storage.cfg. First verify whether the chosen user can actually list and create that exact folder on the share, then try adding the storage from the normal PVE Datacenter → Storage view, not only through PDM. For a quick workaround, a separate Synology share that points directly at Home-Assistant/VM is usually cleaner than relying on a hidden/unsupported subdir option; after any manual change, check it with pvesm status before scheduling backups.

 

[Wayno58]

check your rights on that samba share.

Thanks, I had missed the read/write on the share. It hasn't resolved the problem but it has saved me hassle down the line

 

[fiona]

Hi,
what does "greyed out" look like? It's expected that the field cannot be edited after creation anymore, but it should work for creation and it does for me with the current 9.2 version.

 

[Wayno58]

Hi,
what does "greyed out" look like? It's expected that the field cannot be edited after creation anymore, but it should work for creation and it does for me with the current 9.2 version.

Thanks. I'm running PVE 9.1.1.


The Subdirectory field is already disabled when creating a new SMB/CIFS storage from Datacenter → Storage → Add → SMB/CIFS. It's not something that becomes disabled after saving—the field is unavailable from the start out from the start, so I can't enter a value. Does this look like expected behaviour for 9.1.1, or was this changed in 9.2?

 

[Wayno58]

Thanks. I'm running PVE 9.1.1.


The Subdirectory field is already disabled when creating a new SMB/CIFS storage from Datacenter → Storage → Add → SMB/CIFS. It's not something that becomes disabled after saving—the field is unavailable from the start out from the start, so I can't enter a value. Does this look like expected behaviour for 9.1.1, or was this changed in 9.2?

Thanks. I'm running PVE 9.1.1.


The Subdirectory field is already disabled when creating a new SMB/CIFS storage from Datacenter → Storage → Add → SMB/CIFS. It's not something that becomes disabled after saving—the field is unavailable from the start out from the start, so I can't enter a value. Does this look like expected behaviour for 9.1.1, or was this changed.

The issue is resolved. I recreated the SMB storage from scratch, and this time the Subdirectory field was available during creation. After configuring it, the backup went directly into the intended folder. Thanks for pointing me in the right direction.