Unable to backup or view CIFS storage - "Unable to activate storage..."

V

victorhooi

Well-Known Member
Apr 3, 2018
255
20
58
38
I am running Proxmox 6.2 I have added a CIFS storage server to the Proxmox config.

The NAS is running FreeNAS, and exporting the ZFS datastore via SMB (CIFS).

The server is listed in /etc/pve/storage.cfg:
Code: 
cifs: proxmox_backups
    path /mnt/pve/proxmox_backups
    #server 10.7.17.95
    server 10.7.78.35
    share proxmox-backups
    content images,backup
    maxfiles 5
    username example
If I do a "mount", I do see the share listed there:
Code: 
//10.7.78.35/proxmox-backups on /mnt/pve/proxmox_backups type cifs (rw,relatime,vers=3.0,cache=strict,username=example,uid=0,noforceuid,gid=0,noforcegid,addr=10.7.78.35,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1)
However, when I try to view the storage contents via the Web UI, I get the error:
Code: 
unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable (500)

And when I try to backup to that storage as well, I get:
Code: 
TASK ERROR: could not get storage information for 'proxmox_backups': unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable
Any ideas what's going on?

Thanks,
Victor
 
I just saw this earlier thread (https://forum.proxmox.com/threads/unable-to-activate-cifs-for-pve-storage.70060/), and thought I'd paste some of the diagnostic commands mentioned there in case it helps with my issue.

Here is the output from journalctl -xe:
Code: 
-- The job identifier is 2637.
May 25 04:25:01 exampleserver1 pvestatd[1915]: got timeout
May 25 04:25:01 exampleserver1 kernel: CIFS VFS: \\10.7.78.35 Cancelling wait for mid 96 cmd: 5
May 25 04:25:01 exampleserver1 kernel: CIFS VFS: \\10.7.78.35 Cancelling wait for mid 97 cmd: 16
May 25 04:25:01 exampleserver1 pvestatd[1915]: unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable
May 25 04:25:10 exampleserver1 pvestatd[1915]: got timeout
May 25 04:25:10 exampleserver1 kernel: CIFS VFS: \\10.7.78.35 Cancelling wait for mid 98 cmd: 5
May 25 04:25:10 exampleserver1 kernel: CIFS VFS: \\10.7.78.35 Cancelling wait for mid 99 cmd: 16
May 25 04:25:10 exampleserver1 pvestatd[1915]: unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable
May 25 04:25:20 exampleserver1 pvestatd[1915]: got timeout
May 25 04:25:20 exampleserver1 kernel: CIFS VFS: \\10.7.78.35 Cancelling wait for mid 100 cmd: 5
May 25 04:25:20 exampleserver1 kernel: CIFS VFS: \\10.7.78.35 Cancelling wait for mid 101 cmd: 16
May 25 04:25:20 exampleserver1 pvestatd[1915]: unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable
May 25 04:25:24 exampleserver1 kernel: CIFS VFS: \\10.7.78.35 has not responded in 180 seconds. Reconnecting...
May 25 04:25:28 exampleserver1 systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit systemd-tmpfiles-clean.service has begun execution.
--
-- The job identifier is 2709.
May 25 04:25:28 exampleserver1 systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit systemd-tmpfiles-clean.service has successfully entered the 'dead' state.
May 25 04:25:28 exampleserver1 systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: A start job for unit systemd-tmpfiles-clean.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit systemd-tmpfiles-clean.service has finished successfully.
--
-- The job identifier is 2709.
May 25 04:25:34 exampleserver1 sshd[9638]: Accepted password for root from 10.7.78.109 port 61843 ssh2
May 25 04:25:34 exampleserver1 sshd[9638]: pam_unix(sshd:session): session opened for user root by (uid=0)
May 25 04:25:34 exampleserver1 systemd-logind[1185]: New session 4 of user root.
-- Subject: A new session 4 has been created for user root
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat
--
-- A new session with the ID 4 has been created for the user root.
--
-- The leading process of the session is 9638.
May 25 04:25:34 exampleserver1 systemd[1]: Started Session 4 of user root.
-- Subject: A start job for unit session-4.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-4.scope has finished successfully.
--
-- The job identifier is 2713.
Likewise, if I look in /var/log/syslog:
Code: 
May 25 04:27:40 exampleserver1 pvestatd[1915]: got timeout
May 25 04:27:40 exampleserver1 kernel: [ 1034.905133] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 98 cmd: 5
May 25 04:27:40 exampleserver1 kernel: [ 1034.905323] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 99 cmd: 16
May 25 04:27:40 exampleserver1 pvestatd[1915]: unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable
May 25 04:27:51 exampleserver1 pvestatd[1915]: got timeout
May 25 04:27:51 exampleserver1 kernel: [ 1045.467861] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 102 cmd: 5
May 25 04:27:51 exampleserver1 kernel: [ 1045.468067] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 103 cmd: 16
May 25 04:27:51 exampleserver1 pvestatd[1915]: unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable
May 25 04:28:00 exampleserver1 systemd[1]: Starting Proxmox VE replication runner...
May 25 04:28:00 exampleserver1 pvestatd[1915]: got timeout
May 25 04:28:00 exampleserver1 kernel: [ 1054.804497] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 104 cmd: 5
May 25 04:28:00 exampleserver1 kernel: [ 1054.804696] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 105 cmd: 16
May 25 04:28:00 exampleserver1 pvestatd[1915]: unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable
May 25 04:28:01 exampleserver1 systemd[1]: pvesr.service: Succeeded.
May 25 04:28:01 exampleserver1 systemd[1]: Started Proxmox VE replication runner.
May 25 04:28:11 exampleserver1 pvestatd[1915]: got timeout
May 25 04:28:11 exampleserver1 kernel: [ 1065.210406] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 106 cmd: 5
May 25 04:28:11 exampleserver1 kernel: [ 1065.210617] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 107 cmd: 16
May 25 04:28:11 exampleserver1 pvestatd[1915]: unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable
May 25 04:28:20 exampleserver1 pvestatd[1915]: got timeout
May 25 04:28:20 exampleserver1 kernel: [ 1074.646888] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 108 cmd: 5
May 25 04:28:20 exampleserver1 kernel: [ 1074.647086] CIFS VFS: \\10.7.78.35 Cancelling wait for mid 109 cmd: 16
May 25 04:28:20 exampleserver1 pvestatd[1915]: unable to activate storage 'proxmox_backups' - directory '/mnt/pve/proxmox_backups' does not exist or is unreachable

I also ran the following command - it return no output
Code: 
# pvesm scan cifs 10.7.78.35
#
 
You must log in or register to reply here.
Top Bottom