SABnzbd Forums

Hey,

I'm new to usenet, to Sabnzbd, sickbeard and couchpotato. After years of trying to automate transmission-daemon, JDownload, filestube, rapidshare, etc on my server I'm simply amused right now.
I have been awake for some days straight playing with them. I would like you guys to confirm me some initial thoughts.

PAR2 Issues
1. Setting up Config / General / "Cleanup List" to anything that probably IS gonna be a part of what you download (like nfo, sfv, txt, etc) would likely cause the _FAILED_ error if they are removed before par2 check. Running par2verify tells you the files are missing and many times you wouldn't have enough par blocks to par2repair. So, can anyone confirm me if the extensions in the Cleanup list are excluded after or before the par2verify?
2. Setting up Config / Switches / "Ignore Samples" to anything other than "off" would work the same way. Par2verify will complain about missing files and you'll get the _FAILED_ error, correct?
3. As a workaround for issues 1 and 2, activating Config / Switches / "Enable Quick Check" is thought of as a way to work around _FAILED_ errors. But without par2 I could end up with a broken download being treated as a correct one, which is probably useless, right? In practical terms, why would I not want to par2verify the download?

RAR Issues
4. Manually running unrar (free / non-free, whatever), with no fancy cmdline params, no rar repairing, etc is 99.9% of the times enough to successfully decompress the _FAILED_ downloads that are stalled at the Complete-Downloads folder. Why can't Sabnzbd do it? Like, a "ok, par2 says this things is incomplete (missing file) but hey, lets try to decompress what we have anyway" switch. Is there any way to currently make it work like that?
5. $rename 's/_FAILED_//' * && unrar e -r * is, as it seems to me, not enough for Sabnzbd to ever try to finish post-processing (rename, move, etc) the files again, right? At this point is it ok to simply mv it manually to the definitive media folder? Or am I breaking the process by doing that?

Regards,
Effenberg

EDIT: 4 is probably meant to be accomplished by Config / Switches / "Post-Process Only Verified Jobs". Forget about it.

1: clean-up is done at the end

2: "ignore samples" can be setup if different ways. "don't download" only works if the samples are not part of the general PAR2 check.

3: QuickCheck is nothing more than a light implementation of par2-verification (done from data in memory).
When any issue is found (bad CRC or missing files), par2 will be run anyway.
It saves time when there are no missing parts.

5: Not sure what you mean. The next release will handle failed downloads differently, allowing retries and additional download.