Just upgraded to the newest version 16.4 (yes, I'm behind the times), and I'm having an issue with nearly all my downloads, where NZBGet verifies the par, and finds no issue (no repair required), then it tries to unpack, and discovers the files are broken, and it fails.
ParCheck is on FORCE
ParScan is on DUPE
I then load the .par into MultiPar, which quickly identifies the broken files and repairs.
I can then go back to NZBGet and do "post-process again" which will then unpack correctly.
Why does NZBGet not seem to actually find the broken files, and repair? It's like NZBGet is just assuming everything's good, or it's simply ignoring the fact there are broken files...
It's frustrating, as this is the only step that is holding my setup back from being completely unattended...
EDIT - here's what it's showing in the "broken.txt"
Code: Select all
filename.part04.rar (68/69) filename.part02.rar (68/69) filename.part07.rar (68/69) filename.part13.rar (68/69) filename.part23.rar (68/69) Repair not needed for nzbname\filename Repair not needed for nzbname\filename