I use this option because there have been failed downloads after 16GB already downloaded, but it is causing the software to download nothing for days at a time. The downloads will just sit at checking... without starting any downloads for well over 12 hours for even normal downloads. I have 8 (yes, eight) different Usenet servers setup to download from US, EU, JP, Korea, Russia, etc so there should be no problem with it. I can also disable the option, blast the queue completely (they sit at checking... after restart, queue rebuild etc, I can't get them out of this mode any way except removing the download from the queue and starting it again), and download everything successfully without any problems.
Is this option broken or is this behavior expected?
Check before download broken in 0.7.3 on 10.8 Mountain Lion?
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: Check before download broken in 0.7.3 on 10.8 Mountain L
There is a problem in 0.7.4 and 0.7.4RC1 in that these forget to scan for extra par2-files during the pre-check.
The results is that any post with missing articles will be rejected and sent to History
because if will not reach the required 100.2% for damaged posts.
I'm not sure if this relates to your situation, because I find it rather hard to follow.
But I bet it is anyway.
The work-around is to disable pre-check for a few days until 0.7.4RC2 comes out
or set the limit in Config->Special to 100%.
The latter will benefit posts without errors, you still need to "retry" other ones.
The results is that any post with missing articles will be rejected and sent to History
because if will not reach the required 100.2% for damaged posts.
I'm not sure if this relates to your situation, because I find it rather hard to follow.
But I bet it is anyway.
The work-around is to disable pre-check for a few days until 0.7.4RC2 comes out
or set the limit in Config->Special to 100%.
The latter will benefit posts without errors, you still need to "retry" other ones.