CIFS share refuses to connect.

[sovietbear]

Proxmox keeps giving me the following when I try to connect to a CIFS share running off of a virtualized FreeNAS box:

create storage failed: error with cfs lock 'file-storage_cfg': storage 'Proxmox' is not online (500)

This share works fine on multiple computers, and running

smbclient -m smb3 -d 0 -L [IP] -N

returns this:

Anonymous login successful

        Sharename       Type      Comment
        ---------       ----      -------
        Private         Disk     
        Proxmox         Disk     
        Public          Disk     
        Warez           Disk     
        IPC$            IPC       IPC Service (FreeNAS Server)
Reconnecting with SMB1 for workgroup listing.
Anonymous login successful

        Server               Comment
        ---------            -------

        Workgroup            Master
        ---------            -------
        AD                   VIRT-NFS0

Furthermore, in the web UI when I set up the share, Proxmox successfully scans and lists the shares.

Any ideas?

 

[t.lamprecht]

Any ideas?

Which Proxmox VE version do you use: pveversion -v

 

[sovietbear]

Which Proxmox VE version do you use: pveversion -v

For some reason my other computers are having intermittent issues connecting to the server,
I'm going to re-image the FreeNAS VM and restore from back up.

Though since you asked, the out put is:

root@ravenholm:~# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.10-1-pve)
pve-manager: 6.1-3 (running version: 6.1-3/37248ce6)
pve-kernel-5.3: 6.0-12
pve-kernel-helper: 6.0-12
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.2-pve4
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 1.2.5-1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.13-pve1
libpve-access-control: 6.0-5
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-9
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-3
libpve-storage-perl: 6.1-2
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve3
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 6.1-2
pve-container: 3.0-14
pve-docs: 6.1-3
pve-edk2-firmware: 2.20191002-1
pve-firewall: 4.0-9
pve-firmware: 3.0-4
pve-ha-manager: 3.0-8
pve-i18n: 2.0-3
pve-qemu-kvm: 4.1.1-2
pve-xtermjs: 3.13.2-1
qemu-server: 6.1-2
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.2-pve2

 

[sovietbear]

Which Proxmox VE version do you use: pveversion -v

Looks like the issue is still occurring, despite the fact that I can hit the smb share from my Win 10 machine.

Edit: And it just magically worked. I'll go sacrifice a lamb to make sure it keeps at it.

 

[sinopsis]

I am having this exact same issue...same symptoms, but I haven't been lucky enough to have it just start working again....It was working just fine for a couple of months but stopped working last Friday night

root@pve:/etc/pve# pveversion -v
proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve)
pve-manager: 6.1-11 (running version: 6.1-11/f2f18736)
pve-kernel-helper: 6.1-9
pve-kernel-5.3: 6.1-6
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.2
libpve-access-control: 6.0-7
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-6
pve-cluster: 6.1-8
pve-container: 3.1-4
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.0-7
pve-ha-manager: 3.0-9
pve-i18n: 2.1-1
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-20
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

 

[sinopsis]

I was able to resolve this my deleting the storage and recreating it, only this time, I didn't use myuser@mydomain and a blank domain, I specified just "myuser" and then mydomain in the domain box...not sure why it initially worked and then stopped working, but I don't care, now that it is working