The catalog on my indexor shows ~ 13 episodes where as sonarr only shows ~ 8. ![]() I ended up going to my nzb indexor and downloading the F ck that’s Delicious manually. Maybe the errors were from a previous attempt to grab these files? Maybe I screwed something up? I don’t know. ![]() Now on topic, I did notice those errors in the log, but the fileNames/filePaths don’t lie. I’ll be donating to sonarr Shortly after I post this. Which filesystem are you using for unRAID?įirst off, thanks for all the help markus101! I really do appreciate it. I don’t see how Sonarr would have imported them given the error and the logs don’t show that it does, but it’s only ~1 hr of logs. 18-1-26 10:22:11.8|Error|DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr: /data/Complete/tv/.2018.01.25.x264-TBS/ġ8-1-26 10:22:12.1|Error|DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr: /data/Downloads/Complete/.2018.01.25.Cecile.x264-TBS/ġ8-1-26 10:22:12.1|Error|DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr: /data/Downloads/Complete/.2018.01.25.WEB-DL.AAC2.0.H.264-monkee/ġ8-1-26 10:22:12.2|Error|DownloadedEpisodesImportService|Import failed, path does not exist or is not accessible by Sonarr: /data/Downloads/Complete/.2018.01.25.Cecile.x264-TBS/ The only rules to naming your container-paths is that if another contatiner is on the same network then it has to use the same container-path for the share so if Sonarr and Radarr both pull from a media folder then both containers need to share the same container-path name.According to the logs Sonarr either these folders don’t exist or the user running Sonarr doesn’t have permissions on them. (/mnt/user/"YOUR-DOWNLOAD-SHARE-NAME")_ (/downloads) (/mnt/user/"YOUR-MEDIA-SHARE-NAME")_ (/media) Usually the container-paths are always set up as /"name-of-path." Now your container is like its own light weight OS so it does'nt share the same pathing as your host system Your config path is the appdata, so you create a share on your array (or better yet cache drive) named "whatever-you-want." This share is what you will use for host path. You can name your shares whatever you want, the only important thing is that the host paths are linked to to the docker paths with the correct information.Ī standard template for Radarr has your ports, media path, download path, config, and backup path. Your issue is that your missing a foundational understanding on how docker containers work. I will watch it in a bit and report back! *Edit: Automod linked the guides I am using, but I missed the video. Sorry if these have been answered, i am having a heck of a time. Additionally this guide has additional path mapping that spaceinvader1 does not mention?Īdditionally when I am looking at a template, Sonarr for example how do I differentiate which host path is the container path vs the host path? It seems the templates dont differentiate host vs container. My concern is that this guide has the user create a "data" share as opposed to the "downloads" share spaceinvader1 suggests. I also located another guide that was create a week ago linked below. Are these still the go-to source for setting these containers up? ![]() I have watched spaceinaver1 videos but they seem to be from 2017-ish. I ahve recently gotten my unraid server built and while I am beginning to explore I am getting conflicting information on how to get the Sonarr, Radarr, and Plex apps up and running.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |