Repairs failing, but able to manually unpack just fine?

hpman247 · Post by **hpman247** » January 24th, 2013, 5:05 am

I get this error message sometimes on TV shows that I'm using with sickbeard. » Repair failed, not enough repair blocks (579 short)

However, when I go into my incomplete downloads folder, and I unpack the files manually, the file is always fine. It unpacks without any issues and I just manually add it to the proper folder. Why wont SAB still unpack the file and do this even if articles are missing. Obviously no needed articles are missing or else I wouldn't be able to unpack the episode and watch it with no issues? This doesn't happen too often, but I'm just curious why SAB can't automate this process.

Thanks

Post by **shypike** » January 24th, 2013, 7:10 am

I suspect these downloads use odd naming conventions.
This will be handled better in the next release.

bison88 · Post by **bison88** » January 24th, 2013, 1:16 pm

Good to know shypike

. I've only experienced this one time myself and it was an obfuscated posting.

zoneboyz · Post by **zoneboyz** » January 25th, 2013, 9:34 am

perhaps a temp alternative prior to full bug-fix is to have these dump into an alternative DL directory named "issues" or something. This way manual intervention is possible prior to deleting the download.

BDJ · Post by **BDJ** » January 31st, 2013, 10:23 pm

shypike wrote:I suspect these downloads use odd naming conventions.
This will be handled better in the next release.

Very same thing happening to me...and it seems to be much more common as the days go by. example of file names are:

130028-3.4
130028-3.5
130028-3.6
etc...

The pars don't recognize the files exist.

Post by **shypike** » February 1st, 2013, 4:09 am

Tried the new 0.7.10 release?

BDJ · Post by **BDJ** » February 1st, 2013, 2:05 pm

shypike wrote:Tried the new 0.7.10 release?

Well...sort of.

I'm running a Debian server stable (squeeze). What I did was use sabnzbd 7.10 compiled for ubuntu on it. python version is still 2.6.6 on the server.

After running, the download hangs on verifying 01/01. Could it be a python 2.7 related issue or something similar?

I think I might need to update Debian to testing?

Post by **shypike** » February 1st, 2013, 2:15 pm

Just download the tar.gz distribution file, unpack it to some location
and run the SABnzbd.py script, using your favourite Python version.
You should have Cheetah and PyOpenSSL installed for the Python version that you use.

BTW: hanging unpacks are usually the result of bugs in unrar, not SABnzbd itself.

BDJ · Post by **BDJ** » February 1st, 2013, 2:30 pm

It finally took. It seemed to take forever but it works.

Thank you sir.

Post by **shypike** » February 1st, 2013, 6:50 pm

Unrar's speed has a bad reputation on some systems,
especially in combination with non-local drives.

Support Forum

Repairs failing, but able to manually unpack just fine?

Repairs failing, but able to manually unpack just fine?

Re: Repairs failing, but able to manually unpack just fine?

Re: Repairs failing, but able to manually unpack just fine?

Re: Repairs failing, but able to manually unpack just fine?

Re: Repairs failing, but able to manually unpack just fine?

Re: Repairs failing, but able to manually unpack just fine?

Re: Repairs failing, but able to manually unpack just fine?

Re: Repairs failing, but able to manually unpack just fine?

Re: Repairs failing, but able to manually unpack just fine?

Re: Repairs failing, but able to manually unpack just fine?