# Unable to mount an NFS drive **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [December 28, 2021, 10:45am UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985 "2021-12-28T10:45:42Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![brianread108](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brianread108/32/1537_2.png) [@brianread108](https://forums.rockylinux.org/u/brianread108)\ **Post date:** [December 28, 2021, 10:45am UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/1 "2021-12-28T10:45:42Z")
Using proxmox LXC Container Rocky 8.5 image. I get “permisssion denied” when I try to mount an NFS drive (which IS mountable by an Ubuntu LXC). Selinux is disabled. What should I look for? ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [December 28, 2021, 11:18am UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/2 "2021-12-28T11:18:25Z")
Hi, when using your mount command, add: `-vvv` which will expand on the verbose output. You can try with `-v` but generally one or two more provide extra output, so `-vv` will provide more, and `-vvv` even more output. Also check your /var/log/messages file as this can also hint at why it’s unable to mount. ---
**Author:** ![brianread108](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brianread108/32/1537_2.png) [@brianread108](https://forums.rockylinux.org/u/brianread108)\ **Post date:** [December 28, 2021, 11:23am UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/3 "2021-12-28T11:23:22Z")
Thanks for your suggestion: ```auto [root@emby11 ~]# mount -a -vvvv mount.nfs: timeout set for Tue Dec 28 11:23:23 2021 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.100.88,clientaddr=192.168.100.92' mount.nfs: mount(2): Operation not permitted mount.nfs: trying text-based options 'addr=192.168.100.88' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.100.88 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.100.88 prog 100005 vers 3 prot UDP port 60935 mount.nfs: mount(2): Operation not permitted mount.nfs: Operation not permitted [root@emby11 ~]# ``` ---
**Author:** ![brianread108](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brianread108/32/1537_2.png) [@brianread108](https://forums.rockylinux.org/u/brianread108)\ **Post date:** [December 28, 2021, 11:24am UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/4 "2021-12-28T11:24:20Z")
Here’s my /etc/fstab. ```auto [root@emby11 ~]# cat /etc/fstab filestore:/music/files /srv/storage/Music/ nfs defaults 0 0 [root@emby11 ~]# ``` ---
**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\ **Post date:** [December 28, 2021, 12:04pm UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/5 "2021-12-28T12:04:40Z")
Can your verify that the ports are not blocked by a firewall. Are you also sure that it is version 4.2 for the NFS share. Also check and verify with the same `-vvv` on the Ubuntu machine that works, as this should also show what NFS version is connecting(3, 4, 4.2), as well as the ports. ---
**Author:** ![brianread108](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brianread108/32/1537_2.png) [@brianread108](https://forums.rockylinux.org/u/brianread108)\ **Post date:** [December 28, 2021, 12:13pm UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/6 "2021-12-28T12:13:59Z")
This is the ubuntu container: ```auto root@emby10 ~# mount -a -vvvv mount.nfs: timeout set for Tue Dec 28 12:13:20 2021 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.100.88,clientaddr=192.168.100.95' /srv/storage/Music : successfully mounted root@emby10 ~# ``` and firewalld is not running: ```auto [root@emby11 ~]# firewall-cmd --list-all -bash: firewall-cmd: command not found [root@emby11 ~]# ``` ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [December 28, 2021, 12:21pm UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/7 "2021-12-28T12:21:48Z")
The `firewalld.service` is not the only way to manage firewall rules. The real, currently active firewall rules are in the kernel’s nftables and can be seen with: ```auto sudo nft list ruleset ``` Client `192.168.100.95` can mount, but does server allow `192.168.100.92` as client for same exports? ---
**Author:** ![brianread108](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brianread108/32/1537_2.png) [@brianread108](https://forums.rockylinux.org/u/brianread108)\ **Post date:** [December 28, 2021, 12:32pm UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/8 "2021-12-28T12:32:08Z")
I’m afraid that command does not work! ```auto [root@emby11 ~]# nft list ruleset -bash: nft: command not found [root@emby11 ~]# sudo nft list ruleset ``` The filestore is an OpenMediaVault VM, and It does not have any specific IP connection rules. A couple of other systems connect to it. ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [December 28, 2021, 1:06pm UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/9 "2021-12-28T13:06:56Z")
No firewall-cmd nor nft? > [@brianread108](#): > > Using proxmox LXC Container Rocky 8.5 image. It is probably usual for container/cloud to not have any firewall _in_ them and filtering is done by the platform on which they run. Therefore, does “proxmox LXC” have any such settings? ---
**Author:** ![anemarkus](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@anemarkus](https://forums.rockylinux.org/u/anemarkus)\ **Post date:** [December 28, 2021, 1:59pm UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/10 "2021-12-28T13:59:34Z")
> [@jlehtone](#): > > Client `192.168.100.95` can mount, but does server allow `192.168.100.92` as client for same exports? what is the content of /etc/exports on the nfs server? ---
**Author:** ![brianread108](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brianread108/32/1537_2.png) [@brianread108](https://forums.rockylinux.org/u/brianread108)\ **Post date:** [December 28, 2021, 4:02pm UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/11 "2021-12-28T16:02:46Z")
Relevant contents of /etc/export (generated by OpenMediaVault) ```auto /export/music 192.168.100.0/24(fsid=f4211af4-9fad-4dc3-8707-14c9fcc7e310,rw,subtree_check,insecure) ``` Actually I have just spotted that the new container is “Unpriviledged” (set to “yes”), whereas the old one is set to “no”. Looks like I can switch it by backing up and restoring - I’ll try that. ---
**Author:** ![brianread108](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brianread108/32/1537_2.png) [@brianread108](https://forums.rockylinux.org/u/brianread108)\ **Post date:** [December 28, 2021, 4:17pm UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/12 "2021-12-28T16:17:57Z")
> [@brianread108](#): > > Actually I have just spotted that the new container is “Unpriviledged” (set to “yes”), whereas the old one is set to “no”. Looks like I can switch it by backing up and restoring - I’ll try that. …and that was it!. Thanks for the attention, I’ve been wrestling with this off and on for a few days. Much appreciated. ---
**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brian/32/5777_2.png) [@brian](https://forums.rockylinux.org/u/brian)\ **Post date:** [August 25, 2023, 3:58am UTC](https://forums.rockylinux.org/t/unable-to-mount-an-nfs-drive/4985/13 "2023-08-25T03:58:39Z")