Vero 4k stuttering suddenly

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

something like this

osmc@osmc:~$ sudo systemctl stop autofs
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 +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/readynas/media/videos with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/readynas/media/videos
mounted direct on /mnt/dune/0e8c9ea8_f96d_4822_9c2a_7d66219e9baa/videos with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/dune/0e8c9ea8_f96d_4822_9c2a_7d66219e9baa/videos
mounted direct on /mnt/tng/4k with timeout 15, freq 4 seconds
do_mount_autofs_direct: mounted trigger /mnt/tng/4k
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 /-
handle_packet: type = 5
handle_packet_missing_direct: token 2, name /mnt/tng/4k, request pid 1876
attempting to mount entry /mnt/tng/4k
lookup_mount: lookup(file): looking up /mnt/tng/4k
lookup_mount: lookup(file): /mnt/tng/4k -> 192.168.178.15:/4k
parse_mount: parse(sun): expanded entry: 192.168.178.15:/4k
parse_mount: parse(sun): gathered options:
parse_mount: parse(sun): dequote("192.168.178.15:/4k") -> 192.168.178.15:/4k
parse_mount: parse(sun): core of entry: options=, loc=192.168.178.15:/4k
sun_mount: parse(sun): mounting root /mnt/tng/4k, mountpoint /mnt/tng/4k, what 192.168.178.15:/4k, fstype nfs, options (null)
mount_mount: mount(nfs): root=/mnt/tng/4k name=/mnt/tng/4k what=192.168.178.15:/4k, fstype=nfs, options=(null)
get_nfs_info: called with host 192.168.178.15(192.168.178.15) proto 6 version 0x30
st_expire: state 1 path /-
expire_proc: exp_proc = 4095730768 path /-
expire_cleanup: got thid 4095730768 path /- stat 0
expire_cleanup: sigchld: exp 4095730768 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
st_expire: state 1 path /-
expire_proc: exp_proc = 4095730768 path /-
expire_cleanup: got thid 4095730768 path /- stat 0
expire_cleanup: sigchld: exp 4095730768 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
get_nfs_info: called with host 192.168.178.15(192.168.178.15) proto 17 version 0x30
st_expire: state 1 path /-
expire_proc: exp_proc = 4095730768 path /-
expire_cleanup: got thid 4095730768 path /- stat 0
expire_cleanup: sigchld: exp 4095730768 finished, switching from 2 to 1
st_ready: st_ready(): state = 2 path /-
mount(nfs): no hosts available
dev_ioctl_send_fail: token = 2
failed to mount /mnt/tng/4k
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 = 4095730768 path /-
expire_cleanup: got thid 4095730768 path /- stat 0
expire_cleanup: sigchld: exp 4095730768 finished, switching from 5 to 7
st_shutdown: state 5 path /-
umount_multi: path /mnt/readynas/media/videos incl 0
set_direct_mount_catatonic: set /mnt/readynas/media/videos catatonic
umounted direct mount /mnt/readynas/media/videos
umount_multi: path /mnt/dune/0e8c9ea8_f96d_4822_9c2a_7d66219e9baa/videos incl 0
set_direct_mount_catatonic: set /mnt/dune/0e8c9ea8_f96d_4822_9c2a_7d66219e9baa/videos catatonic
umounted direct mount /mnt/dune/0e8c9ea8_f96d_4822_9c2a_7d66219e9baa/videos
umount_multi: path /mnt/tng/4k incl 0
set_direct_mount_catatonic: set /mnt/tng/4k catatonic
umounted direct mount /mnt/tng/4k
automount_path_to_fifo: fifo name /var/run/autofs.fifo--
shut down path /-
autofs stopped
osmc@osmc:~$
49

What is the output of:

showmount -e 192.168.178.15

EDIT: I just noticed that you are using 3 different IPs. Are all of these mounts on the same NAS?

When you stop automount from running and paste the output, I mean to paste it here, not back in the putty windows (thatā€™s the cause of all the errors)

50

clnt_create: RPC: Port mapper failure - Timed out

no it is a NAS , windows pc, and a DUNE

showmount

51

If itā€™s windows, then you have to use SMB. So for the mounts coming from windows switch autofs back to use cifs and try running the above test again. Is the windows system 192.168.178.15?

Letā€™s work on 1 mount at a time, so lets stick with getting the mount from that IP working, then we will move on to the next one.

52

lets forget the windows pc not important the dune and nas has most of the files 192.168.178.15 is windows i will try the nas ok

53

Ok, leave the NAS on NFS, and run the showmount command on itā€™s IP.

To help me understand your setup better, give me a list of IP -> system type.

54

Export list for 192.168.178.10:
/c/SUBS *
/c/Foto *
/c/media *
/c/backup *
on the media ar my video files

192.168.178.16 = Dune but i think that is using SMB but i already made that in putty , got an error with showmount -e 192.168.178.16

55

I donā€™t know anything about the DUNE, but a quick google shows that it should support NFS. Check the settings on it, maybe you have to enable it.

For the .10 server, change the autofs map to 192.168.178.10:/c/media

and that one should start working.

56

you are correct the 10 server is working , there is my 4k movie zo i can test if the problem is over i have to figure out the DUNE

this is the path in windows \192.168.178.16\0e8c9ea8_f96d_4822_9c2a_7d66219e9baa\Videos

here are my movies

57

bmillham thanks for all your help but still the movie is shit, stuttering black screens , if i play it on my NUC no problems so i think i will skip it for the momentā€¦:confused:

58

Thatā€™s the path that you used in your original source? Then change the map to match that:

/mnt/tng/4k fstype=cifs,rw,credentials=/home/osmc/.smbcredentials,iocharset=utf8,uid=osmc,gid=osmc ://192.168.178.15/0e8c9ea8_f96d_4822_9c2a_7d66219e9baa/Videos
59

Did you actually add the source in Kodi to use /mnt/readynas/media/videos

If you didnā€™t then you are not using the mount yet.

60

yes is did and first i could not see the files

then you told me to change this : For the .10 server, change the autofs map to 192.168.178.10:/c/media

and then is see the files in Kodi , still black screens stuttering

61

Post a new log when the stutter happens.