Comment on Incorrect permissions on my .arr stack
zer0squar3d@lemmy.dbzer0.com 3 months ago
Can you provide your /etc/fstab (I assume you are automounting) on the *arrs machine?
Comment on Incorrect permissions on my .arr stack
zer0squar3d@lemmy.dbzer0.com 3 months ago
Can you provide your /etc/fstab (I assume you are automounting) on the *arrs machine?
MrQuallzin@lemmy.world 3 months ago
The following was added to my fstab
//192.168.86.181/TrixieTV /home/brobot/Storage/Completed/TV cifs credentials=/home/brobot/.smb 0 0 //192.168.86.181/TrixieMovies /home/brobot/Storage/Completed/Movies cifs credentials=/home/brobot/.smb 0 0The credentials are using a new user ‘moose’ that owns the folders and has full control
user=moose password=3141Voroxpete@sh.itjust.works 3 months ago
OK, so right now you’re mounting the remote shares as user moose, but then you tried to chown those folders to user $USER. In case you don’t know this, the $ sign indicates a variable; the command is actually subbing in the name of the user who ran the command.
Now the question here is, what user is radarr / sonarr running under? If you’re running them directly on your machine without docker, that’s probably being set by a systemd task that runs the programs in startup.
You need to make sure that that user has the ability to write to those media folders. The simplest way to do this would probably be to edit the systemd units to run the arr programs as moose, since that’s apparently an unprivileged user you created just for mounting the shares.