Welcome to Incremental Social! Learn more about this project here!
Check out lemmyverse to find more communities to join from here!

Burn1ngBull3t

@Burn1ngBull3t@lemmy.world

This profile is from a federated server and may be incomplete. Browse more on the original instance.

Burn1ngBull3t OP , (edited )

Hello @theit8514

You are actually spot on ^^

I did look in my exports file which was like so :/mnt/DiskArray 192.168.0.16(rw) 192.168.0.65(rw)

I added a localhost line in case: /mnt/DiskArray 127.0.0.1(rw) 192.168.0.16(rw) 192.168.0.65(rw)

It didn't solve the problem.
I went to investigate with the mount command:

  • Will mount on 192.168.0.65:
    mount -t nfs 192.168.0.55:/mnt/DiskArray/mystuff/ /tmp/test

  • Will NOT mount on 192.168.0.55 (NAS):
    mount -t nfs 192.168.0.55:/mnt/DiskArray/mystuff/ /tmp/test

  • Will mount on 192.168.0.55 (NAS):
    mount -t nfs 127.0.0.1:/mnt/DiskArray/mystuff/ /tmp/test

The mount -t nfs 192.168.0.55 is the one that the cluster does actually.
So i either need to find a way for it to use 127.0.0.1 on the NAS machine, or use a hostname that might be better to resolve

EDIT:

I was acutally WAY simpler.

I just added 192.168.0.55 to my /etc/exports file.
It works fine now ^^

Thanks a lot for your help@theit8514 !

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • incremental_games
  • meta
  • All magazines