SABnzbd Forums

Posted: **April 15th, 2011, 6:06 pm**

Version: 0.5.6
OS: CentOS 5.5 x86_64
Install-type: Python source
Skin: smpl
FW: None
IPV6: No
Reproducible: yes

When using certain NZBs, I can see sabnzbd mark the par2s as Waiting so it should go back and grab them if there's problems, but it will verify, find it's damaged, and then just quit rather than going back and grabbing the rest of the par2 files. I'm using multicore par2 if that makes a difference.

edit: and the relevant log entries:

Code: Select all

2011-04-15 17:20:10,034::INFO::[postproc:243] Starting PostProcessing on Item1 => Repair:True, Unpack:True, Delete:True, Script:sabToSickBeard.py
2011-04-15 17:20:10,034::INFO::[postproc:247] Par2 check starting on Item1
2011-04-15 17:20:10,035::INFO::[postproc:254] Running repair on set Item1
2011-04-15 17:20:10,041::INFO::[newsunpack:674] Scanning "/var/downloads/incomplete/Item1/Item1.vol000+
04.par2"
2011-04-15 17:20:17,903::INFO::[newsunpack:689] Par verify failed on /var/downloads/incomplete/Item1/Item1.vol000+04.par2!
2011-04-15 17:20:17,904::INFO::[postproc:271] Par2 check finished on Item1
2011-04-15 17:20:17,904::INFO::[misc:837] Creating directories: /var/downloads/complete/TV/Item1
2011-04-15 17:20:19,514::INFO::[postproc:470] Cleaning up Item1
2011-04-15 17:20:19,517::INFO::[postproc:134] Saving postproc queue
2011-04-15 17:20:19,518::INFO::[downloader:357] Post-processing finished, resuming download

Posted: **April 16th, 2011, 6:32 am**

It's possible that the par2 files do not follow the conventional naming pattern.
SABnzbd isn't very good at handling that (improvement for a future release).

Posted: **April 16th, 2011, 8:25 am**

shypike wrote: It's possible that the par2 files do not follow the conventional naming pattern.
SABnzbd isn't very good at handling that (improvement for a future release).

It seems like it does recognize it though as it marks them as 'Waiting', right? I'm imagining I went wrong in the par2 setup somewhere or I checked some option I've now forgot about...although other NZBs have repaired without a problem. Maybe they only required the already downloaded pars. Hmm this is confusing!

Posted: **April 16th, 2011, 2:57 pm**

SABnzbd will recognize par2 files alright, but it may not know to which file set they belong.
Without more details such as an actual NZB, there's not much I can say about this.
Please email one to bugs at sabnzbd.org referring to this post.

Posted: **April 19th, 2011, 10:30 am**

shypike wrote: SABnzbd will recognize par2 files alright, but it may not know to which file set they belong.
Without more details such as an actual NZB, there's not much I can say about this.
Please email one to bugs at sabnzbd.org referring to this post.

Sent, thanks!

Posted: **April 19th, 2011, 7:36 pm**

Received.
It will take a while to analyse, because currently I'm travelling.

Posted: **April 22nd, 2011, 3:12 pm**

This is a screwed up post.
If you run par2 manually on the files, it will give this message:

No details available for recoverable file number 1.
Recovery will not be possible.

That's what makes SABnzbd decide that it's useless to try any further recovery.

Even QuickPar cannot make heads or tails of it. Which usually means: abandon hope.

SABnzbd Forums

not downloading par2s even after failed verify

not downloading par2s even after failed verify

Re: not downloading par2s even after failed verify

Re: not downloading par2s even after failed verify

Re: not downloading par2s even after failed verify

Re: not downloading par2s even after failed verify

Re: not downloading par2s even after failed verify

Re: not downloading par2s even after failed verify