newsbin.com

This problem has been happening to me in prior versions as well.

When Sonarr downloads an nzb file from one of my indexers Newbin can only repair it about 50% of the time. Same thing happens if I do it manually. It's not a problem with the indexer as no one else is having the same problem and it's not a problem with Sonarr.

I can always successfully repair if I go to AutoPAR/Run QuickPar

If I then go to AutoPAR/UnRAR/Join Files it comes up with this message : Quick UnRAR:No filename found

If I click on the files properties and hit refresh that doesn't help either.

The only way I can unrar it is if I use Winrar.

This is a bit annoying so I was wondering if anyone else has encountered this problem and if they know a fix?

BTW am using Windows 10 but it was happening in Windows 8.1 too.

Cheers

Had a guy on the IRC channel who was monitoring a download with quickpar in parallel to newsbin. Part way through he let Quickpar rename some of the files. That scewed Newsbin up because the files it was looking for weren't there anymore. You're not doing anything like that are you?

Downloading an NZB from Sonaar is no different than downloading any other NZB file. I'd suggest watching the download and look at the PAR counts while it downloads and watch for error messages. Your symptoms suggest that Newsbin doesn't think enough blocks are there to repair even though there are enough.

What happens if you click the + icon and unpause some PARS associated with the download?

No QuickPAR is not constantly monitoring so it's not that.

Newsbin downloads all PARS as it keeps trying to repair the file seeing the first PAR didn't do it.

But I have 5 indexers and this is only happening when It downloads an nzb file from one paarticular indexer yet nobody else who uses that indexer is having any problems.

Newsbin downloads all PARS as it keeps trying to repair the file seeing the first PAR didn't do it.

This is the key. Random par filenames I'll bet.


http://www.newsbin.com/downloads/nb663B1.exe

give this one a try.

Will do but like I mentioned earlier this has been happening to me for a while and not just version 6.62

1 - Random PAR filenames are new.

2 - 6.63 has a specific fix for random par filenames.

The fact it downloads all the PARS but repair fails and that it's not a 100% issue is what makes me suspect 6.63 will help.

So far so good so hopefully that has fixed the problem.