Why do we have corrupted files?

Asked by Emanem


yesterday, after downloading 6.6 GB of data, the RARs from 0 to 29 were ok, from 30 to 64 were all corrupted.
I've opened the offending archives and apparently they were truncated (all began with proper RAR header etc etc).
Why do we have such issues when downloading binary info from news servers?
I mean, they do work with TCP/IP, the same connection as in http, and I've downloaded ISOs from http without any corruption.

What is the reason behind this happening with LottaNZB/HellaNZB/NNTP ?

Doesn't HellaNZB have an automated mechanism to know when a truncated binary has been downloaded and re-download it?


Question information

English Edit question
LottaNZB Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Severin Heiniger (severinh) said :

I'm afraid that I cannot answer your question. HellaNZB apparently doesn't have a mechanism to detect truncated binaries. What I suggest you to do is to use another NNTP client and check if it also happens. This would allow you to rule out (or not) HellaNZB as a potential cause for your problem.

Revision history for this message
Emanem (emaentra) said :

Thanks mate, I'll have a go with NZBget and see what happens.

Can you help with this problem?

Provide an answer of your own, or ask Emanem for more information if necessary.

To post a message you must log in.