NFS problems after fresh install of Fedora 30 - problem solved

I just installed Fedora 30 to my computers and 2 days later had a ssd die. I have one machine which runs Plex and the OS was on the ssd. Replaced the ssd and installed fresh Fedora 30 Xfce to a fresh blank ssd. I have 5 hdds with data that I had been running with NFS so I could access from my desktop (runs Fedora 30 Xfce also). I wrote the /etc/exports the same way as before and restarted the nfs-server. On my desktop I have the files mounted under /media/nfs and the directories are there but empty. Using mount -a just tells me that “no route to host”.
On a different computer I have a VM running Fedora 30 server edition and one directory exported to my desktop and it is working fine and the desktop has it mounted.
2 of the computer firewalls show NFS3 and NFS4 while the desktop shows NFS and NFS3. Desktop and Plex computer can ping each other without a problem.

Any suggestions or help is greatly appreciated.

Thanks,
john

This is the exports file from the Plex computer:

/mnt/Media/Plex/music   192.168.1.241/255.255.255.0(rw)
/mnt/Media/Plex/Photos  192.168.1.241/255.255.255.0(rw)
/mnt/Movies             192.168.1.241/255.255.255.0(rw)
/mnt/Movies-1           192.168.1.241/255.255.255.0(rw)
/mnt/Movies-2           192.168.1.241/255.255.255.0(rw)
/mnt/Movies-3           192.168.1.241/255.255.255.0(rw)
/mnt/TV_Shows           192.168.1.241/255.255.255.0(rw)
/mnt/TV_Shows-1         192.168.1.241/255.255.255.0(rw)
/mnt/TV_Shows-2         192.168.1.241/255.255.255.0(rw)
/mnt/TV_Shows-3         192.168.1.241/255.255.255.0(rw)

Spence-Main

/mnt/Media/Plex/music   192.168.1.101/255.255.255.0(rw)
/mnt/Media/Plex/Photos  192.168.1.101/255.255.255.0(rw)
/mnt/Movies             192.168.1.101/255.255.255.0(rw)
/mnt/Movies-1           192.168.1.101/255.255.255.0(rw)
/mnt/Movies-2           192.168.1.101/255.255.255.0(rw)
/mnt/Movies-3           192.168.1.101/255.255.255.0(rw)
/mnt/TV_Shows           192.168.1.101/255.255.255.0(rw)
/mnt/TV_Shows-1         192.168.1.101/255.255.255.0(rw)
/mnt/TV_Shows-2         192.168.1.101/255.255.255.0(rw)
/mnt/TV_Shows-3         192.168.1.101/255.255.255.0(rw)

no route to host indicates that there is rather some network issue. Can you ping the server from the desktop? What is the output of ip route on the desktop?

Must be a different time zone here, I just woke up :slight_smile:
I can pin from each to the other and I have just double checked and the service Plex and it’s port are in both firewalls. Also, I don’t think I mentioned it but systemctl start nfs-server will not complete, just hangs.

thanks, john

My apologies, but I forgot to do part of you answer. ip route is below:

[john@spence-main ~] ip route default via 192.168.1.1 dev enp6s0 proto static metric 100 192.168.1.0/24 dev enp6s0 proto kernel scope link src 192.168.1.101 metric 100 192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown 192.168.254.0/24 dev virbr2 proto kernel scope link src 192.168.254.1 linkdown [john@spence-main ~]

I do use static routes for the most part and my desktop is 192.168.1.101

john

You could try to showmount -e <nfs-server-ip> from the client. Showing the content of /etc/fstab could also help.

[root@spence-main john]# showmount -e 192.168.1.201
rpc mount export: RPC: Unable to receive; errno = No route to host
[root@spence-main john]#

/etc/fstab

Created by anaconda on Fri Jan 11 09:07:36 2019

Accessible filesystems, by reference, are maintained under ‘/dev/disk/’.

See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.

After editing this file, run ‘systemctl daemon-reload’ to update systemd

units generated from this file.

UUID=2323b73d-11a3-44ee-ab22-3b1f42c358e3 / ext4 defaults 1 1
UUID=770082f8-e897-4508-a9e1-adceca33824e /boot ext4 defaults 1 2
UUID=C763-1AB4 /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=9c6cf4ba-d1e2-46ab-8f58-10907f1f4f32 /home ext4 defaults 1 2
UUID=b554150a-7b81-46fc-a231-3763d6af184c swap swap defaults 0 0

My Add-Ons

UUID=6840bfa3-90fb-49f9-a3d5-ea8b142d4798 /mnt/files ext4 defaults 0 0
UUID=213ee227-7c8b-48e0-83d3-40b02b41a219 /mnt/Backups ext4 auto 0 0
UUID=9e968262-3dc1-47c0-b780-fc07ddd25265 /mnt/storage-2tb ext4 defaults 0 0

nfs

192.168.1.201:/mnt/Movies /media/nfs/Movies nfs defaults 0 0
192.168.1.201:/mnt/Movies-1 /media/nfs/Movies-1 nfs defaults 0 0
192.168.1.201:/mnt/Movies-2 /media/nfs/Movies-2 nfs defaults
192.168.1.201:/mnt/Movies-3 /media/nfs/Movies-3 nfs defaults 0 0
192.168.1.201:/mnt/TV_Shows /media/nfs/TV_Shows nfs defaults 0 0
192.168.1.201:/mnt/TV_Shows-1 /media/nfs/TV_Shows-1 nfs defaults 0 0
192.168.1.201:/mnt/TV_Shows-2 /media/nfs/TV_Shows-2 nfs defaults
192.168.1.201:/mnt/TV_Shows-3 /media/nfs/TV_Shows-3 nfs defaults
192.168.1.201:/mnt/Media/Plex/music /media/nfs/music nfs defaults 0 0
192.168.1.201:/mnt/Media/Plex/Photos /media/nfs/Photos nfs defaults 0 0
192.168.1.241:/mnt/usenet /media/nfs/usenet nfs defaults 0 0

everything worked before the ssd crashed and I had to replace it

Thanks for your help,

john

This seem very likely to be an firewall issue. You should review the firewall rules at your server and the client. To double-check this you might want to disable the firewall temporarily on both sides, test the mount. And if successful start the firewalls again and check the rules.

1 Like

Ok, I will give that a try. Again, thank you very much for your help.

I am going to close this because if that doesn’t work I am just going to move everything to eliminate the problem. Not ideal and I will probably continue to try again at some point in the future.

john

@thomaswood,

I finally had some free time and dug into the firewall settings on the Plex server. Found that mountd was not added in the firewall. Once I allowed this everything else fell into place.

Thank very much for your help and you were definitely correct about it being firewall problem.

john

1 Like