Help in fixing incomplete nzb from sanzb plz

[Mindrage]

Hi all i just switched over to sanzb from using grabit for years. Firstly let me say i love sanzb and i think its a great program. However im having issues with it.
Most of my downloads are incomplete ( pretty much every rar file is missing a few blocks each and i cant repair at all. I use nzb matrix for my nzbs, and while ive had bad files 99% have been repairable, ive just come home to 76gb of nzbs that have downloaded but are unrepairable. Does anyone know why ever rar would be incomplete in quickpar?

More importantly, is there a way i can fix these without redowmloading the whole nzb again?

ThNks in advane, and sorry for the bad typing, im using my iphone with fatty fingers

[shypike]

SABnzbd does support retries from the History list.
However, this will not attempt to get parts of files (which generally isn't useful).
The best thing is to hunt for additional par2 files on search engines.
Pay attention to completeness, look over the files listed by the search engine.

BTW: Grabit is not better than SABnzbd in this area. Grabit cannot improve an incomplete NZB.
You may have found the built-in search of Grabit more reliable.
That's what you pay for with Grabit, since Grabit is just a promotion tool for
their commercial search engine.

[Mindrage]

Na i meant i wasnt getting incomplete downloads with grabbit, i tested 2 nzbs with grabbit overnight and they downloaded fine, but they were incomplete with sabnzbd,

Either way, is there anyway to fix them? I have all the par files just theres too many blocks missing from the rar files to repair.

[shypike]

Did you use the exact same NZBs for Grabit and SABnzbd?
Did you use the same Usenet server?
If so, I would like to have the NZB files, because it does suggest a problem with SABnzbd.
Please email to bugs at sabnzbd.org and include the URL of this message too.

[zeflash]

Hi, I do see the same behavior, it's been going on since I switched from newsleecher to sabnzbd, and it's the only cloud in an otherwise perfectly empty sky

More often than not, when I get a failed download on sabnzbd and I open the backup nzb file in newsleecher, newsleecher produce a valid output.

From what I can see, sabnzbd only downloads the first par file, not the other ones and therefore is unable to repair, where newsleecher does download all of them.

I'll send the nzb to the bug email address.

[shypike]

Initially SABnzbd will download only the smallest par2 file.
When it fails to repair the download, it will download additional par2 files
until the job is repaired or there are no more par2 files in the NZB.
The method may fail if the poster used non-standard naming.

[shypike]

SABnzbd behaves OK with this NZB, the first repair fails after which
more par2 files are downloaded and then the repair is successful.
The log file you sent is empty, so I cannot see whether anything went wrong on your system.

BTW: did you ever click on "Retry" when a job fails. If so, what it the result?

[zeflash]

When I hit repair it seems to be downloading more but it then fails again with the same error. I haven't checked the log when it does that though. I'll look into it.
I'll send the original log again.

[pobox]

I always find out why a post has to be repaired, just out of curiosity.

[zeflash]

Well, most of the time it's missing articles, and most of the time the par2 repair volumes that are part of the nzb report are there for those missing articles.
What happens (to me) with sabnzbd is that it's not, as never, even after multiple retries, saving the additional volxx+xx files. Just the first one. Therefore the quickpar check fails, and the report can't be repaired.

[pobox]

Did you ever solve this problem? If articles are missing I would hunt them down.

[zeflash]

I've never solved my problems. Sabnzbd is just downloading the first par volumes, not the rest. I don't understand. I have to download the rest of the pars manually then run a manual repair everytime it happens (and it happens quite often)

[zeflash]

Initially SABnzbd will download only the smallest par2 file.
When it fails to repair the download, it will download additional par2 files
until the job is repaired or there are no more par2 files in the NZB.
The method may fail if the poster used non-standard naming.

Hate to bring this back again on the table, but on my end it's still not working.
Sickbeard grabs a NZB. Sabnzbd downloads the first par and all the rars, and it fails to repair. I reopen the same nzb, it stays in pause given it's already been downloaded, and I can see in the details that all the pars are still listed.
Then I unpause it, and right away when I look in the details which files are being downloaded, I can't see the other pars anymore, it's like sabnzbd just discarded them right on start.

Can someone tell me which switches I should set or not set to fix this? Isn't there really any way to just force sabnzbd to download all pars without trying to be too intelligent for its own good? I (yet) don't care about downloading some extra MB for nothing, provided I don't have to spend time to manually download, copy, par repair and extract each failed episodes.

[shypike]

Does it end in a situation where not all available par2 files are actually downloaded?
Don't look at the display, look in the job folder in the temporary download folder.

[zeflash]

It ends with just the first par2 volume downloaded along with the (incomplete) rars. Those have been moved by the sickbeard script. I haven't seen any job folder, where should I look?

In the post-processing settings I have this:

Ignore Samples: do not download
Enable Quick Check Skip par2: false
Enable Unrar: true
Enable Unzip: true
Enable Filejoin: true
Enable TS Joining: true
Enable Par Cleanup: false
Fail on yEnc CRC Errors: true
Post-Process Only Verified Jobs: false
Enable SFV-based checks: false
Check result of unpacking: true
Extra PAR2 Parameters: t0
Nice Parameters: empty
IONice Parameters: empty