Hello fellow self-hosters,

I’m fairly new to hosting my own services and have been learning as I go, but have run into an issue and am not sure where to look for answers. Hoping you all can help a confused soul out.

Up until now, I’ve been running the .arr services (Sonarr, Radarr, Overseerr, etc.) on my Windows machine with minimal issue, but I’ve been working on setting up a separate Debian machine to get it off my main PC.

I’m following this guide to get everything setup, and at this point I have all my services setup and running, but I can’t seem to get Radarr and Sonarr to work correctly. My indexers work, Radarr will grab the wanted file and Deluge will download it, but when the download finishes it just stays in limbo; Radarr is unable to import it into the library due to invalid permissions (It doesn’t have Write permissions).

I’ve done sudo chown -R $USER:$USER /path/to/ROOT/directory and sudo chown -R $USER:$USER /path/to/HDDSTORAGE/directory as the guide instructs under ‘Folder Structure’ (of course replacing the paths with my actual paths), but to no avail.

Where I think the problem is is my actual Media Library. All the services are running on their own laptop, but my 10TB HDD is still in my main Windows PC. Until I build a new rig specifically for the server, I can’t put the HDD into the laptop. In Windows, the TV and Movie folders are network shared and I have them mounted on my server in the respective locations where Radarr and Sonarr should be looking. At this point, the .arr services can definitely read the mounted directories, but can’t make new ones for new shows and movies.

  • VoroxpeteEnglish
    3·
    4 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.