par2 file repair not efficient
Posted: January 19th, 2016, 8:36 am
I am using SABnzbd 0.7.20 on Debian 8 64bit and I get a lot of "unrepairable" data notifications with SABnzbd.
Usually only one or two data blocks are corrupted and the are more than enough repair blocks left, but the par file repair is not working correctly.
Actually SABnzbd reports that there are hundreds of data blocks missing but when I copy the data to an external hard drive and boot into Windows 8.1 64 bit and run quickpar for Windows I get the notification that only one or two data blocks are corrupted and repair is done within seconds.
This is happening rather regularly and I wonder what is wrong.
Is it a Linux/Debian problem?
Is it a problem with SABnzbd ?
Did I do some configurations wrong?
What kind of par2 repair is SABnzbd using?
Usually only one or two data blocks are corrupted and the are more than enough repair blocks left, but the par file repair is not working correctly.
Actually SABnzbd reports that there are hundreds of data blocks missing but when I copy the data to an external hard drive and boot into Windows 8.1 64 bit and run quickpar for Windows I get the notification that only one or two data blocks are corrupted and repair is done within seconds.
This is happening rather regularly and I wonder what is wrong.
Is it a Linux/Debian problem?
Is it a problem with SABnzbd ?
Did I do some configurations wrong?
What kind of par2 repair is SABnzbd using?