Error unpacking ***.rar*2, but everything is actually extracted fine

[isofan]

Hi,

I have a very annoying behaviour: whenever I have a release downloaded that has been repaired, I get an error message that looks like thsi:

Unpacking failed, unable to find xyz.part087.rar.2

but actually, evertything is extracted fine. I guess the .rar.[number] file somehow is related to a file that was repaired, but not found, or not needed, I don't know, all I know is I get this with about 50% of my downloads, which are finally 100% okay.

Any way to fix this?

[shypike]

I have a very annoying behaviour

See a therapist.

What happens is that you unpack an archive with poorly encoded filenames.
Usually it's about weird Unicode characters that cannot be mapped on your file system.
SABnzbd has to guess what unrar will make of it, and it's sometimes wrong.
You can disable the error message as described here:
http://wiki.sabnzbd.org/configure-special item "unpack_check".

[isofan]

Sorry, I am sure what you describe is not the problem, it really happens with normal files only containing US-american ASCII characters.

The problem seems to be that when Sabnzbd detects that a file needs to be repaired, that was called filename.r62, the repaired file gets the name filename.r62.1

And after unpacking succeeded, the program somehow tries to unpack these new .1-files again, that's at least what it looks like.

This error is shown on the web interface, but the rar-files are finally deleted, and the unpacked content is moved to the right directory, and the content is perfectly right. So I guess it is only an error in the user-interface, since Sabnzbd has internally detected the unpacking-process to be correct. Otherwise, wouldn't the program leave the files and not delete them, so that the user can try to repair them manually?

[shypike]

OK, missed the .2 in the rar file name.
Can you send the NZB to bugs at sabnzbd.org with a reference to this post?

[isofan]

Hi shypike,

thanks alot, I sent you a sample, but since so many nzbs are affected, I guess it is not related to the nzb itself...

[shypike]

Cannot find anything wrong.
It's not quite clear to me why .2 files would be created.
.1 makes sense, that's the original damaged file left behind by par2-repair.
I would need to have a full debug-log of such a failed download.
At least the part covering the post-processing.

[isofan]

Hi,

I have had a look at abnzbd.log, but I find it very hard to read, since all the entries from this and other downloads are mixed up, i.e. chronologically. Is there any way to sort the logfile, so that I see only entries relevant to that single NZB?

Nevertheless, I will send you the whole log if you'd like to have a look at it

[shypike]

If you ZIP or RAR it, I'd be happy to analyse it.

[isofan]

If you ZIP or RAR it, I'd be happy to analyse it.

Thanks alot, I've sent it to the emailaddress you gave me, can you see anything strange from the logs?

[shypike]

Looking at the logfile shows that for some bizarre reason doesn't recognize the rar sets properly.
SABnzbd doesn't exhibit this problem normally (else we would get plenty complaints).
Also it's not likely that its something triggered always by this NZB (at least not when I test it).

This may take while, please be patient.

[dcorban]

This is the same problem I was having maybe a year ago. If something happens with sabnzb which causes it to create a *.rar.1 file, then everything will process correctly, however sabnzb will report a failure when it tries to handle the .1 file.

[shypike]

.rar.1 files appear whenever files have been repaired by par2,
so it's nothing unusual.
Very occasionally SABnzbd seems to have trouble ignoring these files.