Synology NAS share not allowing Sonarr access

Sonarr version (exact version):
Mono version (if Sonarr is not running on Windows):
OS: Docker (CentOS8)
Debug logs: 2021-07-21 20:27:38.4|Error|DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr: /volume1/downloads/complete/media.mkv. Ensure the path exists and the user running Sonarr has the correct permissions to access this file/folder
Description of issue: Sonarr not importing new downloads from completed folder

Hi All,

I am currently running Sonarr in Docker on CentOS8 and all of my media is stored on a Synology NAS.

I can add new series’ to Sonarr and my download client (SABnzbd also on the Synology NAS) goes off and downloads it and moves it to the completed folder but Sonarr is then unable to access this folder to detect that its completed.
As far as I know all of my Synology privileges should be okay as I am allowing everything including guests full access.

As Sonarr is running in Docker, I am getting myself confused with what access I should be allowing to what system.

My system looks like this, these are my mounts in CentOS:

//                5.5T   18G  5.4T   1% /mnt/data
//  5.5T   18G  5.4T   1% /mnt/downloads

And this is my Docker container which match with the above mounts:

    container_name: sonarr
      - PUID=0
      - PGID=0
      - TZ=Europe/London
      - /etc/sonarr:/config
      - /mnt/data:/data
        # - /mnt/TVShows:/TV
      - /mnt/downloads:/downloads
      - 8989:8989
    restart: unless-stopped

If I browse to the completed folder through my Mac or CentOS I can see all of the files sitting there waiting.

Is there anyone that could suggest where I can start with this? I’m not sure if its a Synology problem, Sonar or SABnzbd.
Thanks in advance!

At first sight I think you’ll need a remote path mapping to translate /volume1/… to /downloads

Would that be at the OS level or in the Docker config?
Really getting myself confused.

/volume1/… is the Synology location. I cannot actually connect to that from anywhere but the NAS. I have to use //… connecting to it from anything else.

Neither :wink:
It’s a setting in sonarr’s settings.

Your download client reports /volume1/some/path for sonarr to pick up the files. Obviously this path doesn’t exist in your sonarr container, so sonarr tells you the path doesn’t exist or can’t be accessed.

Remote path mapping would “translate” the non-existing path (from sonarr’s point of view) into a path that exists inside the container, e.g. /data/some/path…

(You may also want to look into changing your paths so you only have a single mount both in your host as well as (and especially) inside the docker container. Right now sonarr will always perform a slow copy from one mount to the other, while you could have an instant move of completed files.)

1 Like

Thank you so much!

I flattened out my Synology folders a bit and made the Plex and Downloads share under ‘data’.
I then mounted just one mount at OS level for this and my Docker config now only has data and config paths specified. Seems to have done the trick!

Thank you so much!

1 Like