Server Version#: 1.21.0.3711
Player Version#: 1.24.0.1483-714cba36
Hello !
I have a PMS inside a docker container, the persistent data is a folder from a samba share.
I chain the way I add content to Plex with radarr and RuTorrent.
I had no problem before however since few weeks I add issues with some new content added which are UNAVAILABLE in red when I want to launch them.
I have checked the permissions on the movies it is 664 as you can see in the picture.
Also one thing quite surprising that I can’t explain, while I was trying to debug this doing the plex dance, clearing cache etc one recently added content was readable and then it became UNAVAILABLE for no obvious reason. The older content is still accessible.
I have attached my logs (File removed)
Any help would be much appreciated I’m a bit stuck, I have tried all I had.
Thank you in advance !
Debian is aggressive (arguably broken) launching processes before the adapters are ready and /etc/fstab processing is complete. ( /etc/fstab is supposed to complete first – that’s what the standard says)
Even with PMS set to launch after the network adapter is available,
it can get launched before network shares are launched (unless manually edited).
On fast CPUs, it’s possible for PMS to launch before network shares are mounted and get this result.
I have this same problem with NFS mounts on Ubuntu
My resolution is to setup a service to remount the network shares after the host is up.
[chuck@lizum ~.501]$ cat /etc/systemd/system/chuck-network.service
# Chuck's fix for broken Ubuntu mounts
[Unit]
Description=Mount network shares after system boot
After=network-online.target
[Install]
WantedBy=multi-user.target
[Service]
Type=oneshot
ExecStart=/bin/sh -c 'sleep 10 ; mount -a ; exit 0'
User=root
Group=root
[chuck@lizum ~.502]$
It waits 10 seconds then mounts.
You can change the conditions if you wish to fine tune it more.
This is more than enough time for me on an i7-8809g NUC8
Thank you it seems to have solved the problem !
My curiosity and lack of knowledge make me question how could a mount partially work ?
Since I had part of my library which was accessible and part which was not but they are on the same mount, it means that the host system remembers some mounting info for old good well mounted content ?
