Please Check that file exists and necessary drive is mounted / transcoder stopped due to an error

Plex Media Server Remote Access
, ,
1

Server Version#: 1.18.9.2578
Player Version#: Apple TV 2.16 and Google Chrome 4.22.3

Okay so had an issue this weekend playing any of my media on my Plex server. Friday I updated both the Ubuntu headless server as well as the Plex software running on it.

Last night I tried to play a move on my Apple TV and got the transcoder error listed in the subject line. This morning I had a buddy try to play something remotely and he received the “check that the file exists error”. I tried to play the movie locally to the Plex and received the same error. I use and NFS connector between the plex and the Synology so the permissions on the files are inherited.

I did solve the first problem of the file not existing error. I consoled into the Plex server and ran a “sudo mount -a” to verify I wasn’t getting a drive mount error. Then I went to the library in the Plex server and verified the file path. Re-mapped the file, Plex re-scanned the library and it fixed the issue.

I will update if it also fixed the error I am receiving on my Apple TV.

2

I am running into issues where Ubuntu doesn’t like to automount NFS on system reboot. It’s become so bad that I created a systemd service to do it.

I recently moved from Fedora to Ubuntu. If I may rant a bit? Ubuntu is primitive and buggy as heck. I’d rather deal with the bleeding edge in Fedora than old broken crap in Ubuntu.

3

ChuckPa, my initial Plex deployment on Linux was a CentOS, which has all the same commands as Fedora. Unfortunately I let it sit waiting on my NAS drives to come in so I could stand up my Synology. When I came back around to it, I had forgotten the passwords, and the buddy that was helping me with the CentOS commands wasn’t available. I found a bunch of support for Ubuntu (I’m a linux noob so…) so I blew my CentOS VM away and deployed an Ubuntu.

I also stood up a system service and that part has survived the Ubuntu and Plex update. I followed a lot of the steps here: https://askubuntu.com/questions/345087/how-do-i-add-a-network-drive-to-plex.

But when it came to setting up the mount I used a different command to do the NFS connection.

sudo vi /etc/fstab

In the /etc/fstab I added the below line.

{synology IP address}:/volume1/Storage/media /media/Plex nfs defaults 0 0

Followed that up with a:

sudo mount -a

So far after a few months and several updates, I’ve had no problems.

4

If you want to have a tighter integration (which I need for my work here),

  1. I created users on the syno
  2. I edited /etc/passwd for UID/GID matching (the new values didn’t interfere wtih syno)
  3. I added sec=sys to my mount command. “sec=sys” tells NFS that the local host will handle the security and the remote server (Syno) need not be concerned.

Here’s one of my NFS mount lines, with all the trimmings.

# movies
vienna:/movies    /vie/movies     nfs sec=sys,intr,rw,vers=4,timeo=15,rsize=1048576,wsize=1048576,auto,async,nofail,bg 0 0
vienna:/movies2   /vie/movies2    nfs sec=sys,intr,rw,vers=4,timeo=15,rsize=1048576,wsize=1048576,auto,async,nofail,bg 0 0

sec=sys - The local host (my workstation) handles the security. Syno doesn’t need concern itself.
intr - interruptable ( i don’t have to wait for it to time out)
vers=4 - minimally use NFS v4
timeo=15 - if I don’t get a reply from the Syno in 15ms, something is wrong. (most replies are sub-millisecond.)
rsize=1048576 = read request block size of 1 MB (performance)
wsize=1048576 = write request bloc size of 1 MB (performance)
auto - Automatically mount at system startup (where ubuntu fails)
async - allow I/O to be asynchronous. I send the write request but don’t have to wait for the disk buffers to flush before the workstation is allowed to continue.
nofail - Allows the host to skip the mount, without failing, if the Syno doesn’t reply in time
bg - Put the mount request in the background to complete if the first mount requests times out.

You’ll probably want to preface the mount options with defaults.
Some distros want that.

5

This topic was automatically closed after 90 days. New replies are no longer allowed.