newsbin.com

Using B12, I'm finding that AutoPAR is sometimes deleting all of the .rars in a fileset before it has finished unraring them.

I have Newsbin set to download all of the files in a set into a folder on one hard drive, and then have it set to unrar them onto another drive for the sake of speed (otherwise Newsbin grinds to a halt while file operations are taking place).

Here are the errors received:

[17:48:48] ERROR - Assemble RAR Error: Cannot open: D:\Newsbin Download\NZBFolder\241110-01_12_23.rar
[17:48:48] ERROR - AutoPARPlugin: UnRAR failed: /bk3dkcbV/5+W8shaCJgnw==
[17:48:48] ERROR - AutoPARPlugin: Autopar Repair Repaired the files but, UnRAR FAILED: No UnRAR: 241110-01_12_23.vol007+08.par2

This has happened to me twice this week. Sucks because my ISP has a 150GB limit on transfers for the month and this has wasted at least 20GB for me.

Also of note, I have Newsbin set to delete files into the Recycle Bin and none of these files are ending up there.

17:48:48] ERROR - Assemble RAR Error: Cannot open: D:\Newsbin Download\NZBFolder\241110-01_12_23.rar

This error (which I've never seen before) kind of implies that the RARS aren't there in the first place. PM me the subject and group and I'll take a look.

This is happening because the program is confused on what your rar files are.
this happened to me.
you have to add the actual rar file types to your rar filter.
by default it only knows .rar and a couple others
you have to add any rar type you download such as
.001
.01
.part01
etc... this happened to me and i was pissed. i downloaded 6 gigs to get 2.5 lol

in other words the unrar fails, it deletes the rar files, but because they arent rar files they are permanently deleted.

Skeptic23 wrote:in other words the unrar fails, it deletes the rar files, but because they arent rar files they are permanently deleted.

If an unrar fails, then the files should not have been deleted. If they were then that is a bug.

Another (I think more likely) scenario is that they were rar files posted with the deprecated .nnn type file extensions and that NB treated them as a QPMS file that it tried (it thought successfully) to combine into one bigger file. However if it was not really a QPMS file then this could have unfortuante side-effects.