
So once the mover script has run, the /mnt. Say you have a file /mnt/cache/Downloads/1.txt, it also exists as /mnt/user/Downloads/1.txt BUT, /mnt/disk1/Downloads/1.txt, which is visible in the user path, will NOT be visible in the cache path. Typically with my setup Sonarr or Radarr will continue looking in the path mapped folder until the files are actually imported. Looks like for some reason sonarr doesnt see your downloaded file. Once the rsync eventually takes places, Lidarr doesn't do anything as part of its refresh monitored downloads task - it seems to think the import worked. The log message is correct - the path doesn't exist - yet! However the status isn't, the files never were imported.
#Sonarr remote path download#
Same setup works well in Sonarr and RadarrĪs soon as a file completes downloading in the client - Lidarr marks it as Download complete and successfully imported, whilst at the same time leaving this log message: Import failed, path does not exist or is not accessible by Lidarr. the common /downloads volume mapping is what allows sonarr to see where transmission (or sab in your case) has put the completed file. files aren't available in the path mapped dir until this sync/move takes place Once all files are downloaded they are moved into the path mapped dir Rsync script syncs remote client to a temp local directory If you have Sonarr in Docker and the Download Client in non-Docker (or vice versa) or have the programs on different servers then you may need a remote path map.

This is definitely something worth looking into!
