Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[shiny]

Hi,
I have a download, which has only 180KB left. Whenever amule downloads those remaining bytes, it restrats again from 180. ( It looks like this: 180...90...50...20.. 180). It behaves that way 3 days for now.
It's not the first time I have this problem, but previously I solved it by canceling downlodad, and seraching for another similar file. Now I have only so little left that it would be pity to restart.
Does anybody have a clue, what the problem is? I have pleny of space left on partition.

OH, one more thing: amule keeps displaying this message in status bar:

Code: [Select]

AICH-Recovery: AICH successfully recovered 9.10 MB of 9.28 from part 0 for [MyBrokenDownload]

[shiny]

I can't believe nobody encountered this problem before. I guess I'll just have to start over. Again...  ;(

[lionel77]

What you are seeing is that the last part of the file can not be completed because of corruption. One possibility is that someone is consistently sending you corrupted data, another one is that there is something wrong with your local file system.

A friend of mine is experiencing this kind of problem with about 1 out of 3 files, and we have still not been able to figure out why. Eventually, these files finish after he has downloaded about twice their size.

Say, if you look into your log file there should be lines like the following:
2006-08-06 20:53:21: PartFiles: SomeFile.rar: Expected part-hash: ABCD045BB73C8A6D9B94B96A872ED20C
2006-08-06 20:53:21: PartFiles: SomeFile.rar: Actual part-hash: 59C09888EBA4D76A9F5AABBE71ED5655
Are the actual hashes always the same for the same expected hash?

[shiny]

Thanks for information! I have temporarily paused that broken download, because it was getting on my nerves, but as soon as it starts again, I'll post results.

Thanks again.

[shiny]

Good news! The download actually finished. I'm a bit confused, but happy

So, about those hashes: if actual hashes are always the same for same expected ones, that indicates that my fs is OK, and I'm receiving corrupted data. But if they're not the same, it means something is wrong with filesystem?
Or is it just the opposite?

Cheers,

[lionel77]

Originally posted by shiny
So, about those hashes: if actual hashes are always the same for same expected ones, that indicates that my fs is OK, and I'm receiving corrupted data. But if they're not the same, it means something is wrong with filesystem?
Or is it just the opposite?

Well, I guess it depends. If you are downloading the last 180kb of a file from different sources but still always get the same actual part hash, then it seems like it's very unlikely that all those people are actually sending you the identical corrupted data. Instead, it seems more likely then, that there is either a problem with your local file system or that something is going wrong with aMule's hashing of those remaining 180kb.