Not able to add nfs server, getting error nfs is not online

[ermanishchawla]

pveversion

proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve)
pve-manager: 6.2-6 (running version: 6.2-6/ee1d7754)
pve-kernel-5.4: 6.2-4
pve-kernel-helper: 6.2-4
pve-kernel-5.0: 6.0-11
pve-kernel-5.4.44-2-pve: 5.4.44-2
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph: 14.2.9-pve1
ceph-fuse: 14.2.9-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve2
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-3
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-network-perl: 0.4-6
libpve-storage-perl: 6.1-8
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-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-8
pve-cluster: 6.1-8
pve-container: 3.1-8
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-3
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1

 

[ermanishchawla]

Error in syslog

Jul 11 07:12:22 inc1pve25 pvestatd[2319]: storage 'vmnfs' is not online
Jul 11 07:12:31 inc1pve25 pvestatd[2319]: storage 'vmnfs' is not online
Jul 11 07:12:41 inc1pve25 pvestatd[2319]: storage 'vmnfs' is not online
Jul 11 07:12:51 inc1pve25 pvestatd[2319]: storage 'vmnfs' is not online
Jul 11 07:13:00 inc1pve25 systemd[1]: Starting Proxmox VE replication runner...
Jul 11 07:13:01 inc1pve25 systemd[1]: pvesr.service: Succeeded.
Jul 11 07:13:01 inc1pve25 systemd[1]: Started Proxmox VE replication runner.
Jul 11 07:13:01 inc1pve25 pvestatd[2319]: storage 'vmnfs' is not online

 

[ermanishchawla]

root@inc1pve25:~# showmount -e inc1vfs3


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

 

[ermanishchawla]

/etc/pve/storage.cfg


nfs: vmnfs


content images,rootdir,backup


server 172.19.2.183


export /inc1fpg/inc1vfs3/vm


path /mnt/pve/vm


options vers=4

 

[ermanishchawla]

Able to mount manually

root@inc1pve25:~# df -k | grep vm


172.19.2.183:/inc1fpg3/inc1vfs3/vm 4294967296 2343936 4292623360 1% /mnt/pve/vm

 

[ermanishchawla]

root@inc1pve25:~# nmap -p 111,2049 172.19.2.183


Starting Nmap 7.70 ( https://nmap.org ) at 2020-07-11 07:18 UTC


Nmap scan report for inc1vfs3 (172.19.2.183)


Host is up (0.00010s latency).





PORT STATE SERVICE


111/tcp open rpcbind


2049/tcp open nfs


MAC Address: 52:54:00:F5:86:3A (QEMU virtual NIC)





Nmap done: 1 IP address (1 host up) scanned in 0.55 seconds

 

[ermanishchawla]

Any update??

 

[ermanishchawla]

@t.lamprecht can you please help

 

[t.lamprecht]

What even happened, does the NFS mount never worked or did it stop working?

What does pvesm scan nfs 172.19.2.183 outputs?

Is the mount working? ls -la /mnt/pve/vm /mnt/pve/vm/images

 

[ermanishchawla]

What even happened, does the NFS mount never worked or did it stop working?

it never worked, able to mount manually

What does pvesm scan nfs 172.19.2.183 outputs?


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


command '/sbin/showmount --no-headers --exports 172.19.2.183' failed: exit code 1



Is the mount working? ls -la /mnt/pve/vm /mnt/pve/vm/images

yes mount is working

root@inc1pve25:~# df -k | grep vm


172.19.2.183:/inc1fpg3/inc1vfs3/vm 4294967296 2343936 4292623360 1% /mnt/pve/vm

 

[ermanishchawla]

errors with pvesm command
rpc mount export: RPC: Unable to receive; errno = No route to host


command '/sbin/showmount --no-headers --exports 172.19.2.183' failed: exit code 1

 

[ermanishchawla]

mount -av command output


mount.nfs: timeout set for Sun Jul 12 10:02:43 2020


mount.nfs: trying text-based options 'hard,vers=4.2,addr=172.19.2.183,clientaddr=172.19.2.32'


mount.nfs: mount(2): Protocol not supported


mount.nfs: trying text-based options 'hard,vers=4.1,addr=172.19.2.183,clientaddr=172.19.2.32'


mount.nfs: mount(2): Protocol not supported


mount.nfs: trying text-based options 'hard,vers=4.0,addr=172.19.2.183,clientaddr=172.19.2.32'


/mnt/pve/vm : successfully mounted


This are done using mounting via /etc/fstab not via pvegui

 

[t.lamprecht]

You did not post the requested commands, the mount can work but the storage can hang..
Also, you did not answered the question:

What even happened, does the NFS mount never worked or did it stop working?

 

[ermanishchawla]

Yes, nfs did not work from beginning from UI, I tried adding through /etc/pve/storage.cfg same error



root@inc1pve27:/mnt/pve/vm# ls -ltra


total 20


drwxr-xr-x 18 root root 4096 May 20 07:29 ..


drwxr-xr-x 2 root root 8192 Jul 11 06:10 .snapshot


drwxrwx--- 3 root 10544 8192 Jul 12 2020 .

 

[ermanishchawla]

pvescan nfs 172.19.2.183

errors with pvesm command
rpc mount export: RPC: Unable to receive; errno = No route to host


command '/sbin/showmount --no-headers --exports 172.19.2.183' failed: exit code 1

 

[ermanishchawla]

please note I have installed one RHEL 7 vm in the proxmox and assign the IP in same network of proxmox,
there i executed showmount -e 172.19.2.183

I got the result whereas i did not get anything on proxmox

 

[ermanishchawla]

@Alwin any suggestions?

 

[Alwin]

I have gone through this in the below thread. I was not able to reproduce the issue described.
https://forum.proxmox.com/threads/mount-no-longer-works-in-proxmox-6-nfs-synology.56503/

Try as a workaround, mount the share via fstab and set the folder to shared and is_mounted. Then create the corresponding storage entry.