Support Forum

I've updated to the latest beta of sab. That also solved the issue.

Beta was fine, but the final broke sab: it doesnt unrar anymore.

Hi, i have the same issue (i think since i upgraded to the latest version of my synology box) for every download: 2013-07-16 16:19:53,734::DEBUG::[newsunpack:950] Par2-classic = True 2013-07-16 16:19:53,745::DEBUG::[newsunpack:975] Starting par2: ['/var/packages/baseutils/target/utils/bin/par2', 'r'...

OK i think i found the script you mentioned:

http://j3e.de/linux/convmv/man/

I put that into a user-script which looks like that:

#!/bin/sh
convmv -r -f iso-8859-1 -t utf8 --notest $1

Lets see if this is working...

shypike wrote: The best way is to configure your system to support UTF-8.

Hmh how to do that?

I just searched a little bit and maybe found the tool you mentioned: fslint? http://en.flossmanuals.net/FSlint/BadNames I would be more happy with a solution on the unraring-side but if there is none i will try it that way... Is it possible to use the logic which is already build into sabnzbd for th...

Hi there, i have a problem. I have running sabnzbd on my QNAP. Sometime after unpacking there are some files which are unaccessible via SMB. When i look via SSH they have strange characters in the filenames in it (lika a CR) where for example german umlauts should be (ä,ü,ö). I guess the unrar choos...