Just occasionally, sab will check the pars, confirm the set is ok, delete them, and then at the unpack stage return an error of 'no post-processing because of failed verification'. Extracting the rar set in 7zip will then go without any problems.
What could be causing this?
par check problem
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: par check problem
Carefully check the error messages.
Some NZB file contain files that do not belong to the actual download.
Say a spurious par2 file. In that case the file set belonging to that par2 file will fail,
hence SABnzbd will not do post-processing because one set failed.
Some NZB file contain files that do not belong to the actual download.
Say a spurious par2 file. In that case the file set belonging to that par2 file will fail,
hence SABnzbd will not do post-processing because one set failed.
Re: par check problem
It seems to be tripping up on the samples. Even if it was finding an error with the sample (or the par2 associated with the sample), I wouldn't have thought that would stop Sab processing the main par and rars as it usually can deal with multiple rar/par sets easily. It's also strange that it's showing the deleted pars together in the failed one (4 deleted, instead of 2 x 2 deleted).
Last edited by c0ld on November 16th, 2009, 8:23 am, edited 1 time in total.
Re: par check problem
One of the options in Config->Switches allow you to disable the "safe postprocessing" feature.
Re: par check problem
Ok, thanks. I'm sure that will be a decent workaround, but it seems to me there's an underlying bug somewhere. I've downloaded plenty of collections with multiple par/rar sets in the past and I've not noticed Sab stopping all rar processing because of single failed par check. Seems odd.
Re: par check problem
This is not a recent feature.
If the par2 sets are complete, there's no problem.
If the par2 sets are complete, there's no problem.