Create storage failed mount error mount nfs access denied by server while mounting

[Solved] NFS-Storage mount error 500 after Update

Kalle Wisch

New Member

Hi to all Proxmox fans!

I updated to the latest Version of Proxmox and after that
I could not mount same nfs share as before.
‘mount error: mount.nfs: an incorrect mount option was specified (500)’

Working nfs mounting:
pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-24 (running version: 3.1-24/060bd5a6)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-9
libpve-access-control: 3.0-8
libpve-storage-perl: 3.0-18
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Not working nfs mounting:
pveversion -v
proxmox-ve-2.6.32: 3.1-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.1-43 (running version: 3.1-43/1d4b0dfb)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-24-pve: 2.6.32-111
pve-kernel-2.6.32-25-pve: 2.6.32-113
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-13
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

If I try it on prompt:
root@proxmox:

# mount.nfs -v NFS-SERVER:/Sicherung /mnt/pve/NAS-NFS/ -o vers=3,nolock -vvv
mount.nfs: timeout set for Wed Feb 19 15:31:20 2014
mount.nfs: trying text-based options ‘vers=3,nolock,addr=NFS-SERVER’
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying NFS-SERVER prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying NFS-SERVER prog 100005 vers 3 prot UDP port 45924

cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content images,iso,vztmpl,rootdir

nfs: NFS-NAS
path /mnt/pve/NFS-NAS
server NFS-SERVER
export /Sicherung
options vers=3
content backup
maxfiles 1

Источник

[SOLVED] nfs mount error

BP2010

Member

I have setup a folder on my Synology NAS to backup my ProxMox server. Everything worked perfect until I had to change the location of my NAS.
I got a new IP Address and an error:

mount error: mount.nfs: access denied by server while mounting 192.168.1.142:/volume1/Ordination (500)

I changed the IP address at /etc/pve/storage.cfg

cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content vztmpl,iso,backup

lvmthin: local-lvm
thinpool data
vgname pve
content images,rootdir

nfs: Backup
export /volume1/Ordination
path /mnt/pve/Backup
server 192.168.1.142
content backup
maxfiles 5

zfspool: ZFS-MCW-Pool
pool myPool/MCW
content rootdir,images
sparse 0

pveversion -v
proxmox-ve: 6.0-2 (running kernel: 5.0.21-1-pve)
pve-manager: 6.0-6 (running version: 6.0-6/c71f879f)
pve-kernel-5.0: 6.0-7
pve-kernel-helper: 6.0-7
pve-kernel-4.15: 5.4-8
pve-kernel-5.0.21-1-pve: 5.0.21-2
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph-fuse: 12.2.12-pve1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.11-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-7
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-64
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-7
pve-cluster: 6.0-7
pve-container: 3.0-5
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-2
pve-qemu-kvm: 4.0.0-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve2

But the error still appears.

Obviously, I am doing something wrong. Is there another place where I have to change the ip address? Any help would be appreciated.

Источник

CentOS

The Community ENTerprise Operating System

[solved]NFS mount.nfs: access denied by server while mountin

[solved]NFS mount.nfs: access denied by server while mountin

Post by ras123 » 2016/03/01 05:43:13

Previously, the client was a RHEL4 computer, now installed a fresh centos 6.7, after that I couldn’t mount using NFS.

Re: NFS mount.nfs: access denied by server while mounting

Post by TrevorH » 2016/03/01 07:49:16

Re: NFS mount.nfs: access denied by server while mounting

Post by ras123 » 2016/03/01 07:56:42

Re: NFS mount.nfs: access denied by server while mounting

Post by TrevorH » 2016/03/01 08:28:51

Isn’t that missing a leading / on the «exports» portion?

Does the client have more than one ip address?

Re: NFS mount.nfs: access denied by server while mounting

Post by ras123 » 2016/03/01 09:59:11

Hi,
it is /exports, ‘/’ not missed.

Client has not more than one ip, the if config returns:

Re: NFS mount.nfs: access denied by server while mounting

Post by ras123 » 2016/03/01 23:21:15

where user name (on both computer user name is same), and is local network ip.

Источник

“mount.nfs: access denied by server while mounting” – how to resolve

Problem

Mounting the nfs share from CentOS/RHEL NFS server on a NFS client gives error as shown below:

You can try running the mount command with the verbose option to get an detailed error on the issue.

Solution

This is a generic issue with NFS mounting at client and can occur due to many issues. Below are some of the most commonly occuring issues.

1. Try mounting with NFSv3

Sometimes the NFS server may only support NFSv3 connections. By default the mount command uses NFSv4, which may result is the error. To avoid this specify the NFSv3 while mounting the share.

Ensure /etc/exports is properly referring to the correct NFS client information for providing access. Some NFS servers require NFS client name to be resolvable to IP, thus it should be resolvable via DNS or specified in /etc/hosts of the NFS server.. The format of the /etc/exports file is:

Client options include (defaults are listed first):
ro / rw :
a) ro : allow clients read only access to the share.
b) rw : allow clients read write access to the share.
sync / async :
a) sync : NFS server replies to request only after changes made by previous request are written to disk.
b) async : specifies that the server does not have to wait.
wdelay / no_wdelay
a) wdelay : NFS server delays committing write requests when it suspects another write request is imminent.
b) no_wdelay : use this option to disable to the delay. no_wdelay option can only be enabled if default sync option is enabled.
no_all_squash / all_squash :
a) no_all_squash : does not change the mapping of remote users.
b) all_squash : to squash all remote users including root.
root_squash / no_root_squash :
a) root_squash : prevent root users connected remotely from having root access. Effectively squashing remote root privileges.
b) no_root_squash : disable root squashing.

3. Check NFS server permissions

– There could be issue with the NFS server sharing the NFS share. Try mounting the problematic share on another NFS client, to rule out the possibility of issue at NFS server.
– Set the permission as (ro,no_root_squash,sync) for nfs export on server end and run command:

Then try to mount the NFS share directory. If specifying the NFS client in /etc/exports by domain or hostname ensure the domain name maps to the correct IP, an incorrect entry in /etc/hosts for example could cause access to be denied.

4. Using tcpdump

In very rare cases, you may have to use the tcpdump to capture tcpdump of the mount operation. Run the below command first to start capturing the network packets. In another terminal start the NFS mount operation.

Источник

mount.nfs: access denied by server while mounting

I have a problem I have been googling for at least 6 hours 28 hours with no luck. Whenever I try to mount a directory I get the following error (verbose version at end):

mount.nfs: access denied by server while mounting :

Initally I was using computer1 as the nfs server, but I have moved it over to computer2 and I am trying to mount on computers3-8 . As a further note, computer2 is now acting as the dhcp router for all other computers (even computer1 ), but I am almost certain that the problem has to do with computer2 ‘s nfs settings as I have tried the following:

1. Try mounting a folder from the original computer1 server to one of the computers3-8 clients — SUCCESS
2. Try mounting a folder from the original computer1 server to the new computer2 server — SUCCESS
3. Try mounting a folder from the new computer2 server to one of the computers3-8 clients — FAILURE
4. Try mounting a folder from the new computer2 server to the old computer1 server — FAILURE
5. Try exporting then mounting any other folder on computer2 — FAILURE
6. ssh to and from computer2 — SUCCESS

In addition to this, I have also checked to make sure that the relevant parts of the /etc/exports file do not have any mistakes. Therefore, I am almost absolutely certain this is not a permission issue.

Question: Given that this is not a network error, can anyone advise me as to how I can start debugging this problem.

Verbose output:

Verbose Output2:

Here is a more direct approach which isolates the mount to only the directory in question here:

I had come across this rpc.statd is not running but is required for remote locking error before, but all the googling in the world did not help me at all.

EDIT:

Chaos asked me to execute the following commands and display the results:

First on the server:

And then on the client

EDIT 2:

Chaos asked me to further execute the following commands and display the results:

Here is my /etc/exports file on the server. As you can see I am trying to use its name as defined in /etc/hosts , its ip address, and I am also trying to different folders to export. All other lines I omitted as they are just duplicates of the last line, just redirected to different raspis.

Here is my /etc/fstab file on my raspi5 client

EDIT 3:

Following some of the advice here I also set the insecure flag in exports, but to no avail, and here is the output of rpcinfo -p on the client and the server:

EDIT 4:

Further following some of the advice here I have gotten the following debugging logs:

EDIT 5:

I’ve made some progress and have deduced the following

1. It’s not a port issue as client can telnet into host telnet 192.168.7.1 2049
2. It’s probably not a network issue as the server can not even mount to itself
3. The old version which supported (and still supports) mounting was running nfs-kernel-server 1:1.2.4-1 whereas the new server which does not support mounting is running nfs-kernel-server 1:1.2.8-2
4. The command sudo /etc/init.d/portmap restart works on the old server, but not the new server, which tells me that I am missing portmap on the new server. However, when I try to install it via sudo apt-get install portmap , it tells me Note, selecting ‘rpcbind’ instead of ‘portmap’, and that rpcbind is already the newest version`

Edit 6:

Here is the output of iptables -L on my server:

Источник

# showmount -e 1 <nfs-server-ip>
Export list for <nfs-server-ip>

# showmount -e <nfs-server-ip>
Export list for <nfs-server-ip>
/home   192.168.122.0/24
/export-1  192.168.122.0/24
/export2   192.168.122.0/24

# rpcinfo -p <nfs-server-ip>
   program vers proto   port  service
    100000    2   udp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    3   udp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    4   tcp    111  portmapper
    100003    3   udp   2049  nfs
    100003    3   tcp   2049  nfs
    100005    1   udp    635  mountd
    100005    2   udp    635  mountd
    100005    3   udp    635  mountd
    100005    1   tcp    635  mountd
    100005    2   tcp    635  mountd
    100005    3   tcp    635  mountd
    100021    4   udp   4045  nlockmgr
    100021    4   tcp   4045  nlockmgr
    100024    1   udp   4046  status
    100024    1   tcp   4046  status

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.