I know this is a necro thread. But I am having this exact same issue. Half of my nzbs that are getting processed by sabnzbd are getting stuck as UNPACK_foldername in the complete downloads folder. Result is sonarr never imports them or processes them. I have to manually drag them over or manually import them myself.
All the folders are on the main OS drive. Running Windows.
Your issue sounds like its the opposite of the other thread.
Sonarr will automatically strip the _UNPACK portion of the folder name when parsing it, but it also won’t ever import before SAB finishes unpacking if you’re using Completed Download Handling, it could if you’re using Drone Factory for importing, which is not recommended in any scenario.
When the release isn’t imported, what do the logs show, specifically debug logs?
This looks like a problem on SAB’s end, its telling Sonarr to look in a specific location, but the folder is actually in another (not yet renamed), if SAB failed to rename the directory and told Sonarr to use the UNPACK folder, Sonarr wouldn’t have any problems doing so.
The cause is a bit out of SAB’s control because Windows is pretty aggressive with locking files/folders which prevents the rename from succeeding, but my opinion is SAB shouldn’t report the path to be a specific path if the rename fails and its still under a different path, this should be reported to SAB so they can look into it, but make sure you’re on the latest release first (it might have already been fixed).
You can work around the issue by having SAB extract directly into the properly named folders, which I believe is the Enable folder rename switch, which has this description "Use temporary names during post processing. Disable when your system doesn't handle that properly." - I wouldn’t doubt that the second sentence is directed at Windows users.
PS, please edit your posts instead of double posting.
Yes, but SAB maybe fails to rename the folder because Sonarr is hugging it!? I had this issue just now myself. Had to manually rename/remove UNPACK from the folder name.
This is so easy fixed so why not do it? Even if it is something Else thats casing SAB from renaming. Making a rule for Sonarr to workaround this could not be more simple thats all I’m saying.
Sonarr doesn’t even touch it until SAB says its finished processing it, even SAB’s settings warn that its not possible. Sonarr intentionally ignores those folders to avoid importing something early (mainly from the Drone Factory days).
but what your saying is that SAB tells the client its done processing when its really not? what happens if I disable “Enable folder rename” wouldn’t SAB just inform the client even sooner that its done?
BTW, is this the reason you don’t support .rar files?
No, in this case SAB fails to rename the folder and reports that its done. If you disable Enable folder rename SAB won’t prefex the folder name with _UNPACK and won’t have to rename it, but while its unpacking it will still report on the API that its unpacking it.
Originally we only supported usenet, which has clients that unpack after completion so we had no need for RAR support (unrarring), if we add support for RARs it will be to unRAR, not keep in RAR files (regardless of media players being able to play it its not worth the complication to support that).