SABnzbd Forums

Hi

I have Couchpotato setup to work with Sabnzbd and send movies to my Plex monitored movie folder.

Now everything is working fine, CP finds the movie nzb, opens it in Sab, Sab downloads, CP moves the movie to the correct Plex folder and renames it.

However what also happens is that sabnzbd reports this...

"Unpacking failed, an expected file was not unpacked"

and the downloaded movie also remains in the "downloads/complete" folder as well, instead of being deleted.

Now it would appear something is happening with the moving of the files that means CP moves a file, but perhaps a duplicate is made? Here is how I have it setup.

CP downloads to Sab via the movies category. This works fine.

Sab downloads, file is tagged as a movie.

Movie category is setup like this...

Priority low, Processing +delete, Script none, Folder/Path "/Volumes/Mac Mini/Users/Danny/Downloads/Movies", Group Movies.

CP is set to monitor downloads in..
"/Users/Danny/Downloads/Movies/"
and move them to
"/Users/Danny/Music/iTunes/iTunes Media/Movies"

Naming is setup in CP as is "cleanup".

Sabs main folders are set as downloads/complete an downloads/incomplete as standard. The movie is renamed, moved by CP and available in Plex - but for some reason also appears in downloads/complete despite this folder being over ridden in the categories setting?

Why is this happening and why is Sab reporting an error.

Is it because I have professing set as +delete in Sab AS WELL as "cleanup" ticked in CP? Should it be one or the other? Is the error message being reported because Sab can't delete anything as its already been cleaned up and deleted by CP and if so, why is then also appearing in the downloads folder too?

I want to make sure the file only appears in my Plex media folder and thus isn't taking up twice the room on my disk and of course get rid of the error message in Sab.

Im running latest version of Sab on OSX.
Latest version of CP as well.

Thanks in advance.

realdannys wrote: "Unpacking failed, an expected file was not unpacked"

This is usually caused on Linux platform that have unclear file name encoding
settings for their file systems.
The unrar program assumes that the file system is UTF-8 compatible.
When the OS tells SABnzbd differently, then SABnzbd will assume that some files are missing.
If you cannot solve this by tweaking your OS, you can disable the file check option
in Config->Switches. It's called "Check result of unpacking".

thanks Shypike - I will try to do this.

I might add, this doesn't happen with TV shows or any other download - it only happens with downloads in the movies categories.

And its not just the error message I'm bothered about, but why the movie gets moved to my plex folder by CP but also then seems to get moved back into the "/downloads/complete" folder by Sabnzbd, which according to the category settings, its never supposed to go near this folder anyway.

I might add as well the file it thinks is missing is the movie.mkv file.

This is obviously because CouchPotato has already moved it to the plex movie folder?

In which case why is Sab keeping another copy of the full download in the "downloads/complete" folder when its been told to keep them in downloads/movies, unpack the movie and then let CP move the .mkv and delete whats left...

I'm not sure about your setup and I don't have a clue what CP is supposed to do in this case.
I can only say that if you are combining SABnzbd's Sort functions with CP, that's probably not a good idea.
After SABnzbd has done all its post-processing it will call the CP script (I suppose there is one) and the rest
is CP's responsibility. After that, SABnzbd won't do a thing with the files.

Of course I'm being an idiot here..

All the related rar, par etc files remain in "downloads/incomplete" (not complete, doh) because it unrars the movie and straight away CP movies it to my plex media directory.

When Sab tries to check this now to do the delete of the files it can't find the extracted.mkv anymore, thus fails part of the extraction process and leaves all the downloaded files in the incomplete directory for me to get rid of manually.

That of course makes much more sense than what I wrote before - but how do I stop this happening?

(CP doesn't have a script by the way and never has - it just scans the movie download file you tell it to and moves the file and does its renaming from there. All i want Sab to do is unrar/unzip the file and delete the rars/zips/assocaited files that are left...but as the mkv gets moved straight away it thinks that file is missing when it runs the check and fails extraction (or rather files cleanup) this must happen to every CouchPotato user, so I'm baffled as to why theres not a wiki or a forum post already about this...)

Did you disable the "Enable folder rename" feature?
I can imagine that CP ignores folder names starting with the __UNPACK__ prefix that's used during unpacking.

I'm having this exact same issue... Has anyone worked out how to fix it?

Files downloaded by couch potato always come back with "Unpacking failed, these file(s) are missing:;" in Sab...

There are several suggestions in this thread, have you tried any?

I've tried turning off the clean-up option in CP which hasn't made a difference.

Guess I can try disabling "Check result of unpacking" in Sab, but I'm not sure of what other side effects this could potentially have?

Or is the better option to remove the +delete option for movie category in Sab?

disabling "Check result of unpacking" fixes it, but will this have any other side effects in the processing of files once Sab is done?

xitation wrote:disabling "Check result of unpacking" fixes it, but will this have any other side effects in the processing of files once Sab is done?

The only side-effect is that SABnzbd won't notice that there are write problems, like when the disk is full.

shypike wrote:

xitation wrote:disabling "Check result of unpacking" fixes it, but will this have any other side effects in the processing of files once Sab is done?

The only side-effect is that SABnzbd won't notice that there are write problems, like when the disk is full.

Ah ok fair enough, thanks for the info.