Repair failed, not enough repair blocks

Get help with all aspects of SABnzbd
Forum rules
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.
Post Reply
det427
Newbie
Newbie
Posts: 3
Joined: March 26th, 2016, 9:37 am

Repair failed, not enough repair blocks

Post by det427 » March 13th, 2018, 12:59 pm

I am using version 2.3.2
Windows 10 Pro
I use the check before download to save bandwidth; learned the hard way!
This was only an hour old.
I did the check first an Sab said it was OK.
When I downloaded it the error was:

Retry The.Guardians.2017.PROPER.1080p.BluRay.x264-SADPANDA Repair failed, not enough repair blocks (501 short)

I thought if Sab checks the nzb first this problem would not show up.

User avatar
sander
Release Testers
Release Testers
Posts: 6389
Joined: January 22nd, 2008, 2:22 pm

Re: Repair failed, not enough repair blocks

Post by sander » March 13th, 2018, 5:00 pm

So ... if you do check-before-download now again, what does SAB say ... ?

EDIT:

Ah, I tried that NZB:
first the check-before-download, which went OK.
then the acutal download, which whent wrong
So I can confirm your experience.

Look at the log file:

Code: Select all

[email protected]:~/.sabnzbd/logs$ cat sabnzbd.log | grep -A99999999999 2018-03-13  | grep missing
2018-03-13 23:48:00,408::INFO::[__init__:909] [sabnzbd.postproc.parring] /media/sander/BDEDrive/Downloads/incomplete/The.Guardians.2017.PROPER.1080p.BluRay.x264-SADPANDA/__ADMIN__/__verified__ missing
No nothing is missing in the check-before-download. So each message is there.

Then the download:

Code: Select all

[email protected]:~/.sabnzbd/logs$ cat sabnzbd.log | grep -A99999999999 2018-03-13  | grep damaged
Target: "g80ad7aab4fc4072230acd9f9c.part22.rar" - damaged. Found 49 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part23.rar" - damaged. Found 1 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part24.rar" - damaged. Found 3 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part25.rar" - damaged. Found 1 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part28.rar" - damaged. Found 60 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part27.rar" - damaged. Found 8 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part29.rar" - damaged. Found 15 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part30.rar" - damaged. Found 7 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part31.rar" - damaged. Found 25 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part32.rar" - damaged. Found 39 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part33.rar" - damaged. Found 62 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part34.rar" - damaged. Found 63 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part35.rar" - damaged. Found 63 of 64 data blocks.
Target: "g80ad7aab4fc4072230acd9f9c.part37.rar" - damaged. Found 63 of 64 data blocks.
15 file(s) exist but are damaged.
So the rar files are damaged. Possible causes:
1) all individual messages are there, but some them are fakes / empties, leading to incorrect rar files. Possibly due to DMCA, and replaced by fake messages
2) all individual messages are there, but the post was incorrect. Less likely I would say.

I think we need @safihre for this. I must say he's not a fan of check-before-download ... maybe the above is why?

@safihre: what do you think? If is 1), could SAB see that? For example based on size? Or based on contents of the message, for example all-zero's (so low entropy)?

User avatar
jcfp
Release Testers
Release Testers
Posts: 878
Joined: February 7th, 2008, 12:45 pm

Re: Repair failed, not enough repair blocks

Post by jcfp » March 14th, 2018, 3:58 am

sander wrote:
March 13th, 2018, 5:00 pm
If is 1), could SAB see that? For example based on size? Or based on contents of the message, for example all-zero's (so low entropy)?
Pre-check doesn't typically have access to any message content, see https://github.com/sabnzbd/sabnzbd/blob ... er.py#L389 ; STAT returns basically just a yes/no answer.

Post Reply