Support Forum

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!

Anything I can do to help or test let me know

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 anyth...

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.

Thanks, if you need me to provide logs etc then let me know here, happy to help resolve this.

Yes, running on a Qnap ts-419 arm based. But I am running latest version of sabnzbd

Bumping this up again, is there a plan to correct this? I am seeing probably half my NZB downloads hit this issue meaning a lot of manual work. Using par2 with a * always works and renames the files so unpack can take place. This is being done intentionally to avoid DCMA takedowns ... A fix would be...

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. Howev...