Unable To Play Or Access Media - NFS

Help and Support Vero 4K / Vero 4K +
1

Logs: http://paste.osmc.tv/ifisaketiq

Hello,

Just upgraded my system but kept all the same drives, file paths, and local IP. I am running OSMC on Vero 4K and have my media on an HTPC using hanewin NFS with fstab mounts via wired ethernet.

I am currently unable to play any media on OSMC after the upgrade and OSMC freezes when I try to access the file section. Furthermore, when using WinSCP to SSH into OSMC going to the mnt folder causes OSMC to crash too.

Is there a solution that does not involve re-adding fstab mounts and thus meaning I will have all my data reset including unwatched/watched statues?

Additionally, if reinstalling an OS on a new system requires new fstab mounts is there a way to back them up?

Thanks

2

Let’s start with the output of showmount -e 192.168.2.16

3

Thanks for the quick reply.

Here’s the output: Capture

Essentially no output, just lingers on putty and doesn’t do anything

EDIT: Just after my post I got: clnt_create: RPC: Timed out t

4

That sounds like a firewall issue on the Hanwin server.
What does ping 192.168.2.16 says?
Also install nmap sudo apt-get install nmap then run nmap 192.168.2.16

5 
`PING 192.168.2.16 (192.168.2.16): 56 data bytes
64 bytes from 192.168.2.16: seq=0 ttl=128 time=3.154 ms
64 bytes from 192.168.2.16: seq=1 ttl=128 time=1.010 ms
64 bytes from 192.168.2.16: seq=2 ttl=128 time=0.835 ms
64 bytes from 192.168.2.16: seq=3 ttl=128 time=0.938 ms
64 bytes from 192.168.2.16: seq=4 ttl=128 time=0.970 ms
64 bytes from 192.168.2.16: seq=5 ttl=128 time=0.933 ms
64 bytes from 192.168.2.16: seq=6 ttl=128 time=0.938 ms
64 bytes from 192.168.2.16: seq=7 ttl=128 time=0.916 ms
64 bytes from 192.168.2.16: seq=8 ttl=128 time=0.919 ms
64 bytes from 192.168.2.16: seq=9 ttl=128 time=0.930 ms
64 bytes from 192.168.2.16: seq=10 ttl=128 time=0.965 ms
64 bytes from 192.168.2.16: seq=11 ttl=128 time=1.002 ms
64 bytes from 192.168.2.16: seq=12 ttl=128 time=0.861 ms
64 bytes from 192.168.2.16: seq=13 ttl=128 time=1.036 ms
64 bytes from 192.168.2.16: seq=14 ttl=128 time=0.919 ms
64 bytes from 192.168.2.16: seq=15 ttl=128 time=0.929 ms
64 bytes from 192.168.2.16: seq=16 ttl=128 time=0.868 ms
64 bytes from 192.168.2.16: seq=17 ttl=128 time=0.941 ms
64 bytes from 192.168.2.16: seq=18 ttl=128 time=0.960 ms
64 bytes from 192.168.2.16: seq=19 ttl=128 time=0.858 ms
64 bytes from 192.168.2.16: seq=20 ttl=128 time=1.002 ms
64 bytes from 192.168.2.16: seq=21 ttl=128 time=0.973 ms
64 bytes from 192.168.2.16: seq=22 ttl=128 time=0.991 ms
64 bytes from 192.168.2.16: seq=23 ttl=128 time=0.928 ms
64 bytes from 192.168.2.16: seq=24 ttl=128 time=0.972 ms
64 bytes from 192.168.2.16: seq=25 ttl=128 time=0.840 ms

``
osmc@osmc:~$ nmap 192.168.2.16
Starting Nmap 7.70 ( https://nmap.org ) at 2020-11-27 02:22 AST
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.18 seconds

I will double check my port-forwarding that may be the issue here

6

Can confirm firewall was the issue. All is good now. Much thanks @fzinken