CIFS: storage is not online (500)

emberzhang · Nov 11, 2021

same negotiation problem with macOS server too. from bigsur to montery, from pve 5.x to 7.0

check from another macbook shows the server smb version is 3.0:

--------------------------------------------------------------------------------------------------
➜ ~ smbutil statshares -a

==================================================================================================
SHARE ATTRIBUTE TYPE VALUE
==================================================================================================
Archive
SERVER_NAME 172.16.1.100
USER_ID 501
SMB_NEGOTIATE SMBV_NEG_SMB1_ENABLED
SMB_NEGOTIATE SMBV_NEG_SMB2_ENABLED
SMB_NEGOTIATE SMBV_NEG_SMB3_ENABLED
SMB_VERSION SMB_3.0.2
SMB_ENCRYPT_ALGORITHMS AES_128_CCM_ENABLED
SMB_ENCRYPT_ALGORITHMS AES_128_GCM_ENABLED
SMB_ENCRYPT_ALGORITHMS AES_256_CCM_ENABLED
SMB_ENCRYPT_ALGORITHMS AES_256_GCM_ENABLED
SMB_CURR_ENCRYPT_ALGORITHM OFF
SMB_SHARE_TYPE DISK
SIGNING_SUPPORTED TRUE
SIGNING_REQUIRED TRUE
EXTENDED_SECURITY_SUPPORTED TRUE
UNIX_SUPPORT TRUE
LARGE_FILE_SUPPORTED TRUE
OS_X_SERVER TRUE
FILE_IDS_SUPPORTED TRUE
FILE_LEASING_SUPPORTED TRUE
MULTI_CREDIT_SUPPORTED TRUE
DIR_LEASING_SUPPORTED TRUE
ENCRYPTION_SUPPORTED TRUE
SIGNING_ON TRUE
==================================================================================================

and the on pve :
--------------------------------------------------------------------------------------------------
root@pve:~# pvesm add cifs mac --server 172.16.1.100 --share proxmox --username ember --password <password> --domain WORKGROUP --smbversion 3.0
create storage failed: storage 'mac' is not online

--------------------------------------------------------------------------------------------------

no help with changing or deleting the "--domain" part

fiona · Nov 11, 2021

Hi,

emberzhang said:
--------------------------------------------------------------------------------------------------
root@pve:~# pvesm add cifs mac --server 172.16.1.100 --share proxmox --username ember --password <password> --domain WORKGROUP --smbversion 3.0
create storage failed: storage 'mac' is not online

--------------------------------------------------------------------------------------------------

no help with changing or deleting the "--domain" part

does it work if you don't specify --smbversion at all? What do you get with

Code:

time smbclient //<host>/<share> -d 0 -U <user>%<password> -c 'echo 1 0'
time smbclient //<host>/<share> -d 0 -U <user>%<password> -W WORKGROUP -c 'echo 1 0'

Please also share the output of pveversion -v.

emberzhang · Nov 11, 2021

Fabian_E said:
Hi,

does it work if you don't specify --smbversion at all? What do you get with

Code:

time smbclient //<host>/<share> -d 0 -U <user>%<password> -c 'echo 1 0' time smbclient //<host>/<share> -d 0 -U <user>%<password> -W WORKGROUP -c 'echo 1 0'

Please also share the output of pveversion -v.

removed --smbversion
--------------------------------------------------------------------------------------------------
root@pve:~# pvesm add cifs mac --server 172.16.1.100 --share proxmox --username ember --password <password> --domain WORKGROUP
create storage failed: storage 'mac' is not online
root@pve:~# pvesm add cifs mac --server 172.16.1.100 --share proxmox --username ember --password <password>
create storage failed: storage 'mac' is not online
========================================================
time smbclient: to a macOS server
--------------------------------------------------------------------------------------------------
root@pve:~# time smbclient //172.16.1.100/proxmox -d 0 -U ember%password -c 'echo 1 0'
echo failed: NT_STATUS_CONNECTION_DISCONNECTED

real 0m0.293s
user 0m0.034s
sys 0m0.029s

root@pve:~# time smbclient //172.16.1.100/proxmox -d 0 -U ember%password -W WORKGROUP -c 'echo 1 0'
echo failed: NT_STATUS_CONNECTION_DISCONNECTED

real 0m0.101s
user 0m0.029s
sys 0m0.009s

========================================================
time smbclient: to a linux server (no problem)
--------------------------------------------------------------------------------------------------
root@pve:~# time smbclient //172.16.1.200/m2 -d 0 -U ember%password -c 'echo 1 0'

real 0m0.059s
user 0m0.028s
sys 0m0.012s

root@pve:~# time smbclient //172.16.1.200/m2 -d 0 -U ember%password -W WORKGROUP -c 'echo 1 0'

real 0m0.054s
user 0m0.030s
sys 0m0.009s
========================================================
pveversion -v
--------------------------------------------------------------------------------------------------
root@pve:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-3-pve)
pve-manager: 7.0-14+1 (running version: 7.0-14+1/08975a4c)
pve-kernel-helper: 7.1-4
pve-kernel-5.11: 7.0-10
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.11.22-3-pve: 5.11.22-7
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-12
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-13
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.13-1
proxmox-backup-file-restore: 2.0.13-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20210831-1
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.1.0-1
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-18
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
========================================================

vesalius · Nov 27, 2021

Same issue as @emberzhang working from Proxmox 7.1 to macOS Monterey.

kalasnikov · Feb 1, 2022

Did you ever find the fix?

mounty1997 · Feb 14, 2022

I'm having exactly the same issue. Changing timeout from 10 to 40 didn't work either :/

johnny5w · Mar 25, 2022

Anyone find a fix for this? Trying to add SMB/CIFS storage from a macOS Catalina share to Proxmox 7.1-11 and am having the exact issue as the above responses.

windycity · Apr 4, 2022

Same issue as @emberzhang and @johnny5w. Did anyone find a solution to this?

lx07 · May 1, 2022

Looking for a fix of this plz

breakaway9000 · May 9, 2022

I just hit this very same issue. I was trying to connect a SMB share from my Synolgy to my Proxmox. Unfortunately, it didn't work and I had no choice but to give up. I'm now using NFS.

Pandiora · May 28, 2022

I had problems with PVE 7.2 too, but in the end it was my own fault. I was searching for a way to add the HDD, which I passed through to OMV, to Proxmox and then use it for my LXC containers. thushanfernando (Blog) mentioned this command to add a SMB share:

Code:

pvesm add cifs neo-backups --server 192.168.0.12 --share incoming [--username x] [--password y] [--path /mnt/neo-backups]

Turned out the mistake was on my side, since I ignored the --share-Argument. I believe this is not a problem with Proxmox.

nazgul · Oct 9, 2022

Hi, has anyone been able to solve this? I too am trying to share a SMB3 share from macOS Catalina to Proxmox 7.2-11 and seeing the same issue.

EDIT: found a work around for this by mounting the SMB directly into the LXC I wanted the SMB to have been passed through:
https://chrisatech.wordpress.com/20...tion-and-adding-an-smb-server-to-the-library/

blabbermouth · Jun 23, 2023

Just ran into this error in Proxmox 8.0.3.
Wouldn't let me add a Samba share.
Workaround: Input everything but deselect the Enable box.
The storage than saves.
Then edit it and enable it an it works...

drookash · Jun 23, 2023

Thanks for solution. It works.

ragsna · Jun 24, 2023

Thanks very much! I ran into the same issue with Proxmox 8.0.3.
First workaround was to enable "guest access" on the share. This worked, too.

fiona · Jun 27, 2023

Hi,

blabbermouth said:
Just ran into this error in Proxmox 8.0.3.
Wouldn't let me add a Samba share.
Workaround: Input everything but deselect the Enable box.
The storage than saves.
Then edit it and enable it an it works...

thank you for the report! There was an issue with the connection check. It'll be fixed in future versions of the storage package, i.e. libpve-storage-perl >= 8.0.2: https://git.proxmox.com/?p=pve-storage.git;a=commit;h=b27da68320ba004e9a0f490707b86ef01af2c669

Adnan · Jul 3, 2023

Hi Fiona,

fiona said:
thank you for the report! There was an issue with the connection check. It'll be fixed in future versions of the storage package, i.e. libpve-storage-perl >= 8.0.2: https://git.proxmox.com/?p=pve-storage.git;a=commit;h=b27da68320ba004e9a0f490707b86ef01af2c669

I ran into the same problem, and I'm up to date.

The 3 servers highlighted are the same but different shares. When I add them, the shares are seen (so the credentials are correct) and I still get the 500 error. If I add disabled and enable it afterward, even after a reboot they won't connect. Any idea?

fiona · Jul 3, 2023

Hi,

Adnan said:
I ran into the same problem, and I'm up to date.

It's not the same the problem

Since that one is fixed in the new version and that issue was only upon adding the storage, but yours is persistent afterwards.

Adnan said:
The 3 servers highlighted are the same but different shares. When I add them, the shares are seen (so the credentials are correct) and I still get the 500 error. If I add disabled and enable it afterward, even after a reboot they won't connect. Any idea?

What is the exact error message you get? Please check your system logs for more. Are you using an SMB protocol version your server understands? Can be set with pvesm set <storage ID> --smbversion <version> see man pvesm for details.

Adnan · Jul 3, 2023

fiona said:
It's not the same the problem Since that one is fixed in the new version and that issue was only upon adding the storage, but yours is persistent afterwards.

Oops

fiona said:
What is the exact error message you get? Please check your system logs for more. Are you using an SMB protocol version your server understands? Can be set with pvesm set <storage ID> --smbversion <version> see man pvesm for details.

The exact message is: create storage failed: storage 'backups' is not online (500) when I add a share.

I've made some tests, on Synology we have an LDAP server and the account is xxx@domain.ext, it allows the shares to be queried but it doesn't allow adding the share. I removed the domain part and set WORKGROUP in domain, it worked.

Thanks

fiona · Jul 3, 2023

Adnan said:
I've made some tests, on Synology we have an LDAP server and the account is xxx@domain.ext, it allows the shares to be queried but it doesn't allow adding the share. I removed the domain part and set WORKGROUP in domain, it worked.

Thanks for sharing the solution!

CIFS: storage is not online (500)

Member

Proxmox Staff Member

Member

Renowned Member

New Member

New Member

Member

Member

Member

Renowned Member

New Member

Member

Active Member

Member

Member

Proxmox Staff Member

Renowned Member

Attachments

Proxmox Staff Member

Renowned Member

Attachments

Proxmox Staff Member

We value your privacy