2025-03-06, 08:35 PM
Hi TheDreadPirate, thanks for your response.
The information about the /config is good to know. Since Jellyfin was on the NAS, the /config was already there, so I kept it there. I'll move it once I have the rest of it working.
There may be some confusion. I'm not having issues with read/write. Once Jellyfin can see the share, it is able to read/write. The problem is that it doesn't see the mounted directories until it is restarted.
I did try implementing the changes you mentioned. Unfortunately, adding noperm to the fstab and removing the UID and GID lines from the compose didn't change anything. Everything shows up as being owned by root:root now, but the behavior hasn't changed. I still have to manually restart the Jellyfin instance to get it recognize the shares.
As a follow up, I changed both the fstab and compose.yaml to use 1000:1000, which should be me, and while the shown owners of the files changed to my user id and group, no actual behavior changed.
Thanks
The information about the /config is good to know. Since Jellyfin was on the NAS, the /config was already there, so I kept it there. I'll move it once I have the rest of it working.
There may be some confusion. I'm not having issues with read/write. Once Jellyfin can see the share, it is able to read/write. The problem is that it doesn't see the mounted directories until it is restarted.
I did try implementing the changes you mentioned. Unfortunately, adding noperm to the fstab and removing the UID and GID lines from the compose didn't change anything. Everything shows up as being owned by root:root now, but the behavior hasn't changed. I still have to manually restart the Jellyfin instance to get it recognize the shares.
As a follow up, I changed both the fstab and compose.yaml to use 1000:1000, which should be me, and while the shown owners of the files changed to my user id and group, no actual behavior changed.
Thanks