SABnzbd Forums

Hi,

I have a regular Raspberry Pi Model B (512MB RAM), Raspbian Jessie Lite fresh install.

I tried the default version of Sabnzbd, then 0.8.0 beta3 (found the procedure somewhere on this forum).

I tried to download several NZB's and they failed on my Pi. On my PC, the download always succeeds.

I'm trying to reproduce the problem now. The following NZB:

http://www.nzbking.com/details:50389c8b ... 8eb8081a7/

fails to download on the Pi, but it works fine on my PC with Sabnzbd 0.7.16.
I tried twice on the Pi.
First time : 56 blocks short.
Second time : 183 blocks short.
...weird! My usenet provider is fine.

I once found a message on this board saying version 0.7.something doesn't work on the Pi and this 'has been corrected'. So I did upgrade, but in the end still have problems.

I do believe there is something really fishy going on as it's been months I am having big problems. Problems started to appear when I upgraded my old Pi distribution (an old 2013 or 2014 Wheezy distribution that I never changed, and that was running fine, until I decided to upgrade).

Sometimes, downloads succeed.
Lately, I moved my temp and unpack dir from network to local USB drive. To no avail.

Thanks for your help, and happy new year!

I downloaded your NZB with my SABnzbd 0.8.0 Beta4 on my Ubuntu without problems.

And no problems on my Raspberry.

BTW: How good are you with Linux? Can you follow a command line instruction? Reason: in the past days a difference was discovered between SAB-on-Windows and SAB on other OSes, combined with par2 results.

I launched a download last night and the same file failed again - this time repair failed with 115 blocks short.
My temp drive is a (reliable) USB key with plenty of space.

I feel alright with Linux, it should be fine to perform some investigation.

It might be the same cause as here: http://forums.sabnzbd.org/viewtopic.php?f=2&t=19998

On your raspi, what is the output of "par2 -V" (capital V)

On your raspi, can you follow these instructions:
http://forums.sabnzbd.org/viewtopic.php ... 98#p103710

par2 -V output : I have version 0.6.11 installed.
Following the instructions you mentionned now - I might follow up only later today though.

Local build of 0.6.14 was fine (and properly reports version 0.6.14, and existence of -N option).
How to I get sabnzbd to use my own par2 build and not the system's?

I am not sure the problem comes from an option in par2, though, as:
does not list any line.
None of my log files (sabnzbd.log*) does.

Currently, I have
Shall I try to add the -N option? I need to tell sabnzbd to use my own par2 build. Will 'make install' in my par2 build directory work? I need to be careful, because this will become permanent, won't it?

A "sudo make install" should take care of it, but it didn't work on my setup. and that worked on my Minibian (tiny Raspbian)

Before you run it, make a backup of your current par2 ... something like this:
Then run "sudo make install" and then "par2 -V" again. If there is no par2, manually copy the generated par2 to /usr/bin/par2. Then run "par2 -V" again to check.

'sudo make install' worked for me. par2 0.6.14 is now default. Installation has been performed in /usr/local/bin.

Tried the download again : it failed.

I am now (only now) going to add the -N option in the 'Extra PAR2 Parameters' field in the SAB config, restart SAB, then try the download again.

But really, I don't get it : on Windows, I am not using the -N option, and the download succeeds. How do you explain that?

No, wait ... not there yet. Possible ways to go forward:

1) Do a manual "par2 r -N *.par2" in the directory containing your download.
2) Download the git version of SABnzbd, start it, fill out option "-N" out in Config -> Switched "Extra PAR2 Parameters", retry and/or rerun the download
3) The Real Stuff: download my git version of SABnzbd, with everything built in. No need for a manual switch. See http://forums.sabnzbd.org/viewtopic.php ... 96#p103796

So ... what do you prefer? I would like it if you choose 3 so that you can test my automagic version.

But really, I don't get it : on Windows, I am not using the -N option, and the download succeeds. How do you explain that?

I don't get it either, so I can't explain (yet)! Maybe the Windows version has the -N functionality (no data skipping) built in?

-N option added. Restarted SAB.
Suppressed NZB and files. Re-added the NZB.

186 blocks short, this time :-(

How is it possible that I get a different number of blocks each time?!
Will try option 3 above, tomorrow.
Last chance ?

You tried option 2, and that didn't work?! If so, there is no need for option 3; it does the same ("par2 r -N"), only automagic.

Check that -N was really used: Post the line here.

Example from system:

How is it possible that I get a different number of blocks each time?!

I have no idea.

I have not pulled SAB from the Git repository. The version that I am using still is 0.8.0 beta 3.
Can you tell me:

Does my version take into account this -N option for par2, even with 0.6.14 installed?
shypike said only the Windows understands it - could you confirm?
https://forums.sabnzbd.org/viewtopic.ph ... 98#p103718

My Windows setup has 'par_option = ""' specificed, eg. there is no option -N.
Is -N enabled in all cases in the Windows version?

Two more things I want to try:
1) reformat my temp drive to ext4 - I am currently using ntfs-3g (which is very stable, though).
2) rebuild an SD card with a distro of your choice, and try again everything.

pi@raspberrypi:~ $ cat ~/.sabnzbd/logs/sabnzbd.log | grep "Starting par2" | cut -c-200
2016-01-11 17:54:36,987::DEBUG::[newsunpack:1195] Starting par2: ['/usr/bin/par2', 'r', '/media/usbdrive/50389c8b66cec608eb8081a7/Avengers (2012) HDrip BBer.mkv.par2', '/media/usbdrive/50389c8b66cec60
2016-01-11 19:24:03,511::DEBUG::[newsunpack:1195] Starting par2: ['/usr/local/bin/par2', 'r', '/media/usbdrive/50389c8b66cec608eb8081a7/Avengers (2012) HDrip BBer.mkv.par2', '/media/usbdrive/50389c8b6
pi@raspberrypi:~ $

So here we see the new version of par2 being in use (good).
The folder names behind /media/usbdrive are truncated, but that's probably a log thing?

Have reformatted my usb pen drive with ext4. I am trying the download again.
If this fails, I will try to manually launch par.