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.
I just found sabnzbd and attempting to run it. It complained about missing stuff. I started to install par2 using these instructions.
[New users are not allowed to post links].org/wiki/installation/multicore-par2
whitemouse@ubuntu:~$ sudo apt-get install par2-tbb
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libtbb2
The following NEW packages will be installed:
libtbb2 par2-tbb
0 upgraded, 2 newly installed, 0 to remove and 10 not upgraded.
Need to get 242 kB of archives.
After this operation, 764 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 [New users are not allowed to post links]universe amd64 libtbb2 amd64 2020.1-2 [124 kB]
Get:2 [New users are not allowed to post links]main amd64 par2-tbb amd64 0.4+20150503-0ubuntu1~jcfp2~focal [117 kB]
Fetched 242 kB in 0s (539 kB/s)
Selecting previously unselected package libtbb2:amd64.
(Reading database ... 356976 files and directories currently installed.)
Preparing to unpack .../libtbb2_2020.1-2_amd64.deb ...
Unpacking libtbb2:amd64 (2020.1-2) ...
Selecting previously unselected package par2-tbb.
Preparing to unpack .../par2-tbb_0.4+20150503-0ubuntu1~jcfp2~focal_amd64.deb ...
Unpacking par2-tbb (0.4+20150503-0ubuntu1~jcfp2~focal) ...
Setting up libtbb2:amd64 (2020.1-2) ...
Setting up par2-tbb (0.4+20150503-0ubuntu1~jcfp2~focal) ...
Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
whitemouse@ubuntu:~$ sudo apt-get install par2-mt
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package par2-mt is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'par2-mt' has no installation candidate
The patches from par2-mt were merged into the standard par2 years ago, leaving par2-tbb as the sole alternative version. At that time, the par2-mt package was modified to simply pull in the regular (now multicore) par2; it was dropped for recent ubuntu releases once every supported ubuntu upgrade path was covered.
Standard multicore par2 is newer, better maintained, and works on all hardware architectures; par2-tbb is abandoned upstream, based on ancient source code with zero bug fixes in more than a decade, and limited to archs supported by libtbb - but also the faster of the two.
jcfp wrote: ↑September 14th, 2021, 2:45 am
The patches from par2-mt were merged into the standard par2 years ago, leaving par2-tbb as the sole alternative version. At that time, the par2-mt package was modified to simply pull in the regular (now multicore) par2; it was dropped for recent ubuntu releases once every supported ubuntu upgrade path was covered.
Standard multicore par2 is newer, better maintained, and works on all hardware architectures; par2-tbb is abandoned upstream, based on ancient source code with zero bug fixes in more than a decade, and limited to archs supported by libtbb - but also the faster of the two.
jcfp wrote: ↑September 14th, 2021, 2:45 am
The patches from par2-mt were merged into the standard par2 years ago, leaving par2-tbb as the sole alternative version. At that time, the par2-mt package was modified to simply pull in the regular (now multicore) par2; it was dropped for recent ubuntu releases once every supported ubuntu upgrade path was covered.
Standard multicore par2 is newer, better maintained, and works on all hardware architectures; par2-tbb is abandoned upstream, based on ancient source code with zero bug fixes in more than a decade, and limited to archs supported by libtbb - but also the faster of the two.
I would say: Delete that page completely. Not relevant for 99.9% of SAB users. And the 0.1% percent lovers of abandon-ware should find their info elsewhere