unpacking issue suddenly started a couple weeks ago

[damienb]

Hi, long time user, until recently I've essentially had zero issues with sab. But something weird is happening with the unpacking and I can't figure out the issue (Ive read quite a few posts with similar issues but they seem to be different setups or outcomes)
As of a couple weeks ago I started getting half unpacked files moved from my temp sab folder to my 'completed sab folder'. The normal process from there would be couchpotato's renamaer would rename etc and move it on to my synology nas
There would be an error from sab "expected file not available" (or something to that effect) always referencing the video file not being available. Often with the unpacked rar files that were transferred to my 'completed' folder would be a not fully extracted/damaged video file that renamed would move to my nas. A 13 gig 1080 file would show up as a 3 gig file on my nas (and obviously damaged, not playable). If only the rar files were transferred and no video file was extracted, the majority of the time a manual extraction would work and the completed file wold be available.

Last night I upgraded to beta 8.02 (from 7.20) to see if any difference would be made and ran a file that had previously failed. "The gift" on 10-11-15 at 2:39am, ran into the same issue. half the rars and the damaged video file were moved to the 'completed' folder were cp moved the video file that sabnzbd couldn't find during the unpacking (obviously bc it was no longer in the temp file to be extracted).

I've included the log for the time period I ran 'the gift". Also a link of the screenshot of the error message (probably not necessary). I've been running Sab secured for years but tried running it without; didn't seem to make a difference.

I have movies set to delete+
Running OS X 10.10.5
Any guidance or suggestions would be hugely appreciated. Thanks a lot.
log https://www.dropbox.com/s/raunx5ko9r4zk ... log.1?dl=0 
error https://www.dropbox.com/s/fm8hm8884zmw5 ... 1.png?dl=0

[shypike]

Are you using SABnzbd in isolation or with SickBeard or CoachPotato?

[Chizuruk]

Hi,

I've exactly the same problems.
I have SABNZBD 0.7.20.13 installed on my Synology NAS, and most of the time exactly the same error. If I take manually the files and use Quickpar the repair is OK... So I think the problem is coming from the PAR2 module included in SABNZBD.
I tried with another soft on my PC, same server etc... everything is OK...
(
I also tried with Beta 0.8 but exactly same result.

Isn't it possible to change the PAR2CMDLINE module on the SABNZBD (for Synology)?

[shypike]

par2cmdline is not part of SABnzbd.
It has been added by the third party that created the Synology package.
You need to ask that party.

[blackkatt]

Same issue here, Win10, using par2x64 that comes with...this happens also for UnRAR.exe
http://imgur.com/3XbMwos PM me and I give you a couple of files that this happens with.
Got the same error for SAB when trying to restart from the notification bar

[safihre]

This seems to be another problem, when searching for the code (0xc0000142) it comes up with problems in DLL registration caused by other software:
http://www.usmanalitoo.com/how-to-fix-a ... l-windows/

[blackkatt]

This seems to be another problem, when searching for the code (0xc0000142) it comes up with problems in DLL registration caused by other software:
http://www.usmanalitoo.com/how-to-fix-a ... l-windows/

Oh, well that's good to known.

[damienb]

Are you using SABnzbd in isolation or with SickBeard or CoachPotato?

sorry for the late reply, for some reason I didn't receive a notification.

Too answer your question, I have cp working with Sab. It's still an on going issue (least for me) in beta 4. I run into issues when the files are larger. The entire rar pack gets moved out of the temp folder to completed (where it's moved to my NAS).

It's odd as I've essentially had almost no problems with Sab for years. Leads me to believe I'm doing something to cause the issue but I can't imagine what.

[shypike]

If the bugs are in par2 and unrar, then there's not much we can do.
You can disable the 64bit versions in Config->Special->allow_64bit_tools
You can also downgrade unrar to an older release, see rarlab's website.
We haven't touched par2 for a few years.