storage SMB is not online (500)

[Torpion]

Hello everyone,

I've just installed a new server under Proxmox 8.0.3, but I'm encountering problems when adding an SMB disk. An error message appears: "Create storage failed: storage 'NAS' is not online (500)" :



However, I can access the shared folder of the concerned NAS :



After several searches on this forum, I've noticed that some have found a solution by not immediately checking the "Enable" box. When I do this and then go to check the "Enable" box, it works and the connection to my NAS is successful :



However, the storage remains inactive and I cannot access it.

Could you please offer me a solution?

Thank you in advance.

 

[Chris]

Hello everyone,

I've just installed a new server under Proxmox 8.0.3, but I'm encountering problems when adding an SMB disk. An error message appears: "Create storage failed: storage 'NAS' is not online (500)" :

View attachment 53825

However, I can access the shared folder of the concerned NAS :

View attachment 53822

After several searches on this forum, I've noticed that some have found a solution by not immediately checking the "Enable" box. When I do this and then go to check the "Enable" box, it works and the connection to my NAS is successful :

View attachment 53828

However, the storage remains inactive and I cannot access it.

Could you please offer me a solution?

Thank you in advance.

Hi,
what PVE version are you running? Please share the output of pveversion -v. Seems like the mounting of the storage does not work, please check the journal for errors/hints.

 

[Torpion]

Hi,
what PVE version are you running? Please share the output of pveversion -v. Seems like the mounting of the storage does not work, please check the journal for errors/hints.

Thank you for your response.

Here is the version:

# pveversion -v
proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)
pve-kernel-6.2: 8.0.2
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.0
libpve-access-control: 8.0.3
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.5
libpve-guest-common-perl: 5.0.3
libpve-http-server-perl: 5.0.3
libpve-rs-perl: 0.8.3
libpve-storage-perl: 8.0.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 2.99.0-1
proxmox-backup-file-restore: 2.99.0-1
proxmox-kernel-helper: 8.0.2
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.5
pve-cluster: 8.0.1
pve-container: 5.0.3
pve-docs: 8.0.3
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.2
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.4
pve-qemu-kvm: 8.0.2-3
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1

Are you talking about the Proxmox logs or the NAS ones?
If it's the Proxmox logs, in which log file should I look?

Thank you for your help,

Anthony

 

[Chris]

Thank you for your response.

Here is the version:

# pveversion -v
proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve)
pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916)
pve-kernel-6.2: 8.0.2
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.0
libpve-access-control: 8.0.3
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.5
libpve-guest-common-perl: 5.0.3
libpve-http-server-perl: 5.0.3
libpve-rs-perl: 0.8.3
libpve-storage-perl: 8.0.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 2.99.0-1
proxmox-backup-file-restore: 2.99.0-1
proxmox-kernel-helper: 8.0.2
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.0.5
pve-cluster: 8.0.1
pve-container: 5.0.3
pve-docs: 8.0.3
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.2
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.4
pve-qemu-kvm: 8.0.2-3
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1

Are you talking about the Proxmox logs or the NAS ones?
If it's the Proxmox logs, in which log file should I look?

Thank you for your help,

Anthony

I am referring to the PVE host log files, but you might want to check the logs on the NAS as well. journalctl -b -r will give you a paged view of the journal since boot in reverse. Did you verify that the user and password are correct?

Also, the log message you showed above is with respect to the home share and not the NAS share. So does the user actually have access to this share?

 

[Torpion]

I am referring to the PVE host log files, but you might want to check the logs on the NAS as well. journalctl -b -r will give you a paged view of the journal since boot in reverse. Did you verify that the user and password are correct?

Also, the log message you showed above is with respect to the home share and not the NAS share. So does the user actually have access to this share?

In the logs, I see nothing related to SMB.

Regarding the shared access, the user does have access to the relevant folder.

To test, I connected my SMB share with the same username and password to a Windows virtual machine. Everything was fine, I don't understand where the problem could come from.

 

[nio]

j'ai le meme probleme avec un nas synology

 

[Torpion]

j'ai le meme probleme avec un nas synology

J'ai changé de protocole, j'ai monté un volume en NFS directement en ligne de commande puis dans l'interface proxmox.
ça fonctionne maintenant