Another Not Enough Blocks question. I read the FAQ.

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
datalogger
Newbie
Newbie
Posts: 4
Joined: November 21st, 2015, 5:13 pm

Another Not Enough Blocks question. I read the FAQ.

Post by datalogger »

I'm trying to get SABnzbd Version: 0.7.20 to work properly on my seedbox, but having a problem.

I can successfully download/verify some Multi-Rar files, but many fail with the message "Repair Failed, Not Enough Repair Blocks, xxxx Short"
I understand what the message is telling me, that there is too much missing from the RARs and it can't reconstruct them using the PAR2's

The only problem is, this isn't true.

Using the same exact Usenet Account and the same exact .NZB file, I can download the same RAR's and PAR's onto my local PC, run QuickPAR on them and it successfully rebuilds them 100% of the time.

I looked in the SABnzbd "incomplete" folder and I see the same RARs and PAR2s as I have on my PC and they are the same size. (Before the repair attempt)

Reading the FAQs tells me it must be the
"The post has an unusual naming convention and SABnzbd doesn't understand the relation between RAR files and PAR2 files. Manual repair is the only solution (Windows users can use QuickPar)."
But isn't there someway to get SABnzbd to understand the names same as QuickPAR can?
It defeats the purpose of using SABnzbd on a seedbox if the user has to download the files to their local PC to PAR2 repair them then send them back using an FTP server...

(Not the problem - see messages below)

The file list below looks pretty standard to me

Code: Select all

VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.par2
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part1.rar
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part2.rar
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part3.rar
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part4.rar
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part5.rar
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol000+01.par2
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol001+02.par2
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol003+04.par2
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol007+08.par2
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol015+16.par2
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol031+32.par2
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol063+64.par2
VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol127+73.par2

Here is what I have selected in the Post Processing Parameters:

Code: Select all

   Ignore Samples (off)
   Enable Quick Check
X  Enable Unrar
X  Enable Unzip
   Enable Filejoin
   Enable TS Joining
X  Enable Par Cleanup
X  Fail on yEnc CRC Errors
X  Post-Process Only Verified Jobs
X  Enable SFV-based checks
X  Check result of unpacking
   Enable MultiCore Par2
   Extra PAR2 Parameters (none)
   Nice Parameters (none)
   IONice Parameters (none)
Last edited by datalogger on November 22nd, 2015, 10:17 pm, edited 1 time in total.
datalogger
Newbie
Newbie
Posts: 4
Joined: November 21st, 2015, 5:13 pm

Re: Another Not Enough Blocks question. I read the FAQ.

Post by datalogger »

It has to be something with the settings....

I just tested one of the same .NZB files on one of my other seedboxes and it works fine.

Same .NZB file
Same Usenet host
Same Usenet account

One installation of SABnzbd 0.7.20 repairs the files 100% (bytesized-hosting)
The other installation tells me "Not Enough Repair Blocks (1015 Short)" (Feralhosting)

I tried this 3 times and get the same results.
What am I looking for in the settings?
I looked as best I can and they look the same, but I must be missing something....



Follow-Up
It's not anything in the sabnzbd.ini file, I cloned the working one to the bad one and it still does the same thing.

Could something like this be caused by the seedbox host?
The two I'm comparing now are Feralhosting (Fails) and bytesized-hosting (Works)
datalogger
Newbie
Newbie
Posts: 4
Joined: November 21st, 2015, 5:13 pm

Re: Another Not Enough Blocks question. I read the FAQ.

Post by datalogger »

OK, I realize that I'm talking to myself here, but this information would have saved me a ton of time if I found it, so maybe it will be of use to others someday.

What is causing the "Repair Failed, Not Enough Repair Blocks, xxxx Short" in my case, and most likely for other users of Feralhosting, is Feralhosting's Servers.

The root cause of the problem is, Feralhosting's servers are not downloading the same amount of data as the other Seedbox houses do.

Here's the proof.
Same exact .NZB file
Same exact Usenet Server
Same exact Usenet Account
=Fail on Feralhosting
=Pass on other Seedbox Servers

From bytesized-hosting (Repair is possible)

Code: Select all

itsme@luna:~/sabnzbd/complete/VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part1.rar$ par2 r VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.par2

par2cmdline version 0.4, Copyright (C) 2003 Peter Brian Clements.
par2cmdline comes with ABSOLUTELY NO WARRANTY.

This is free software, and you are welcome to redistribute it and/or modify
it under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version. See COPYING for details.

Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.par2".
Loaded 12 new packets
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol001+02.par2".
Loaded 2 new packets including 2 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol007+08.par2".
Loaded 8 new packets including 8 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol127+73.par2".
Loaded 73 new packets including 73 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol003+04.par2".
Loaded 4 new packets including 4 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol063+64.par2".
Loaded 64 new packets including 64 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol015+16.par2".
Loaded 16 new packets including 16 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol031+32.par2".
Loaded 32 new packets including 32 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol000+01.par2".
Loaded 1 new packets including 1 recovery blocks

There are 5 recoverable files and 0 other files.
The block size used was 2437684 bytes.
There are a total of 2001 data blocks.
The total size of the data files is 4869268150 bytes.

Verifying source files:

Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part1.rar" - damaged. Found 425 of 431 data blocks.
Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part2.rar" - damaged. Found 429 of 431 data blocks.
Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part3.rar" - damaged. Found 427 of 431 data blocks.
Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part4.rar" - damaged. Found 424 of 431 data blocks.
Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part5.rar" - found.

Scanning extra files:


Repair is required.
4 file(s) exist but are damaged.
1 file(s) are ok.
You have 1982 out of 2001 data blocks available.
You have 200 recovery blocks available.
Repair is possible.
You have an excess of 181 recovery blocks.
19 recovery blocks will be used to repair.

Computing Reed Solomon matrix.
Constructing: done.
Solving: done.
From Feralhosting (Repair is NOT possible)

Code: Select all

[cacus ~/Downloads/complete/Rodea_The_Sky_Soldier_PAL_MULTi4_Wii-PUSSYCAT] par2 r VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.par2
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.par2".
Loaded 12 new packets
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol127+73.par2".
Loaded 73 new packets including 73 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol003+04.par2".
Loaded 3 new packets including 3 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol001+02.par2".
Loaded 1 new packets including 1 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol007+08.par2".
Loaded 8 new packets including 8 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol000+01.par2".
Loaded 1 new packets including 1 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol063+64.par2".
Loaded 63 new packets including 63 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol031+32.par2".
Loaded 32 new packets including 32 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.vol015+16.par2".
Loaded 16 new packets including 16 recovery blocks
Loading "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.par2".
No new packets found

There are 5 recoverable files and 0 other files.
The block size used was 2437684 bytes.
There are a total of 2001 data blocks.
The total size of the data files is 4869268150 bytes.

Verifying source files:

Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part1.rar" - damaged. Found 108 of 431 data blocks.
Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part2.rar" - damaged. Found 296 of 431 data blocks.
Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part3.rar" - damaged. Found 16 of 431 data blocks.
Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part4.rar" - damaged. Found 89 of 431 data blocks.
Target: "VoJCJWCJ4ivzN0GIPkaFpUSzE36U01.part5.rar" - found.

Scanning extra files:


Repair is required.
4 file(s) exist but are damaged.
1 file(s) are ok.
You have 786 out of 2001 data blocks available.
You have 197 recovery blocks available.
Repair is not possible.
You need 1018 more recovery blocks to be able to repair.

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

Re: Another Not Enough Blocks question. I read the FAQ.

Post by sander »

So ... Feralhosting is not a good choice for newsgroup downloading?

What you describe: how is this possible? Does Feralhosting inject faulty bytes into the stuff you download? Or does the newsserver (which one(s) are you using) give back different results?
datalogger
Newbie
Newbie
Posts: 4
Joined: November 21st, 2015, 5:13 pm

Re: Another Not Enough Blocks question. I read the FAQ.

Post by datalogger »

Feralhost is probably fine if you don't use SABnzbd for large RAR Sets.
If fails miserably if you do, at least with NewsDemon News Servers.

If all you use it for is seeding things you uploaded via FTP, or for a lot of small RAR's using SABnzbd, it does fine.
It doesn't do so well with larger files remotely grabbed with SABnzbd.


I tested the same 5.9GB set of RAR's on my Feralhost Server 4 times.
Each time it came back with different amounts of missing blocks, between 682 to 786 of 2001 blocks available - 114 to 197 recovery blocks

I tested my other seedbox 4 times with the same file/host/user and it came back with 1982 out of 2001 blocks available - 200 recovery blocks every time.

The other big difference is "Download folder speed" (from SABnzbd Status and Interface Options)
Feral = 5.7MB/s
Other = 39.9MB/s

This may be the key... maybe it's because Feral has too many users on this server (cacus) and it's dropping data.

This would be my conclusion by comparing the same set of files and looking at the difference in the number of blocks downloaded.


Feralhost:
Target: "part1.rar" - damaged. Found 108 of 431 data blocks.
Target: "part2.rar" - damaged. Found 296 of 431 data blocks.
Target: "part3.rar" - damaged. Found 16 of 431 data blocks.
Target: "part4.rar" - damaged. Found 89 of 431 data blocks.
Target: "part5.rar" - found.

Otherhost:
Target: "part1.rar" - damaged. Found 425 of 431 data blocks.
Target: "part2.rar" - damaged. Found 429 of 431 data blocks.
Target: "part3.rar" - damaged. Found 427 of 431 data blocks.
Target: "part4.rar" - damaged. Found 424 of 431 data blocks.
Target: "part5.rar" - found.


Since all of this downloading is done between their servers, I would conclude the problem is one of them.
I used the same .INI files for both seedboxes. (with the exception of the Port Numbers and temp folder names)

Since I get the same exact size of files when I use one seedbox and varying sizes on Feral, I would assume the issue is on Feral's side.
Post Reply