SABnzbd Forums

Posted: **August 14th, 2013, 6:50 am**

shypike wrote:Please set logging to Debug (Status page) and try to find the
lines where par2 is started.

Typical, recent downloads have been ok, still awaiting a fail ... I have debug log turned on though.

Posted: **August 18th, 2013, 9:17 am**

Bushbrother wrote:I seem to have a similar issue as the original post, I am using the latest 0.7.14 version on my qnap nas and I have loads of issues with downloads failing as they hit the par2 verify stage. Running par2 manually on the nas shows that it cannot see all the spanned .r01 .r02 etc files to unpack.

However if I load the par2 file in windows using quickpar it shows that the files I have downloaded are all incorrectly named and it fixes them into the required spanned rar format.

The files I download are like .10 .11 .12 etc and seem to contain multiple rar files, they are all named in a long sequence of random numbers and letters.

Any help appreciated on how to correct this!

Bump.

I had this exact same problem on my QNAP with lots of downloads failing.

Basically, on 0.7.14, the par2 repair stage would see all the archive files as missing because they weren't renamed correctly. However, running QuickPar in Windows on the NAS files would rename them and repair if needed.

I basically reverted to 0.7.11 to fix the issue.

Is anything gonna be done about this?

Posted: **August 18th, 2013, 10:43 am**

Hi,

So I got this happening with debug logs switched on this time. Appears to be an issue with the "__ADMIN__" folder still being present when running PAR2. I have the same issue when running PAR2 with a "*" command, I have to delete this directory first or it does not find anything. Does this help with working out why this is not working? I ran this on quickpar in windows and it was al fine, I also ran PAR2 on my QNAP with a "*" wildcard and it fixed it fine, I could then unrar the resulting files.

Looks the same as http://forums.sabnzbd.org/viewtopic.php ... N__#p86086 so it may be fixed in the next release as SABnzbd is correctly using the * in the commandline.

Here is the log, file title adjusted for obvious reasons.

Code: Select all

2013-08-16 11:32:48,258::INFO::[postproc:278] Starting PostProcessing on A.Movie.Title => Repair:True, Unpack:True, Delete:True, Script:None, Cat:movies
2013-08-16 11:32:48,304::DEBUG::[bpsmeter:253] bps: 878226.053455
2013-08-16 11:32:48,774::INFO::[postproc:548] Par2 check starting on A.Movie.Title
2013-08-16 11:32:53,314::DEBUG::[bpsmeter:253] bps: 875408.736938
2013-08-16 11:32:53,521::INFO::[__init__:859] /share/Download/sabnzbd/incomplete/A.Movie.Title/__ADMIN__/__verified__ missing
2013-08-16 11:32:53,523::INFO::[postproc:569] Running repair on set b19bd70472c2620420969da3a20c33ba
2013-08-16 11:32:53,652::INFO::[newsunpack:1425] Cannot Quick-check missing file A.Movie.Title.r60!
2013-08-16 11:32:53,684::INFO::[newsunpack:838] Scanning "/share/Download/sabnzbd/incomplete/A.Movie.Title/b19bd70472c2620420969da3a20c33ba.par2"
2013-08-16 11:32:53,771::DEBUG::[newsunpack:1391] build_filelists(): joinables: []
2013-08-16 11:32:53,774::DEBUG::[newsunpack:1392] build_filelists(): zips: []
2013-08-16 11:32:53,815::DEBUG::[newsunpack:1393] build_filelists(): rars: []
2013-08-16 11:32:53,817::DEBUG::[newsunpack:1394] build_filelists(): ts: []
2013-08-16 11:32:53,819::DEBUG::[newsunpack:950] Par2-classic = True
2013-08-16 11:32:54,154::DEBUG::[newsunpack:975] Starting par2: ['/opt/bin/par2', 'r', '/share/Download/sabnzbd/incomplete/A.Movie.Title/b19bd70472c2620420969da3a20c33ba.par2', '/share/Download/sabnzbd/incomplete/A.Movie.Title/*']
2013-08-16 11:32:54,710::DEBUG::[newsunpack:1267] PAR2 output was
The source file does not exist: /share/Download/sabnzbd/incomplete/A.Movie.Title/__ADMIN__
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.
Usage:
par2 c(reate) [options] <par2 file> [files] : Create PAR2 files
par2 v(erify) [options] <par2 file> [files] : Verify files using PAR2 file
par2 r(epair) [options] <par2 file> [files] : Repair files using PAR2 files
You may also leave out the "c", "v", and "r" commands by using "parcreate",
"par2verify", or "par2repair" instead.
Options:
-b<n>  : Set the Block-Count
-s<n>  : Set the Block-Size (Don't use both -b and -s)
-r<n>  : Level of Redundancy (%%)
-c<n>  : Recovery block count (Don't use both -r and -c)
-f<n>  : First Recovery-Block-Number
-u     : Uniform recovery file sizes
-l     : Limit size of recovery files (Don't use both -u and -l)
-n<n>  : Number of recovery files (Don't use both -n and -l)
-m<n>  : Memory (in MB) to use
-v [-v]: Be more verbose
-q [-q]: Be more quiet (-q -q gives silence)
--     : Treat all remaining CommandLine as filenames
If you wish to create par2 files for a single source file, you may leave
out the name of the par2 file from the command line.
2013-08-16 11:32:54,713::INFO::[newsunpack:856] Par verify failed on /share/Download/sabnzbd/incomplete/A.Movie.Title/b19bd70472c2620420969da3a20c33ba.par2!
2013-08-16 11:32:54,729::DEBUG::[__init__:829] Saving data for __verified__ in /share/Download/sabnzbd/incomplete/A.Movie.Title/__ADMIN__
2013-08-16 11:32:54,732::INFO::[postproc:596] Par2 check finished on A.Movie.Title
2013-08-16 11:32:55,768::INFO::[postproc:521] Cleaning up A.Movie.Title (keep_basic=True)

Posted: **August 19th, 2013, 1:15 pm**

Yes, we know by now.
It's only that those NAS systems (or the par2cmdline port) have a serious flaw that
is not easy to make a work-around for.

Posted: **August 19th, 2013, 1:46 pm**

Anything I can do to help or test let me know

Posted: **August 19th, 2013, 4:15 pm**

There will be a work-around in the next 0.7.x release.

Posted: **September 6th, 2013, 3:28 am**

Why does it work in 0.7.11 and not in later revision ?

Posted: **September 6th, 2013, 12:32 pm**

Have you tried 0.7.16?

Posted: **September 7th, 2013, 2:28 pm**

yes, thanks. 0.7.16 has fixed the issue for me.

Posted: **September 17th, 2013, 6:09 am**

Just to add that 0.7.16 has fixed this for me too on a QNAP ARM based NAS. Many thanks for the quick fix on this!

Posted: **January 27th, 2014, 9:00 am**

Recently quite a few of the downloads I do have besides the misname files, also have the file extension of the par files changed.

Is it possible to rename files from *.p to *.par2, before extraction commences ?

Posted: **January 27th, 2014, 2:55 pm**

You mean, rename them yourself or that SABnzbd renames them?
The latter is tricky.

Posted: **January 28th, 2014, 4:03 am**

During download I renamed one .p file into .par2 directly in the download folder. This was not picked up and the download was moved as-is (obfuscated) into the target directory. Perhaps I should disable QuickCheck ?

In the mean time I understood that I can implement a post-processing user-script. I will also give that a try.

Posted: **January 28th, 2014, 4:09 am**

Disabling QuickCheck will not solve anything.
Renaming at any time is difficult, because SABnzbd will assume there are files missing.
I will look at the possibilities for a future release.
In the mean time, use QuickPar and WinRAR to do manual post processing.
I assume a small minority of your download are like this?

Can you email me one or more example NZB files that show this problem?
[email protected] and please add the URL of this message.

SABnzbd Forums

Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?

Re: Intentionally misnamed rar sets unusable with Sabnzbd?