Repair failed, not enough repair blocks

[downloadmonkey]

Hi there

First of all, awesome job with SABnzbd guys This thing is pretty awesome and my trusted Usenet client for many years

Unfortunately I've a lot of "Repair failed, not enough repair blocks" lately.

Today I manually fetched an NZB which failed on SABnzbd and fed it NZBVortex 3 on my Mac.
To my surprise it worked seamlessly. The file wasn't complete and even NZBVortex had to repair it, but it worked!

I already searched these forums a lot and I found some users with the same issues.
So to make sure it's SABnzbd and not a "ghost", I tried the following things:

• I've 3 Usenet providers (Astraweb, UsenetServer, ExtremeUsenet) and I manually switched through all providers (e.g. 3 separate downloads)
• I've disabled Enable Quick Check and enabled Download all par2 files
• I've tried the download via NZB Vortex in advance and after SABnzbd

Unfortunately SABnzbd wasn't able to download & repair my files in all cases. However, NZB Vortex always succeeded without any problems.
As I already wrote, it's always the same NZB file and the same Usenet server in SABnzbd and NZB Vortex.

I'm currently running on the develop git tree on commit 583c233bd282cfef3480948c69eef0055e1828bd.
SABnzbd runs on a Debian machine in a Docker container with Python 2.7.9.

Any things I can try to fix this or narrow down the issue?
Is it possible to switch back from develop to master?

Cheers
Domi

[shypike]

Please email the NZB to [email protected] (and add the URL) of this message.

I cannot advise you regarding "master" or "develop".
Currently "master" is way behind even the "0.7.x" branch.
There's no reason to assume that 0.7.20 would do better than 0.8.0 in this area.

[downloadmonkey]

Thanks. I've sent you the NZB.
I already tried to go back on master and then to the 0.8.0Beta3 tag. Nothing changed, same behaviour.

[downloadmonkey]

If you want to test / reproduce it yourself and you've a Docker host, here's my image:

https://hub.docker.com/r/dbarton/sabnzbd/

Here's the Dockerfile (installation) of SABnzbd:

https://github.com/domibarton/docker-sa ... Dockerfile

[shypike]

It will take a while before I get to this.

[shypike]

I downloaded your NZB with both 0.7.20 and 0.8.0Beta3.
Both succeeded, resulting in an oddly named MKV file.
There were malformed articles and repair was needed.
It could be that different parts are missing on different servers.
Sometimes par2 files are malformed in such a way that SABnzbd is thrown off-track.
Very rare, but it can happen.
Can you also email which Usenet provider(s) you're using?

[ALbino]

Shypike:

• I've 3 Usenet providers (Astraweb, UsenetServer, ExtremeUsenet) and I manually switched through all providers (e.g. 3 separate downloads)

[downloadmonkey]

I downloaded your NZB with both 0.7.20 and 0.8.0Beta3.
Both succeeded, resulting in an oddly named MKV file.
There were malformed articles and repair was needed.
It could be that different parts are missing on different servers.
Sometimes par2 files are malformed in such a way that SABnzbd is thrown off-track.
Very rare, but it can happen.
Can you also email which Usenet provider(s) you're using?

What's weird is that I've used the exactly same NZB and Usenet providers with NZBVortex where it worked, while SABnzbd had issues :/
It was the same NZB and it was the same Usenet provider (same host, port, credentials) and both clients (NZBVortex and SABnzbd) had to repair the downloaded files. However, NZBVortex succeeded while SABnzbd failed. I tried NZBVortex right in advance and directly after SABnzbd failed and it worked flawlessly both times. So I think this wasn't a "temporary issue" of the Usenet provider.

However, I tried it again a few minutes ago. Same NZB I've sent you per mail and same Usenet providers I mentioned before. Unfortunately SABnzbd failed again!

Don't know if there's something weird going on with my Docker container, but I think that should be fine. It's based on debian:8 (Jessie) and I've installed the following packages:

Code: Select all

git python-cheetah python-openssl unzip unrar par2

Have you tried it with a standalone SABnzbd or did you use my Docker image?

Anything else I can try or debug?

[shypike]

Downloading the item, I did see a report of "malformed" articles.
It is possible that SABnzbd handles these less well than other clients.
I will look into it.

If it is not too much to ask.
Can you download the NZB again with SABnzbd in Debug logging?
If it fails again, please email me the log files.
The following is the best way to work.
Stop SABnzbd.
Remove all files from ~/.sabznbd/logs
Start SABnzbd
Set logging mode to Debug on the Status page
Download
Zip all files in ~/.sabnzbd/logs
Email to [email protected]

[downloadmonkey]

Downloading the item, I did see a report of "malformed" articles.
It is possible that SABnzbd handles these less well than other clients.
I will look into it.

Thank you very much, I really appreciate it!

Email to [email protected]

Done!

[downloadmonkey]

Do you've any news? Since I moved from my old server to the new one (we're currently talk about), I've so many failed unpacks / failed repairs. :/

[shypike]

Please read this thread: https://forums.sabnzbd.org/viewtopic.ph ... r2#p103819
Some posts can be repaired by newer releases of par2cmdline and an extra parameter (-N).

[downloadmonkey]

Please read this thread: https://forums.sabnzbd.org/viewtopic.ph ... r2#p103819
Some posts can be repaired by newer releases of par2cmdline and an extra parameter (-N).

Thanks for your response!

I checked the forum today and saw the par2 flag after I wrote the last message (sorry, should have used to forum search first).
So I updated my Dockerfile @ https://github.com/domibarton/docker-sa ... ile#L7-L15 to compile and use the latest par2 sources instead of the stock Debian package. I've also added the '-N' switch to the settings.

The NZB I've sent you a few weeks ago will repair properly now with the new par2 tools. However, I still have a lot of other failed downloads. Unfortunately I didn't cross-check them with another Usenet client so I can't say it's SABnzbd's "fault" I try to check it as soon as possible and let you know.

Cheers