Am I even close…? Thanks, again, for your help. I did place an order for a new 5-port gig Ethernet switch today that’ll be here tomorrow. Figure I may as well take this opportunity to upgrade the network a bit.
What it needs to be is dictated by how you choose to configure your system mount. If your system mount point is attaching nfs://192.168.50.243/mnt/media to /mnt/media then…
Your Kodi library currently has everything stored as nfs://<server><file path> and we want to instead go to <mount point><file path> so you just need to find where in these file paths the two don’t jive and make the substitution there.
is the current path setting in Kodi (on the Vero) for my “shows” video source. My RPi is at 192.168.50.243. On the RPi, fstab has /mnt/media set up thusly:
It doesn’t matter how it is configured on your RPi that your serving the files from. Step one is to make a system mount on the Vero as Jim posted a link to above. In this process you chose what your mounting from your source and where your mounting it to. Once you have a working mount point on your Vero then in order to actually use it there is two options. One option is to completely dump your existing library and sources (and optimally also delete your thumbnails folder) and then setup your library from scratch using new sources pointing to the system mount you created. The other which is in discussion here you leave everything in Kodi as is and just tell Kodi to redirect to the new path. Kodi will do this completely transparently and everything will work inside Kodi as if nothing had changed. You continue to use Kodi nfs paths in the UI. If you configured a new source that pointed directly to a mount point in the future then that is fine as well as the path substitution wouldn’t affect it.
Your overthinking it. Look at my response a couple posts up and just use my first example. You don’t need multiple mount points or any complications. You videos are all under the “media” folder on your share. The paths your using in Kodi now are pulling from a share titled “mnt”. As such if you make a mount titled “media” and locate it in /mnt what is located at nfs://192.168.50.243/mnt/media will then also be located at /mnt/media which in my mind is logical and therefore easiest to deal with.
I still need to modify advancedsettings and can’t just go into my Kodi video source settings at this point and put /mnt/media/shows for my shows source?
Does not appear to have, no. iperf3 output still the same. I went to reboot Kodi via the settings menu in the app, and after the reboot, my files wouldn’t play (“missing”) until I ran sudo systemctl start autofs on the osmc cli.
iperf is testing raw performance between two clients. It is not interacting with your files, mount, or Kodi. The performance of the network in Kodi should have improved though.
I don’t know why it did that but you will probably find a working solution in this post or following that thread a bit farther down…
sudo systemctl enable autofs && reboot looks to have worked. I was playing a test file prior to running that, and I stopped it prior to running the command. When OSMC came back up, I tried to resume that file and got a playback error. Navigated out to the main menu and tried a different file, which worked, so went back to my original file, resumed it, and it, too ran OK from where I’d stopped.
The file I’m testing with is H.265 4K DOLBY-HD and is running without pause or stutter so far (~12 minutes in). I also tried a file that had paused before (H.265 4K DTS-MA), and it’s also playing without stutter so far. Ian Holm has never looked so scary.
New Ethernet switch comes today, so I’ll throw it into the mix and just keep an eye on things. @JimKnopf and @darwindesign , I really can’t thank you enough for your patience and expert assistance. I really, really appreciate your time.
