Proxmox cannot see my Synology NAS NFS on the network

[dosh]

Hi,

I am setting up my first Proxmox instance, and met a roadblock out of the gate.

I am running NFS from my synology NAS (192.168.1.10), but cannot seem to find this from my Proxmox. In ssh, I run:

showmount -e 192.168.1.10
rpc mount export: RPC: Unable to receive; errno = No route to host

Running the same command from my Mac

showmount -e 192.168.1.10
Exports list on 192.168.1.10:
/volume1/Proxmox                    192.168.1.0/24

I am able to ping 192.168.1.10 from my Proxmox.

Some debugging I have seen in this forum:

ip addr show
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: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 04:42:1a:ad:b0:a2 brd ff:ff:ff:ff:ff:ff
3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 04:42:1a:57:cd:de brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 04:42:1a:57:cd:de brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.200/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::642:1aff:fe57:cdde/64 scope link
       valid_lft forever preferred_lft forever

pvesm nfsscan 192.168.1.10
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_TERMINAL = "iTerm2",
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
rpc mount export: RPC: Unable to receive; errno = No route to host
command '/sbin/showmount --no-headers --exports 192.168.1.10' failed: exit code 1

pvesm status
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_TERMINAL = "iTerm2",
    LC_CTYPE = "UTF-8",
    LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
Name             Type     Status           Total            Used       Available        %
local             dir     active        98497780         2739480        90708752    2.78%
local-lvm     lvmthin     active      1793605632               0      1793605632    0.00%

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 04:42:1a:ad:b0:a2 brd ff:ff:ff:ff:ff:ff
3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 04:42:1a:57:cd:de brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 04:42:1a:57:cd:de brd ff:ff:ff:ff:ff:ff

ip route
default via 192.168.1.1 dev vmbr0 proto kernel onlink
192.168.1.0/24 dev vmbr0 proto kernel scope link src 192.168.1.200

Has anybody come across this before?

 

[Spirog]

rpc mount export: RPC: Unable to receive; errno = No route to host

https://debugah.com/solved-rpc-mount-export-rpc-unable-to-receive-errno-no-route-to-host-8307/

firewall issue I suppose as in this link
hope it works

 

[Spirog]

Also some more info

is related to firewall. The command showmount -e IP_server shows all mounts that are available on server. This command works fine, but you have to be careful which port to open. It does not get through the firewall if only port 2049 has been opened. If the firewall on the NFS server has been configured to let NFS traffic get in, it will still block the showmount command. To test if you disable firewall on server you should get rid of this issue.

this is an excerpt from the link below

https://unix.stackexchange.com/ques...-unable-to-receive-errno-113-no-route-to-host

 

[dosh]

Thank you for the tips! It proves what I heard, that the Proxmox community is pretty damn great!

From the link above (https://debugah.com/solved-rpc-mount-export-rpc-unable-to-receive-errno-no-route-to-host-8307/) I assume I am to run the firewall-cmd command on my Synology? This is the output:

firewall-cmd --add-service=rpc-bind
-sh: firewall-cmd: command not found

Running iptables -F on my Synology gives me:

iptables -F
Fatal: can't open lock file /run/xtables.lock: Permission denied
/sbin/iptables: line 19: usleep: command not found
Fatal: can't open lock file /run/xtables.lock: Permission denied
/sbin/iptables: line 19: usleep: command not found
Fatal: can't open lock file /run/xtables.lock: Permission denied
/sbin/iptables: line 19: usleep: command not found
Fatal: can't open lock file /run/xtables.lock: Permission denied
/sbin/iptables: line 19: usleep: command not found
Fatal: can't open lock file /run/xtables.lock: Permission denied
/sbin/iptables: line 19: usleep: command not found

I can disable the Synology firewall in the UI, but this does not fix my issues on my Proxmox.

As a test, I removed my allow ICMP rule on my Synology firewall. I was not able to ping it anymore from my Proxmox or my Mac. I then disabled the firewall from the Synology UI, and was now able to ping it again - confirming the firewall was in fact disabled.

Switching to my proxmox to run the commands:

root@proxmoxbox:~# firewall-cmd --add-service=rpc-bind
-bash: firewall-cmd: command not found
root@proxmoxbox:~# showmount -e 192.168.1.10
rpc mount export: RPC: Unable to receive; errno = No route to host
root@proxmoxbox:~# iptables -F
root@proxmoxbox:~# showmount -e 192.168.1.10
rpc mount export: RPC: Unable to receive; errno = No route to host

So; turning off the firewall in Synology does not seem to help.
My Proxmox, my Mac and my Synology are on the same network. So I am a bit curious as to why they should have different behaviours.

As this is my very first Proxmox install - could I have done anything wrong in my setup? The only thing that comes to mind was the network setup in the install wizard. But it was just IP address, domain, and DNS. Nothing too crazy.

What are some other steps I could take to further pinpoint where the error is?

 

[bobmc]

Strange... should be working. I've used external nfs shares with proxmox in the past with no special requirements on a standard install and you can mount the nfs share on the mac - yes?

I don't get the same perl error messages on my system when I run pvesm commands so that might be the place to start - have you installed any additional packages on the host recently?, does apt-get update and apt-get upgrade work correctly?

 

[dosh]

This is super strange.

I did a full re-install of proxmox, added a no-subscription repository, updated. And I still have the issue when I try to add a NFS in the GUI:

create storage failed: storage 'synology' is not online (500)

I should add that I cannot click the drop-down in the Add NFS window. It doesn't show any available shares for the IP. The error above comes when I add /volume1/Proxmox manually.

I am able to mount the NFS from my Mac. And I am also able to mount the NFS on the Proxmox by SSH-ing into the Proxmox and typing

mount 192.168.1.10:/volume1/Proxmox ./test/

So; It seems like I can mount from the CLI, but not add NFS from the UI. I also still cannot do showmount -e 192.168.1.10.

 

[Spirog]

I can disable the Synology firewall in the UI, but this does not fix my issues on my Proxmox..

Just out of curiosity - can you try to disable the firewall on Proxmox from Datacenter > Firewall > Options
see if that works ?

 

[dosh]

Just out of curiosity - can you try to disable the firewall on Proxmox from Datacenter > Firewall > Options
see if that works ?

After the reinstall of proxmox it seems like the firewall is not enabled. (sorry, first time trying proxmox) Is this right?

 

[Spirog]

After the reinstall of proxmox it seems like the firewall is not enabled. (sorry, first time trying proxmox) Is this right?
View attachment 35491

yes disabled that is right.. I am all out of thoughts except if there is a way to find out what port your synology to proxmox. udp tcp port number and see if its open? or try to open that port so you can connect to proxmox.? sorry I am all out of thoughts. hopefully someone else can chime in

 

[bobmc]

are the proxmox host and the synology NAS physically connected to the same switch? there's no wifi involved at all?

can you mount cifs/smb shares on the proxmox host?

 

[dosh]

are the proxmox host and the synology NAS physically connected to the same switch? there's no wifi involved at all?

can you mount cifs/smb shares on the proxmox host?

Yes, they are both on the same QNAP 10 gbps switch. (Connected upstream to: Unifi Switch -> Unify Security Gateway -> WAN)
No wifi involved.

Mounting a CISF/SMB from my Synology works as expected.

Could it be an option to just use the SMB share for the proxmox? Or is this not recommended for VMs etc? Or perhaps iSCSI? Any recommendations?

Thank you for all the effort and replies!

 

[manwithastick]

I know this is a rather old post but it was the top result when searching for this issue that brought me here, but didn't see a solution.

In Synology DSM, Control Panel, Network. I resolved it by unchecking set as default gateway.

I went from

root@pve1:~# showmount -e 192.168.0.19
rpc mount export: RPC: Unable to receive; errno = No route to host

to

root@pve1:~# showmount -e 192.168.0.19
Export list for 192.168.0.19:
/volume2/docker *
/volume1/data *

and

root@pve1:~# rpcinfo -p 192.168.0.219
192.168.0.219: RPC: Remote system error - No route to host

to

root@pve1:~# rpcinfo -p 192.168.0.19
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
100024 1 udp 662 status
100024 1 tcp 662 status
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
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
100021 1 udp 4045 nlockmgr
100021 3 udp 4045 nlockmgr
100021 4 udp 4045 nlockmgr
100021 1 tcp 4045 nlockmgr
100021 3 tcp 4045 nlockmgr
100021 4 tcp 4045 nlockmgr