Yes. I understand. do you have the docker container still? If you can get the Preferences.xml file from it, and re-create the shares using the same names as before, everything will be back automatically. PMS keeps the MachineID and ProcessedMachineId values are what we want.
I will go through the logs now… Thank you
No I don’t have the docker anymore . Just to be clear… This problem is still persist. When I restart plex now, I have this issue
You’re running with your PMS on a network share, aren’t you?
PMS doesn’t work over networking because File locking isn’t supported by default unless you expressly enable it
I have my media on my freenas and share them over nfs. Also the Settings for plex itself I have on my freenas and share it via nfs. How can I enable it?
NFS mounts require local_lock=posix as one of the mount options.
When you do this, you’ll have to perform a mount -v to confirm the FreeNAS supports the option and acknowledged it. (some NAS boxes don’t).
I have mount the directory within the fstab file. Where I have to do this option settings. Where I can find it. Do you know about?
Here is an example of mine…
moesern:/volume1/plexdb /home/plexdir nfs sec=sys,intr,local_lock=posix,rw,vers=4,auto 0 0
Notice I specifically state NFS version 4 (TCP). and Posix locking.
I will try it. Thanks a lot. Is there a way to check if this solves my issues or have I just to wait whats happening?
I need this for all my shares? Media and plex settings?
I have changed this to a Question for you. When things are stable and ok, ,you can click the appropriate “Yes” answer
@ChuckPA said:
I have changed this to a Question for you. When things are stable and ok, ,you can click the appropriate “Yes” answer
I have made the changes in my fstab and remount with mount -a. It seems it works, I have access to my files. Lets see whats happening. I really hope this will solve my issues. I will thank you very very much for your work 
You are VERY welcome.
If you can capture the Preferences from the Docker container, i will help you get it’s data as well.
I dont have the docker container anymore. It is no problem at all, but like I said before, plex seems to loose the setting ervery time i restart the ubuntu vm. When i start plex again by “service plexmediaserver restart” the settings are back
with the locking in place, you’ll be pleasantly surprised how well things work. Also, any layers between the VM and NAS also need file locking enabled
@ChuckPA said:
with the locking in place, you’ll be pleasantly surprised how well things work. Also, any layers between the VM and NAS also need file locking enabled
I will update all my nfs mountpoints with this locking. Perhaps this sould be insert in the how-to of install plex on ubuntu
It’s not really supported because there will be those who complain (whine) about it not being supported for Windows.
This is a feature of linux and NFS, and Linux isn’t for everyone. It takes a lot of keyboard dedication to use.
If you look at the top of the Linux forum, You’ll see where I do have a Linux Tips. I’ll think about putting something there…
I will probably put it up as an “unsupported but usable” tip. there is a much easier way already documented (puts PMS on the /home or other directory ) already which I do support.
@ChuckPA said:
It’s not really supported because there will be those who complain (whine) about it not being supported for Windows.This is a feature of linux and NFS, and Linux isn’t for everyone. It takes a lot of keyboard dedication to use.
If you look at the top of the Linux forum, You’ll see where I do have a
Linux Tips. I’ll think about putting something there…I will probably put it up as an “unsupported but usable” tip. there is a much easier way already documented (puts PMS on the
/homeor other directory ) already which I do support.
I have restarted the ubuntu vm and get the message protocoll not supportet. So I have deletet the “ver=4” of you command in the fstab. Aftert this I am able to do the “mount -a” Do you think this will be a problem?
Edit: I have to activate NfsV4 on Freenas. Now I have all the options in my fstab. I hope everything will work.
If I do: mount | grep Library
I get:
**192.168.1.220:/mnt/pool_system/docker/plex/config/Library on /var/lib/plexmedias erver/Library type nfs4 (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=2 55,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.200,lo cal_lock=none,addr=192.168.1.220)
**
Looks good I guess, or not?
You are NOT protected . There is no locking.
local_lock=none
You are getting NFS version 4 but your NAS vendor/ computer cannot negotiate posix locking.
You must resolve this first. If not, you need to use the alternative and use a /home/plexdir method to have more space. I have a created instructions for this as well
Ok, sad. I thought I have it solved. Here the Settings I can do on my Nas. Do you perhaps know some of these settings will help?
Your settings are correct. Do you see where rpc.statd and rpc.lockd are? The lock daemon lockd are of interest.
When you SSH into the NAS, do you see it lockd running as a process? If you do not, this is the problem… How to enable it. If it is running, it is not making itself available to NFS for use.
For these I can only suggest you look in the Freenas documentation/forums.
@ChuckPA said:
Your settings are correct. Do you see whererpc.statdandrpc.lockdare? The lock daemonlockdare of interest.When you SSH into the NAS, do you see it
lockdrunning as a process? If you do not, this is the problem… How to enable it. If it is running, it is not making itself available to NFS for use.For these I can only suggest you look in the Freenas documentation/forums.
Where do I find this things rpc.statd and rpc.lockd how can I check if the service is running or start it?
Sorry, but I really no Linux professional 
