Mount no longer works in Proxmox 6 - NFS - Synology

CookieMonster said:
you mean rpcinfo from the NAS to the vm? no that works fine
Click to expand...
No quit, I meant to activate the firewall again and re-test. Just to verify that it wasn't coincident.
 
I had same behaviour. In mycase i have 2 active interfaces on synology, one working, second not (no route to host). Solution was to turn off ARP reply in Network settings on Synology:
  1. Under General, check Reply to ARP requests if the target IP address is a local address configured on the incoming interface.
 
Last edited:
eLxx said:
I had same behaviour. In mycase i have 2 active interfaces on synology, one working, second not (no route to host). Solution was to turn off ARP reply in Network settings on Synology:
  1. Under General, check Reply to ARP requests if the target IP address is a local address configured on the incoming interface.
Click to expand...

Just looked at the setting. It was already checked so its not gonna work.

Does this mean your Proxmox can connect over nfs to your Synology NAS?
 
eLxx said:
Point is to uncheck!
Click to expand...
Oke mis read :)

When disabled the NAS is not accessible on the NET-2 (totally nothing). So it's not a solution.

It also does not explain why only proxmox 6.0 has problems connecting and Proxmox 5.4 with the latest kernel (see whole discussion) has no problems what so ever.
Thanks for giving ideas anyway
 
Are you guys running on the latest DSM version (6.2.2)? There have been some NFS stability fixes, AFAICT from the release notes.
 
Is there NFS traffic coming/going from/to the NAS tcpdump host <IP> -vvv | tee tcpdump-nfs.log?

With the rpcdebug -m module -s you can enable the kernel nfs debug flags and get more output (dmesg/syslog). This should also be possible on the NFS server itself. If the DSM doesn't have a rpcdebug tool, then you can echo '65535' > /proc/sys/sunrpc/{rpc,nfs,nfsd,nlm}_debug.
 
NFS is still not working with Proxmox 6.0.7
Below some debugging info.

We do have DSM 6.2.2-24922 Update 3

rpcinfo from My laptop (MacBook)
$ uname -a
Darwin MacBook-Pro-van-Tezzt.local 18.7.0 Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64 x86_64

$ rpcinfo -p #.#.#.#
program vers proto port
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
100005 1 udp 892 mountd
100005 1 tcp 892 mountd
100005 2 udp 892 mountd
100005 2 tcp 892 mountd
100005 3 udp 892 mountd
100005 3 tcp 892 mountd
100021 1 udp 35528 nlockmgr
100021 3 udp 35528 nlockmgr
100021 4 udp 35528 nlockmgr
100021 1 tcp 38660 nlockmgr
100021 3 tcp 38660 nlockmgr
100021 4 tcp 38660 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100024 1 udp 39508 status
100024 1 tcp 47156 status

rpcinfo from proxmox host
$ uname -a
Linux matrix 5.0.21-2-pve #1 SMP PVE 5.0.21-6 (Fri, 27 Sep 2019 17:17:02 +0200) x86_64 GNU/Linux

$ rpcinfo -p #.#.#.#
^@#.#.#.# RPC: Remote system error - Connection timed out

rpcinfo from proxmox guest
$ uname -a
Linux node155 5.0.21-2-pve #1 SMP PVE 5.0.21-6 (Fri, 27 Sep 2019 17:17:02 +0200) x86_64 x86_64 x86_64 GNU/Linux

$ rpcinfo -p #.#.#.#
#.#.#.#: RPC: Port mapper failure - Unable to send: errno 1 (Operation not permitted)

$ pve-firewall status
Status: disabled/running

$ tcpdump host #.#.#.# -vvv | tee tcpdump-nfs.log
$ cat tcpdump-nfs.log |more
### This is the beginning of tcpdump from the proxmox host
09:49:31.250330 IP (tos 0x0, ttl 64, id 46181, offset 0, flags [DF], proto TCP (6), length 60)
my-domain.com.1004 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags , cksum 0x5d84 (incorrect -> 0x48d1), seq 3418959191, win 64240, options [mss 1460,sackOK,TS val 648315592 ecr 0,nop,wscale 7], length 0
09:49:31.258130 IP (tos 0x0, ttl 53, id 0, offset 0, flags [DF], proto TCP (6), length 60)
ip-111.222.333.444.ip.prioritytelecom.net.sunrpc > my-domain.com.1004: Flags [S.], cksum 0xc1a5 (correct), seq 4286478420, ack 3418959192, win 5792, options [mss 1380,sackOK,TS val 304341449 ecr 648315592,nop,wscale 2], length 0
09:49:31.258170 IP (tos 0x0, ttl 64, id 46182, offset 0, flags [DF], proto TCP (6), length 52)
my-domain.com.1004 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags [.], cksum 0x5d7c (incorrect -> 0x04bf), seq 1, ack 1, win 502, options [nop,nop,TS val 648315600 ecr 304341449], length 0
09:49:31.258293 IP (tos 0x0, ttl 64, id 46183, offset 0, flags [DF], proto TCP (6), length 148)
my-domain.com.1004 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags [P.], cksum 0x5ddc (incorrect -> 0x5b83), seq 1:97, ack 1, win 502, options [nop,nop,TS val 648315600 ecr 304341449], length 96
09:49:31.265980 IP (tos 0x0, ttl 53, id 44654, offset 0, flags [DF], proto TCP (6), length 52)
ip-111.222.333.444.ip.prioritytelecom.net.sunrpc > my-domain.com.1004: Flags [.], cksum 0x00ac (correct), seq 1, ack 97, win 1448, options [nop,nop,TS val 304341450 ecr 648315600], length 0
09:49:31.266616 IP (tos 0x0, ttl 53, id 44655, offset 0, flags [DF], proto TCP (6), length 104)
ip-111.222.333.444.ip.prioritytelecom.net.sunrpc > my-domain.com.1004: Flags [P.], cksum 0xbf04 (correct), seq 1:53, ack 97, win 1448, options [nop,nop,TS val 304341450 ecr 648315600], length 52
09:49:31.266636 IP (tos 0x0, ttl 64, id 46184, offset 0, flags [DF], proto TCP (6), length 52)
my-domain.com.1004 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags [.], cksum 0x5d7c (incorrect -> 0x0421), seq 97, ack 53, win 502, options [nop,nop,TS val 648315609 ecr 304341450], length 0
09:49:31.266675 IP (tos 0x0, ttl 64, id 46185, offset 0, flags [DF], proto TCP (6), length 52)
my-domain.com.1004 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags [F.], cksum 0x5d7c (incorrect -> 0x0420), seq 97, ack 53, win 502, options [nop,nop,TS val 648315609 ecr 304341450], length 0
09:49:31.274366 IP (tos 0x0, ttl 53, id 44656, offset 0, flags [DF], proto TCP (6), length 52)
ip-111.222.333.444.ip.prioritytelecom.net.sunrpc > my-domain.com.1004: Flags [F.], cksum 0x006d (correct), seq 53, ack 98, win 1448, options [nop,nop,TS val 304341450 ecr 648315609], length 0
09:49:31.274394 IP (tos 0x0, ttl 64, id 46186, offset 0, flags [DF], proto TCP (6), length 52)
my-domain.com.1004 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags [.], cksum 0x5d7c (incorrect -> 0x0418), seq 98, ack 54, win 502, options [nop,nop,TS val 648315616 ecr 304341450], length 0
09:49:40.645336 IP (tos 0x0, ttl 64, id 54634, offset 0, flags [DF], proto TCP (6), length 60)
my-domain.com.661 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags , cksum 0x5d84 (incorrect -> 0x5db6), seq 1235908405, win 64240, options [mss 1460,sackOK,TS val 648324987 ecr 0,nop,wscale 7], length 0
09:49:40.653091 IP (tos 0x0, ttl 53, id 0, offset 0, flags [DF], proto TCP (6), length 60)
ip-111.222.333.444.ip.prioritytelecom.net.sunrpc > my-domain.com.661: Flags [S.], cksum 0x74b6 (correct), seq 3344174760, ack 1235908406, win 5792, options [mss 1380,sackOK,TS val 304342388 ecr 648324987,nop,wscale 2], length 0
09:49:40.653132 IP (tos 0x0, ttl 64, id 54635, offset 0, flags [DF], proto TCP (6), length 52)
my-domain.com.661 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags [.], cksum 0x5d7c (incorrect -> 0xb7cf), seq 1, ack 1, win 502, options [nop,nop,TS val 648324995 ecr 304342388], length 0
09:49:40.653254 IP (tos 0x0, ttl 64, id 54636, offset 0, flags [DF], proto TCP (6), length 148)
my-domain.com.661 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags [P.], cksum 0x5ddc (incorrect -> 0x224f), seq 1:97, ack 1, win 502, options [nop,nop,TS val 648324995 ecr 304342388], length 96
09:49:40.660877 IP (tos 0x0, ttl 53, id 46382, offset 0, flags [DF], proto TCP (6), length 52)
ip-111.222.333.444.ip.prioritytelecom.net.sunrpc > my-domain.com.661: Flags [.], cksum 0xb3bc (correct), seq 1, ack 97, win 1448, options [nop,nop,TS val 304342389 ecr 648324995], length 0
09:49:40.661361 IP (tos 0x0, ttl 53, id 46383, offset 0, flags [DF], proto TCP (6), length 104)
ip-111.222.333.444.ip.prioritytelecom.net.sunrpc > my-domain.com.661: Flags [P.], cksum 0x85d0 (correct), seq 1:53, ack 97, win 1448, options [nop,nop,TS val 304342389 ecr 648324995], length 52
09:49:40.661392 IP (tos 0x0, ttl 64, id 54637, offset 0, flags [DF], proto TCP (6), length 52)
my-domain.com.661 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags [.], cksum 0x5d7c (incorrect -> 0xb732), seq 97, ack 53, win 502, options [nop,nop,TS val 648325003 ecr 304342389], length 0
09:49:40.661433 IP (tos 0x0, ttl 64, id 54638, offset 0, flags [DF], proto TCP (6), length 52)
my-domain.com.661 > ip-111.222.333.444.ip.prioritytelecom.net.sunrpc: Flags [F.], cksum 0x5d7c (incorrect -> 0xb731), seq 97, ack 53, win 502, options [nop,nop,TS val 648325003 ecr 304342389], length 0
09:49:40.668966 IP (tos 0x0, ttl 53, id 46384, offset 0, flags [DF], proto TCP (6), length 52)
 
Last edited:
We're experiencing the same issues here.

I ran this down to the point that we decided to roll back to version 5.4

So it's definitely something to do with rpcinfo probe failling in Proxmox v6.0. If I do "rpcinfo <synology-server-ip>" then I get back a list of services available on the Synology. However, if I do "rpcinfo -p <synology-server-ip>" then I get "No route to host". Of course, this means that showmount results in the same error message.

I have a couple other locations that I have test setups with various NFS servers that aren't Synology... I'll be testing these out soon.
 
Technical John said:
We're experiencing the same issues here.

I ran this down to the point that we decided to roll back to version 5.4

So it's definitely something to do with rpcinfo probe failling in Proxmox v6.0. If I do "rpcinfo <synology-server-ip>" then I get back a list of services available on the Synology. However, if I do "rpcinfo -p <synology-server-ip>" then I get "No route to host". Of course, this means that showmount results in the same error message.

I have a couple other locations that I have test setups with various NFS servers that aren't Synology... I'll be testing these out soon.
Click to expand...

To add to this, today we decided to try the "fix" on the synology of unchecking the box "Reply to ARP requests if the target IP address is a local address configured on the incoming interface". It worked... for the 6.0 box, but the 5.4 boxes stopped being able to access the Synology NFS share.

We're going to go ahead and move forward to 6.0, since we have this working... but here's the network info, since this is related to that...

All proxmox boxes have dual ethernet ports, bonded in active-backup mode, both the 5.4 and 6.0. The Synology has the same.
 
Hi,
I use both 5.4.13 and 6.0.9 Proxmox servers.
With 5.4.13 no problem to connect to Synology with lastest DSM (6.2.2-24922 Update 3 ).

Same configuration on 6.0.9, it does not work.

When I try to use the proxmox UI, it does not work.
When I try to make a "showmount -a mynashostaddress", I get "rpc mount export: RPC: Timed out".

When I run tcpdump on the NAS and on the proxmox server, I can see that they discuss... but I get the same result...

Here above the tcpdump output on proxmox 6.0.9:
root@vmhost1:~# tcpdump host mynashostaddress
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
19:24:07.614710 IP proxmoxhostaddress.704 > mynashostaddress.sunrpc: Flags , seq 2083305489, win 64240, options [mss 1460,sackOK,TS val 22623618 ecr 0,nop,wscale 7], length 0
19:24:07.624473 IP mynashostaddress.sunrpc > proxmoxhostaddress.704: Flags [S.], seq 3950101285, ack 2083305490, win 28960, options [mss 1460,sackOK,TS val 181204421 ecr 22623618,nop,wscale 7], length 0
19:24:07.624518 IP proxmoxhostaddress.704 > mynashostaddress.sunrpc: Flags [.], ack 1, win 502, options [nop,nop,TS val 22623628 ecr 181204421], length 0
19:24:07.624697 IP proxmoxhostaddress.704 > mynashostaddress.sunrpc: Flags [P.], seq 1:97, ack 1, win 502, options [nop,nop,TS val 22623628 ecr 181204421], length 96
19:24:07.635058 IP mynashostaddress.sunrpc > proxmoxhostaddress.704: Flags [.], ack 97, win 227, options [nop,nop,TS val 181204431 ecr 22623628], length 0
19:24:07.635095 IP mynashostaddress.sunrpc > proxmoxhostaddress.704: Flags [P.], seq 1:53, ack 97, win 227, options [nop,nop,TS val 181204431 ecr 22623628], length 52
19:24:07.635104 IP proxmoxhostaddress.704 > mynashostaddress.sunrpc: Flags [.], ack 53, win 502, options [nop,nop,TS val 22623638 ecr 181204431], length 0
19:24:07.635194 IP proxmoxhostaddress.704 > mynashostaddress.sunrpc: Flags [F.], seq 97, ack 53, win 502, options [nop,nop,TS val 22623638 ecr 181204431], length 0
19:24:07.645126 IP mynashostaddress.sunrpc > proxmoxhostaddress.704: Flags [F.], seq 53, ack 98, win 227, options [nop,nop,TS val 181204441 ecr 22623638], length 0
19:24:07.645172 IP proxmoxhostaddress.704 > mynashostaddress.sunrpc: Flags [.], ack 54, win 502, options [nop,nop,TS val 22623648 ecr 181204441], length 0
19:26:19.266075 IP proxmoxhostaddress.704 > mynashostaddress.sunrpc: UDP, length 92
19:26:19.276395 IP mynashostaddress.sunrpc > proxmoxhostaddress.704: UDP, length 48

As we can see, nas and proxmox are trying to exchange packets... but it seems they do not understand each other ;)

Any suggestion ?

Edit1: I've forgoten to say that I've tried on the Nas:
- to disable or enable the check box for ARP response for same local address
- to disable NFS V4
(with reboot of the nas after change).

Edit2: the nas and the proxmox server are not on same network (like proxmox 5.4 which work with the same nas).
 
Last edited:
Guys +1 NFS is not working on 6.04 clean install. Sadly, very needed in my case. >>> Problem resolved by adding dns record /etc/hosts on proxmox machine. Monitoring for stability.
 
Last edited:
I have the same problems with 6.1.3 version and qnap nas. And same tcpdump errors. rpcinfo -p (no rout to the host)
 
Same issue. NAS: Thecus N2800.
Works perfectly with Proxmox 5, fails on Proxmox 6.
The server with Proxmox 6 used to work fine with this NAS prior to upgrade (to cross off the hardware issues).
Firewall is disabled.
 
To test, is it working with an Ubuntu 19.10? Proxmox VE uses an Ubuntu Kernel with extra patches on top. Proxmox VE 6.1 runs Kernel 5.3 (latest available pve-kernel-5.3.13-1).
 
@Alwin - it is working on Ubuntu 19.10.
Moreover, i can mount it manually via mount -t nfs on Proxmox.
But when trying to use pvesm add nfs, it fails.
If i understand correctly, it should be an alias for the mount command, am i right?
It's totally weird why one works and the other one fails.
 
What are the options of the manual mount? The NFS storage plugin, also just calls mount. ATM, I can't reproduce the issue.

EDIT: maybe it is a network issue, as some users seem to have their NAS with dual port NICs connected to the network.
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back