Odroid N2 + Kodi + XigmaNAS : How to configure NFS

Troubleshooting
1

Creating a bug report/issue

Required Information

  • DietPi version | 8
  • Distro version | bullseye
  • Kernel version | Linux DietPi 6.1.11-meson64 #23.02.2 SMP PREEMPT Sat Feb 18 00:07:55 UTC 2023 aarch64 GNU/Linux
  • Architecture | arm64
  • SBC model | Odroid N2 (aarch64)
  • Power supply used | 5V 3A
  • SD card used | SanDisk ultra

Additional Information

  • Software title | KODI v19
  • Was the software title installed freshly or updated/migrated? Installed freshly
  • Can this issue be replicated on a fresh installation of DietPi? Yes

Steps to reproduce

Hi Guys

I’m trying to make my NAS (XIGMANAS) available for KODI via NFS and I can’t figure it : how to add folders/drives. It’s may be a defaults to a single one being visible/accessible in kodi, in dietpi or in xigmanas.

Can someone explain to me ?

My setting is:
_Xigmanas:
>nfs server is running
>nfs v4 enable
>folder shared is mnt / Data 1
>the network that is authorised to access the NFS shared : IP ODROID and port 24
>export all the directories in the specified path : enable
>export as WebNFS : disable
_Odroid
>nsf client : installed
>nsf serveur : not installed

The problem is when i tap the IP of XIGMANAS in KODI there is no result.

BR
Nicolas

2

Did you tried to mount your NFS share using dietpi-drive_manager?? This way you can check if your NFS server is working fine.

3

Hi.
dietpi-drive-manger didn’t find the NFS Server (XIGMANAS) :thinking:

4

probably an issue with your NFS server setup. You could use following to verify available shares

showmount -e <ip.of.nfs.server>
5

Hi Guys.
I had many issues with my serveur but now it’s good.
So $ showmount -e localhost show me :

Exports list on localhost:
/mnt/XL01/Share
with the IP adress of Dietpi (…1.59)

but Drive Manager don’t see the serveur (…1.250):

 mount.nfs: trying text-based options
│ 'port=2049,vers=4.2,addr=192.168.1.250,clientaddr=192.168.1.59'
│ mount.nfs: trying text-based options
│ 'port=2049,vers=4.2,addr=192.168.1.250,clientaddr=192.168.1.59'
│ mount.nfs: trying text-based options
│ 'port=2049,vers=4.2,addr=192.168.1.250,clientaddr=192.168.1.59'
│ mount.nfs: trying text-based options
│ 'port=2049,vers=4.2,addr=192.168.1.250,clientaddr=192.168.1.59'
│ mount.nfs: trying text-based options
│ 'port=2049,vers=4.2,addr=192.168.1.250,clientaddr=192.168.1.59'
│ mount.nfs: trying text-based options
│ 'port=2049,vers=4.2,addr=192.168.1.250,clientaddr=192.168.1.59'
│ mount.nfs: trying text-based options
│ 'port=2049,vers=4.2,addr=192.168.1.250,clientaddr=192.168.1.59'
│ mount.nfs: trying text-based options
│ 'port=2049,vers=4.2,addr=192.168.1.250,clientaddr=192.168.1.59'
│ mount.nfs: trying text-based options
│ 'port=2049,vers=4.2,addr=192.168.1.250,clientaddr=192.168.1.59'
│
│                                    <Ok>

Could you give me your advice?

6

you need to do showmount on client side

showmount -e <ip.of.your.server>
7

Here the result :
root@DietPi:~# showmount -e 192.168.1.250
clnt_create: RPC: Unable to receive
:grimacing:

8

That’s the whole error message?

Do you have a firewall in between?

9

root@DietPi:~# showmount -e 192.168.1.250
clnt_create: RPC: Unable to receive
root@DietPi:~#

and

I tryed this:

root@DietPi:~# rpcinfo -p 192.168.1.59
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
root@DietPi:~# service nfs start
Failed to start nfs.service: Unit nfs.service not found.

There are no firewall

root@DietPi:~# journalctl -u nfs*
Oct 28 17:54:15 DietPi systemd[1]: Reached target nfs-client.target - NFS client services.