sabnzbd version - 07.10
Releases tested:
TPB AFK
AFK TPB
These are from my own indexing site, they failed first as a RSS feed, had to kill par.exe and sabnzbd to clean out files.
Tried downloading just TPB AFK and when i killed the par process i got an email alert on failure:
Stage Download
Downloaded in 7 minutes 11 seconds at an average of 8.2 MB/s
Stage Failure
Repair failed, not enough repair blocks (55 short)
Stage Repair
[130145-2] Repaired in 0 seconds
[130145-1] Repair failed, not enough repair blocks (55 short)
[130145-0] Verified in 1 minute 6 seconds, repair is required
Stage Source
A:\NZB\TPB AFK
HOWEVER - Both releases repairs using Quick Pair manually.
Logfile:
http://forums.sabnzbd.org/viewtopic.php?f=8&t=41
Parity repair fails
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Parity repair fails
Last edited by RuneRuler on February 9th, 2013, 1:22 am, edited 2 times in total.
Re: Parity repair fails
Can you read the forum rule http://forums.sabnzbd.org/viewtopic.php?f=8&t=41 and then change your post? Thankyou.
Re: Parity repair fails
Now we are safe, i encrypted the logfile as well...
Edit, seems like this and several other bugs has already been addressed in .11 - well done developer(s).
Let me know if you need competent beta testing; Ill be happy to help.
/Rune
PS I suggest you push update notification to all clients, I never saw the update until i checked the front page
Edit, seems like this and several other bugs has already been addressed in .11 - well done developer(s).
Let me know if you need competent beta testing; Ill be happy to help.
/Rune
PS I suggest you push update notification to all clients, I never saw the update until i checked the front page
Re: Parity repair fails
SABnzbd has an update notification, but it runs at random time within a weekly interval.
Re: Parity repair fails
Or indeed if i restart the client ;-)
Allow me to take this opportunity to commend you on an excellent piece of software, .11 seems to work very well again.
Allow me to take this opportunity to commend you on an excellent piece of software, .11 seems to work very well again.
Re: Parity repair fails
Yes, too bad 0.7.9 and 0.7.10 did notRuneRuler wrote:.11 seems to work very well again.
-
- Newbie
- Posts: 2
- Joined: February 11th, 2013, 2:12 pm
Re: Parity repair fails
I encountered same issue - sabnzbd 7.11 fails to repair (actually only rename) files - windows quickpar runs smooth renaming them only.
error info i receive from him is that release is 54 blocks short.
Is there any update on this one - its really annoying
error info i receive from him is that release is 54 blocks short.
Is there any update on this one - its really annoying
Re: Parity repair fails
Look, SABnzbd cannot fix every crazy naming scheme, at least not without running intoneozerocool wrote:I encountered same issue - sabnzbd 7.11 fails to repair (actually only rename) files - windows quickpar runs smooth renaming them only.
error info i receive from him is that release is 54 blocks short.
performance issues like 0.7.10 and 0.7.9 did.
With QuickPar you "handfeed" files to the thing, it's not a comparable situation.
Please send the NZB that you have an issue with to [email protected] and add the URL of this message too.
-
- Newbie
- Posts: 2
- Joined: February 11th, 2013, 2:12 pm
Re: Parity repair fails
example was send.
thank You for Your help in this matter.
thank You for Your help in this matter.
Re: Parity repair fails
Yeah, it would be nice to get the dos par.exe to handle these renames automatically as quickpar does, since the whole 'fix' is just to double-click a par, and quickpar automatically finds the issue and does the rename/repair automatically. It seems like a goofy thing that the par.exe should be able to handle.
Re: Parity repair fails
par2 doesn't handle it and QuickPar is totally unsuitable for automatic use.
It's also completely closed source and Windows-only.
BTW: par2 can handle most renaming situations just fine.
Especially the alternatives that we use on Windows and OSX.
It's also completely closed source and Windows-only.
BTW: par2 can handle most renaming situations just fine.
Especially the alternatives that we use on Windows and OSX.