Cannot mount NFS export on proxmox 6

DemiNe0

Active Member
Oct 19, 2017
28
10
43
37
Hi Everyone,

I recently did a fresh reinstall of proxmox 6, and I'm no longer able to mount an NFS export. Before the reinstall, mounting the NFS share was not an issue. The only difference between the old install and this new one, was that the old install was upgraded to proxmox 6 from 5.4. I have two proxmox servers right now both on fresh installs of proxmox 6 showing the same problem.

- I've ensured that the time is synced between proxmox and the NAS hosting the NFS share.
- The NAS is also up to date on it's firmware.
- Have tried using the nas's DNS hostname as well as the IP.
- The Proxmox server is also resolvable by DNS.
- Have tried mounting NFS using version 3 as well.

- The NAS is a Buffalo Terastation TS1400D.

- I'm able to mount the NFS share from Windows using the Windows 10 NFS client.

When trying to mount from the webui, I get one of two errors:
Connection error 596: Connection timed out
or
Connection error - Timeout.


Code:
root@pve-01:~# rpcinfo -p 10.100.0.20
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp  42068  mountd
    100005    1   tcp  45485  mountd
    100005    2   udp  37659  mountd
    100005    2   tcp  36506  mountd
    100005    3   udp  57729  mountd
    100005    3   tcp  60770  mountd
    100024    1   udp  33748  status
    100024    1   tcp  54204  status
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049
    100227    3   tcp   2049
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049
    100227    3   udp   2049
    100021    1   udp  46504  nlockmgr
    100021    3   udp  46504  nlockmgr
    100021    4   udp  46504  nlockmgr
    100021    1   tcp  32915  nlockmgr
    100021    3   tcp  32915  nlockmgr
    100021    4   tcp  32915  nlockmgr

Code:
root@pve-01:~# pvesm nfsscan 10.100.0.20
/mnt/array1/Data    0.0.0.0/0.0.0.0
/mnt/array1/Media   0.0.0.0/0.0.0.0
/mnt/array1/Backups 0.0.0.0/0.0.0.0
/mnt/array1/PVE     10.100.3.208,10.100.0.201,10.100.0.200

Code:
root@pve-01:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether e0:3f:49:e8:8a:ef brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e0:3f:49:e8:8a:ef brd ff:ff:ff:ff:ff:ff
    inet 10.100.0.200/22 brd 10.100.3.255 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::e23f:49ff:fee8:8aef/64 scope link
       valid_lft forever preferred_lft forever

Code:
root@pve-01:~# iptables --list
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

root@pve-01:~# pve-firewall status
Status: disabled/stopped

I've also tried mounting from the command line with the following commands, all of which indefinitely hang:
mount 10.100.0.20:/mnt/array1/PVE /mnt/temp
mount -t nfs 10.100.0.20:/mnt/array1/PVE /mnt/temp
mount.nfs 10.100.0.20:/mnt/array1/PVE /mnt/temp
mount.nfs -o vers=3 10.100.0.20:/mnt/array1/PVE /mnt/temp

Also have tried going CIFS to the nas, which also fails with:
create storage failed: error with cfs lock 'file-storage_cfg': mount error: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) (500)


I'm pretty much at my wits end here. I'm gonna try reinstalling to 5.4 to see if I get the same issue. Any thoughts?
 
Last edited:
Just an update on this. Downgraded to 5.4, and this issue does not exist on 5.4. NFS mounts with no issues what so ever.
 
I don't see anything wrong with the ports, ips, or mount command.

Enable nfs debugging:
rpcdebug -m nfs -s all

Go to PVE and watch Syslog

attempt mounting nfs share

Disable nfs debugging:
rpcdebug -m nfs -c
 
I'm fairly sure this is an issue specific to the state of proxmox 6 on a fresh install.

As I stated in my last edit, a fresh install of proxmox 5.4 doesn't present this issue.

I further tested this. I added an NFS mount while at 5.4, then upgraded that in place to proxmox 6. The existing NFS mount worked fine. I was also able to add another NFS mount without issue.

I don't see anything wrong with the ports, ips, or mount command.

Enable nfs debugging:
rpcdebug -m nfs -s all

Go to PVE and watch Syslog

attempt mounting nfs share

Disable nfs debugging:
rpcdebug -m nfs -c

Once I have these machines setup and the VM's restored, I'll create a proxmox vm and see if I can recreate the issue and run these diagnostics.
 
Last edited:
I do have zero issues with my NFS servers, running latest 6.x release.

So there must be something different on your side.
 
Well, it looks like its not just me, multiple people here on the forum are reporting exactly the same issue. I have not found an answer as of what may be causing it.
 
Permission configuration can be tricky, also especially cheap NAS boxes are not known for super stable NFS.

But with the help in this thread you should be able to debug it. Which NFS version do you run on the NFS server?
 
Tom, i'm not sure, i'm running Rockstor, but it works flawlessly and fast with 5.2 and 5.4 versions. It's not just NFS, CIFS is also exhibiting the same issue. CIFS is able to pull up the disk size but is unable to read contents. No firewalls, both on same subnet, yes it could be compatibility issue.
 
I personally do not use Rockstor but they offer support and I am pretty sure they can tell you how to connect a Linux client like Debian.
 
I do know how to connect it, it connects fine from cli, but not from gui.

Please provide error messages and logs, otherwise no one can give advice. And please tell which NFS server configuration in full detail.
 
The reason I installed v6 is because now it was possible to add drives and shares from gui. ive already spent two days trying to troubleshoot. Will wait until someone else finds a solution, i gave it a try already and I give up !!!!!
 
The reason I installed v6 is because now it was possible to add drives and shares from gui.

Please do and read what I asked for instead of posting every minute...
 
New error - Connection error 596: Connection timed out


Mar 17 15:38:09 pve pveproxy[1448]: worker 70613 finished
Mar 17 15:38:09 pve pveproxy[1448]: starting 1 worker(s)
Mar 17 15:38:09 pve pveproxy[1448]: worker 80318 started
Mar 17 15:39:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:39:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:39:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:40:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:40:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:40:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:41:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:41:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:41:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:42:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:42:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:42:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:43:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:43:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:43:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:44:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:44:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:44:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:44:59 pve pvedaemon[43620]: <root@pam> successful auth for user 'root@pam'
Mar 17 15:45:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:45:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:45:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:46:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:46:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:46:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:47:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:47:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:47:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:48:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:48:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:48:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:48:39 pve pveproxy[80107]: worker exit
Mar 17 15:48:39 pve pveproxy[1448]: worker 80107 finished
Mar 17 15:48:39 pve pveproxy[1448]: starting 1 worker(s)
Mar 17 15:48:39 pve pveproxy[1448]: worker 81824 started
Mar 17 15:48:41 pve pvedaemon[40505]: <root@pam> successful auth for user 'lgiunta@AD.NAWSNY.COM'
Mar 17 15:49:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:49:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:49:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:50:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:50:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:50:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:50:21 pve pvedaemon[43620]: <root@pam> successful auth for user 'lgiunta@AD.NAWSNY.COM'
Mar 17 15:50:38 pve pvedaemon[40505]: <root@pam> successful auth for user 'root@pam'
Mar 17 15:51:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:51:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:51:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:52:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:52:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:52:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:53:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:53:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:53:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:54:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:54:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:54:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:55:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:55:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:55:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:56:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:56:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:56:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:57:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:57:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:57:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:58:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:58:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:58:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 15:58:53 pve pveproxy[76895]: worker exit
Mar 17 15:58:53 pve pveproxy[1448]: worker 76895 finished
Mar 17 15:58:53 pve pveproxy[1448]: starting 1 worker(s)
Mar 17 15:58:53 pve pveproxy[1448]: worker 83283 started
Mar 17 15:59:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 15:59:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 15:59:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 16:00:00 pve pvedaemon[35524]: <root@pam> successful auth for user 'root@pam'
Mar 17 16:00:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 16:00:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 16:00:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 16:01:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 16:01:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 16:01:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 16:02:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 16:02:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 16:02:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 16:02:03 pve kernel: CIFS: Attempting to mount //192.168.111.55/vm_backups
Mar 17 16:02:03 pve kernel: CIFS VFS: cifs_mount failed w/return code = -2
Mar 17 16:02:22 pve pveproxy[1448]: worker 81824 finished
Mar 17 16:02:22 pve pveproxy[1448]: starting 1 worker(s)
Mar 17 16:02:22 pve pveproxy[1448]: worker 83800 started
Mar 17 16:02:23 pve pveproxy[83799]: worker exit
Mar 17 16:03:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 16:03:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 16:03:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 16:03:10 pve pveproxy[80318]: worker exit
Mar 17 16:03:10 pve pveproxy[1448]: worker 80318 finished
Mar 17 16:03:10 pve pveproxy[1448]: starting 1 worker(s)
Mar 17 16:03:10 pve pveproxy[1448]: worker 83925 started
Mar 17 16:03:42 pve pvedaemon[40505]: <root@pam> successful auth for user 'lgiunta@AD.NAWSNY.COM'
Mar 17 16:04:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 16:04:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 16:04:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 16:05:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 16:05:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 16:05:01 pve systemd[1]: Started Proxmox VE replication runner.
Mar 17 16:05:22 pve pvedaemon[40505]: <root@pam> successful auth for user 'lgiunta@AD.NAWSNY.COM'
Mar 17 16:05:39 pve pvedaemon[40505]: <root@pam> successful auth for user 'root@pam'
Mar 17 16:06:00 pve systemd[1]: Starting Proxmox VE replication runner...
Mar 17 16:06:01 pve systemd[1]: pvesr.service: Succeeded.
Mar 17 16:06:01 pve systemd[1]: Started Proxmox VE replication runner.

Logs

I tried with CIFS as well as NFS to no avail.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!