I am still getting failed service load. My new directory is an SMB share mounted at /mnt/plex, and I have ensured all the files are owned by plex:plex. Here’s the error stack when I run systemctl status:
Nov 20 09:53:27 localhost.localdomain systemd[1]: plexmediaserver.service: Service RestartSec=5s expired, sch>
Nov 20 09:53:27 localhost.localdomain systemd[1]: plexmediaserver.service: Scheduled restart job, restart cou>
Nov 20 09:53:27 localhost.localdomain systemd[1]: Stopped Plex Media Server.
Nov 20 09:53:27 localhost.localdomain systemd[1]: plexmediaserver.service: Start request repeated too quickly.
Nov 20 09:53:27 localhost.localdomain systemd[1]: plexmediaserver.service: Failed with result ‘exit-code’.
Nov 20 09:53:27 localhost.localdomain systemd[1]: Failed to start Plex Media Server.
Even though the folder is mounted on a local mount point, with a permanent mount call in fstab?
I am trying to save space on the system drive, so I wanted to move it elsewhere than /home; my other option is to attach a second hard drive to the virtual machine, but I would essentially be doing the same thing (mounting it to /mnt/plex through fstab).
Or is it the protocol I’m mounting with that is the impediment?
The network layer takes over before the local block i/o file system driver does.
Everything from the mount-point down is as presented from the remote host.
You can lock the mount point but you cannot lock anything below it.
If you were using NFS, and both the client and server supported POSIX file locking, you can usually achieve success by asserting local_lock=posix however it must be NFS and must be Linux-Linux.
OK, thanks - it actually is a Linux-based NAS, and does support NFS side-by-side with CIFS. I’ll do a bit more testing and see what I can get done, but thank you for all the information (and for your patience with all the novices like me :)).
