ok soo ah the results of running: (It went on forever, so I only included the beginning and end, complete gibberish to me ahha)
sudo systemctl stop autofs
sudo automount -f -v -d
osmc@osmc:~$ sudo automount -f -v -d
Starting automounter version 5.1.2, master map /etc/auto.master
using kernel protocol 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 +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/192.168.1.9/TV-Shows with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/192.168.1.9/TV-Shows
mounted direct on /mnt/192.168.1.9/Movies with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/192.168.1.9/Movies
st_ready: st_ready(): state = 0 path /-
st_expire: state 1 path /-
expire_proc: exp_proc = 4096783440 path /-
expire_cleanup: got thid 4096783440 path /- stat 0
expire_cleanup: sigchld: exp 4096783440 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
st_expire: state 1 path /-
expire_proc: exp_proc = 4096783440 path /-
expire_cleanup: got thid 4096783440 path /- stat 0
expire_cleanup: sigchld: exp 4096783440 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
st_expire: state 1 path /-
expire_proc: exp_proc = 4096783440 path /-
expire_cleanup: got thid 4096783440 path /- stat 0
expire_cleanup: sigchld: exp 4096783440 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
st_expire: state 1 path /-
expire_proc: exp_proc = 4096783440 path /-
expire_cleanup: got thid 4096783440 path /- stat 0
expire_cleanup: sigchld: exp 4096783440 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
^Cdo_notify_state: signal 2
master_notify_state_change: sig 2 switching /- from 1 to 5
st_prepare_shutdown: state 1 path /-
expire_proc: exp_proc = 4096783440 path /-
expire_cleanup: got thid 4096783440 path /- stat 0
expire_cleanup: sigchld: exp 4096783440 finished, switching from 5 to 7
st_shutdown: state 5 path /-
umount_multi: path /mnt/192.168.1.9/TV-Shows incl 0
set_direct_mount_catatonic: set /mnt/192.168.1.9/TV-Shows catatonic
umounted direct mount /mnt/192.168.1.9/TV-Shows
umount_multi: path /mnt/192.168.1.9/Movies incl 0
set_direct_mount_catatonic: set /mnt/192.168.1.9/Movies catatonic
umounted direct mount /mnt/192.168.1.9/Movies
automount_path_to_fifo: fifo name /var/run/autofs.fifo--
shut down path /-
autofs stopped
So did you run ls -lah /mnt/192.168.1.9/Movies in another window? And was the output again Permission denied?
If so can you plese do sudo ls -lah /mnt/ sudo ls -lah /mnt/192.168.1.9/ sudo ls -lah /mnt/192.168.1.9/Movies
Also how have you configured the NFS shares on the Synology?
ohhh ahah opps… sorry I didn’t do it in a new window.
Running in a new window while the other one is open as per the OP, returned:
osmc@osmc:~$ ls -lah /mnt/192.168.1.9/Movies
total 12K
dr-xr-xr-x 3 root root 4.0K Nov 10 11:51 .
dr-xr-xr-x 4 root root 4.0K Apr 8 20:06 ..
dr-xr-xr-x 2 root root 4.0K Nov 10 11:56 MOVIES
osmc@osmc:~$ ls -lah /mnt/192.168.1.9/TV-Shows
total 8.0K
dr-xr-xr-x 2 root root 4.0K Apr 8 20:06 .
dr-xr-xr-x 4 root root 4.0K Apr 8 20:06 ..
osmc@osmc:~$
Ahh ok, right well now we’re getting somewhere. The folders came up in the Kodi rootfile system, mnt folder.
I was able to add each mnt into the database, however, the folders were all empty…
Ahh I have created a user for the required shares: “movies” this user has both R&W access to the shares. Additionally an NFS permission has been created for Kodi as a client. NFS rule as follows:
Hostname or IP: 192.168.1.100
Privilege: R/W
Squash: No mapping
Security: AUTH_SYS
Enable asynchronous = Yes
Allow users to access mounted subfolders = Yes
The folder structure for the share: “TV-Shows”, has two subfolders to get to the shows.
And the folder structure for the share: "Movies, also has two subfolders before the start of the movies.
Well, I don’t quite believe it, it’s all up and running & so much faster!!
Added a NFS user “osmc” and gave user root admin rights, it seems such a simple thing. ahah.
Thanks again for all your help & patience @fzinken!
Might be worth mentioning that when using a .smbcredentials file, it helps to keep the username/password characters to simple characters, avoiding ones such as ’ ’ (space), ‘@’, ‘#’ or ‘.’ characters (particularly in the username).
Well, just tried it now with a simple username/password combo and it still does not work with the .smbcrentials file. Here’s the details, using a Windows account called ‘osmc’, with password ‘osmcosmc’ -
chmod 600 made no difference on the existing file.
Yes, the file was (incorrectly) created in windows (as a .txt file & renamed) and written to the Vero4K using the SMB client add-on. (i.e. this was a Windows (CR LF) UTF-8 text file.)
Recreating it using the native nano editor solved the problem (i.e. this is now a UNIX(LF) UTF-8 text file)
Multiple newlines (LFs) after the password, when created using nano, had no effect and .smbcredentials was still usable.
Spaces in the username of the .smbcredentials file also don’t work. They cannot be forced by preceeding the space with the ‘\’ character (however this is possible when using them in the mount specification to autofs. )
fzinken - thanks for your help and patience, I’d recommend updating your ‘how to guide’ for autofs with these points.
Hope this thread is still alive. Returned to Vero 4K+ after a long hiatus. In setting up autofs with my Synology & QNAP NAS’es, I’m getting former to work, but not latter.
Followed instructions in the first post to mount SMB shares using autofs, and when I type in…
Set the SMB version too, it helped for me. Considering the share is made with SMB version 3:
on RPI with OSMC “-fstype=cifs,rw,vers=3.11”
on Vero4K+ last update “-fstype=cifs,rw,vers=3.0”
(3.11 is not working on vero4k, SMB client version I guess)
You can try the debug way too, it’s described in the wiki if I’m not wrong. You need 2 ssh sessions, the first starting “sudo automount -f -v -d” and the second to restart the systemD unit (autofs) or simply touching the share
