unfortunately just a typo on discourse, it doesn’t work at all on my vero 
I’m doing something wrong.
Did you check this machine to make sure you didn’t already have something setup in fstab like you did with the first machine? Did you try the troubleshooting as explained in the autofs guide. ie…
To test if your mounts works execute:
ls -lah /mnt/<server1>/<share1>you should see the files from your network share. If it didn’t work run
sudo systemctl stop autofs sudo automount -f -v -dto debug what’s wrong. While this is running, it will appear to keep trying to mount. That’s normal. While automount is running, open another SSH connection and try:
ls -lah /mnt/<server1>/<share1>again while watching the output from the automount command.
To exit if running automount, just do a CTRL-C. To restart the service once everything is working, either reboot or:
sudo systemctl start autofs
2 Likes
Did you also copy (or adjust) auto.master?
I added
sudo nano /etc/auto.nfs.shares
/mnt/Movie 192.168.1.120:/v/Movie
/mnt/Shows 192.168.1.120:/t/Shows
/mnt/Anime 192.168.1.120:/r/Anime
/mnt/Films 192.168.1.120:/Films
and this to auto.master
/- /etc/auto.nfs.shares --timeout 15 browse
stopping autofs and running automount -f -v -d gives me these errors
l version 5.02
lookup_nss_read_master: reading master file /etc/auto.master
do_init: parse(sun): init gathered global options: (null)
lookup_read_master: lookup(file): read entry +dir:/etc/auto.master.d
lookup_nss_read_master: reading master dir /etc/auto.master.d
lookup(dir): dir map /etc/auto.master.d missing or not readable
lookup(file): failed to read included master map dir:/etc/auto.master.d
lookup_read_master: lookup(file): read entry +auto.master
lookup_nss_read_master: reading master files auto.master
do_init: parse(sun): init gathered global options: (null)
lookup(file): failed to read included master map auto.master
lookup_read_master: lookup(file): read entry /-
master_do_mount: mounting /-
automount_path_to_fifo: fifo name /var/run/autofs.fifo--
lookup_nss_read_map: reading map file /etc/auto.nfs.shares
do_init: parse(sun): init gathered global options: (null)
mounted direct on /mnt/Anime with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/Anime
mounted direct on /mnt/Movie with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/Movie
mounted direct on /mnt/Shows with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/Shows
mounted direct on /mnt/Films with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/Films
st_ready: st_ready(): state = 0 path /-
st_expire: state 1 path /-
expire_proc: exp_proc = 4100977744 path /-
expire_cleanup: got thid 4100977744 path /- stat 0
expire_cleanup: sigchld: exp 4100977744 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
st_expire: state 1 path /-
expire_proc: exp_proc = 4100977744 path /-
expire_cleanup: got thid 4100977744 path /- stat 0
expire_cleanup: sigchld: exp 4100977744 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
st_expire: state 1 path /-
expire_proc: exp_proc = 4100977744 path /-
expire_cleanup: got thid 4100977744 path /- stat 0
expire_cleanup: sigchld: exp 4100977744 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
st_expire: state 1 path /-
expire_proc: exp_proc = 4100977744 path /-
expire_cleanup: got thid 4100977744 path /- stat 0
expire_cleanup: sigchld: exp 4100977744 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-So and ls -lah /mnt/Films still gives error?
What is mount | paste-log and paste-log /etc/fstab?
ls -lah /mnt/Films
ls: cannot access '/mnt/Films': No such file or directory
https://paste.osmc.tv/komoqarocu
https://paste.osmc.tv/iyawihinut
Guess that was with autofs not started, or?
End the testing session and sudo systemctl restart autofs and then run mount | paste-log again.
Also provide ls -lah /mnt/
I have no idea, the problems keep piling up and start to blur together a little haha.
Can you post showmount -e 192.168.1.120
showmount -e 192.168.1.120
Export list for 192.168.1.120:
/Shows 192.168.1.114,-readonly
/Movies 192.168.1.114,-readonly
/Anime 192.168.1.114,-readonly
/Films 192.168.1.114,-readonly
says everything shows up
You might also check Hanewin to make sure you have allowed the ip of the machine you are currently trying to get working. We had a previous conversation about this as you had opted to only give access in that program to individual machines instead of just allowing access to the entire subnet.
You might also check Hanewin to make sure you have allowed the ip of the machine you are currently trying to get working. We had a previous conversation about this as you had opted to only give access in that program to individual machines instead of just allowing access to the entire subnet.
It has full access to these boxes, I did them all manually but they all have access, I just tried to play something and it works 
OMG you changed your exports !?! Did you give them new names?
With this you need to update all your auto.nfs.shares to
/mnt/Movie 192.168.1.120:/Movie
/mnt/Shows 192.168.1.120:/Shows
/mnt/Anime 192.168.1.120:/Anime
/mnt/Films 192.168.1.120:/Films
Also as @darwindesign you would need to allow access from all your client IP’s
I didn’t change anything, this is just how it is on this box, idk how it’s set.
I added
/mnt/Movie 192.168.1.120:/Movie
/mnt/Shows 192.168.1.120:/Shows
/mnt/Anime 192.168.1.120:/Anime
/mnt/Films 192.168.1.120:/Films
to auto.nfs.share
As I wrote before showmount -e is not related to the client side. It in general shows how the server announces the exports.
So means names and allowed IP’s have changed on the server.
Is it working after reboot? What is the IP of the client you just work on?
I swear I didn’t touch anything. My mounts have always been the same, the only difference is the box and the rules in my hanewin. If neither could cause that I’m getting hacked at the moment haha
I am rebooting now, the IP is 114
edit:
ls -lah /mnt/Films works
‘rules in my hanewin’ that means the NFS Server configuration that you changed.
Get the names fixed in Hanewin (as you have them now leave them as they are). You just need to add all your client IP as allowed (which you currently don’t).
But it will not work on your Pi anymore.
how would one do that? I copied my settings from someone else a long time ago (see above for the export)
Works on both devices I don’t know if I can check all paths manually but Films works on both of them.
Show your current hanewin export file then we can advice