Sonarr version (exact version): 2.0.0.5252
Mono version (if Sonarr is not running on Windows): 5.16.0
OS: Manjaro Linux(Arch Based)
Debug logs: https://pastebin.com/WMg0xqyh
Description of issue: Hi I have installed sonarr(radarr and jackett) recently. I am attempting to scan my collection, but hardly anything gets matched. Can someone point me in the right direction?
Could be severally reasons,
You will find in your log files what error you’re getting.
Most common mistakes not choosing the upper directory where under all your series are ordered.
Files that are bad renamed with to less info to get info from.
Series name, season, episode, source, resolution etc.
99% of the content has the original file name from respected groups. So that shouldn’t be an issue with some exceptions.
As for choosing the upper level directory, I have. This is a common mistake in torrenting. If the media is at
/media/drive-label/tv/some.series.s01.x264.bdrip-gRp/videos1-10.mkv then I select TV not some series.
I have looked at the logs and can’t seem to figure out what the issue is. That’s why I have posted here for assistance.
There should be in the logs a reason why it doesn’t find anything.
Could you perhaps post a link to your debug log.
But your torrent folder won’t work if I’m not mistaking.
Because there isn’t a show named “some.series.s01.x264.bdrip-gRp” but there is a show named “some series”
Also keep in mind Sonarr should point to your download directory.
Or do you want to use mass import ?
My debug logs are in the op. Have been all along.
I have multiple download directories and yes I’m trying to do mass import.
Now am I understanding that the base folder for the series should “read some series not some.series.x264.src-gRp” as I thought part of the purpose of sonarr was to strip the code and group info automatically when importing? I did manage to get a handful of shows to catalog but far from all. So why is it a factor on series a but not series b that follows the same name pattern.
Not sure I see why it would be a purpose of sonarr to strip code/group info, tbf. That said, I too think the matching mechanism in sonarr isn’t its strongest side, this works better in plex, for instance. As you said, path.with.periods.quality.groupname often won’t match, while path with spaces seems to work.
I’ve just “always” considered it how sonarr works and nothing that’s terribly hard to work around so I’ve just edited the show title whenever one comes up unmatched, and moved on. After all you generally don’t do it so often that it becomes particularly onerous, IMO.
It looks like you’re trying to add the unsorted folders to Sonarr as different series.
You should have one location for sorted content that is in Sonarr (each series gets it’s own folder) and another location where your download client puts unsorted files.
Currently Sonarr is trying to match each folder with a release name to a specific series which won’t work.
Sonarr doesn’t care about spaces vs periods, but this particular scenario isn’t one Sonarr supports.
If you’re on Team Sonar then you know so not gonna argue. But I ran into much the same behavior as @TechN9ne hence my reply. My tv series are all sitting in one root folder like so, /mnt/p1/tv with each series having one and only one folder under this, and with each season having its own folder within this folder again (so /mnt/p1/tv/name of series/sNN as an example.
And I shan’t say for certain that this is what happened every single time but any folder that had any other information than the name of the series trailing the series name (quality or group name) and/or name separated with periods rather than spaces, would not be identified correctly and I would have to edit the name for sonarr to find it.
I can dig up examples if wanted (for instance on some of the ended series that I’m not having sonarr monitoring currently), but it doesn’t bother me so no point to it for my part really…
Honestly, they shouldn’t be part of the folder name for a particular series, Sonarr does expect some level of cleanliness for the folders and isn’t meant to parse release names for series folders.
In some recent changes/tests it’ll handle a number of cases, including the year being added, articles moved to the end (Series Tiles, The`), tried with/without periods and it should be better than it was before, though wouldn’t be perfect (TVDB’s searching is a bit lackluster which is ultimately relied on).
Completely understood, hence why I never reacted when it did this for myself as well. It’s a very minor issue to help sonarr find the right series if you for whatever reason can’t/won’t rename the source directory, anyway.
So let me make sure I understand. More or less this is directory tree related. My structure like this won’t work:
Wrong:
Scanning: /media/tv/some-series/
/media/tv/some-series/ep1/ep1.mkv
/media/tv/some-series/ep2/ep2.mkv
Will not work. Instead it needs to be:
/media/tv/some-series/ep1.mkv
/media/tv/some-series/ep2.mkv
If that’s the case that’s no big deal. Some series did register so I will compare directory structures and see what I find.
Both will work.
If you selected /media/tv/some-series instead of /media/tv when adding the folder then you selected the wrong folder.
Once you select /media/tv you’ll be prompted to choose the series to add from there.
I made a typo above but what is the structure radarr will accept in terms of series, seasons, and episodes?
so does this work:
Scan:
/media/tv/
Structure:
/media/tv/series.name/
/media/tv/series.name/season#/
/media/tv/series.name/season#/episode#.mp4
Sonarr, not Radarr, but yes, that format should work just fine (made another tweak to handle series.name a bit better).
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.