Print

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

[Lucho[FLCL]]

Hi, it's me again. You may remember me from this thread.

I'm still getting LOTS of corrupted parts for every ~700MB file that I try to download. I have IPFilter enabled and updated, tried to recompile everything, but the problem is still there. Here is some output from the log:

Code: [Select]

2005-06-23 05:30:02: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:30:20: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:30:20: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:30:45: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:30:45: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:31:03: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:31:03: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:31:22: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:31:22: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:31:39: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:31:39: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:31:52: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:31:52: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:32:11: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:32:11: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:32:27: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:32:27: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:32:43: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:32:43: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:33:00: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:33:00: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:33:16: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:33:16: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:33:35: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:33:35: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:33:51: Expected part-hash: F493716D068D458FEF6CDB91ED3141B9
2005-06-23 05:33:51: Actual part-hash: 3261A96E67D31A0EBAFC84B95BD23FC5
2005-06-23 05:33:51: Downloaded part 21 is corrupt in file: XXX.avi
2005-06-23 05:33:52: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:33:52: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:34:08: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:34:08: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:34:26: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:34:26: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:34:44: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:34:44: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:35:00: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:35:00: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:35:33: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:35:33: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:35:58: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:35:58: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:36:37: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:36:37: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:37:12: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:37:13: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
2005-06-23 05:37:45: Expected part-hash: 80C6860A817E14A9CC82A6982ED7AC06
2005-06-23 05:37:45: Actual part-hash: D8930A4F698A0CE63FAB9B877B3CD564
..And it goes on forever
As you can see, the hash for a corrupted chunk is always the same!


I've also checked one hundred times the system's memory with memtest, and tried with 2 different hard disks with no success. I guess that the problem relies somewhere in the function/library that calculates the hashes.

I'm running a 550 Mhz Pentium III, with Gentoo GNU/Linux.


I hope that this time someome can help me! Thanks!

Lucho[FLCL]

[stefanero]

the file is simple currupt,
if it would be a memory or hardware problem then the part which is reported currupt would change, but since its always teh same one, its the file which is brocken

stefanero

[Lucho[FLCL]]

Hi stefanero, thanks for replying. You are always very kind with us mere users .

I have this same problem with EVERY file I download!!! So it cannot be the file...

[Kry]

Wrong. This is the same file on all your log. If aMule expects the same hash for that part, 99% that it's the same file. I would say 100%.

[Lucho[FLCL]]

Hi Kry, thanks to you too for your excellent support.

This was the same file, but if I try to download another file, it happens the same. It happens for EVERY file I try to download!!!


I'm not waiting for some magic answer / solution....just some clue from you, who know better than me how the program works when it calculates hashes, etc ... How to debug it, etc, to try to find which program/part of program is responsible for this failure. Perhaps it's just a corrupted shared lib!

Thanks anyway, you guys rock

[Lucho[FLCL]]

Originally posted by Kry
Wrong. This is the same file on all your log. If aMule expects the same hash for that part, 99% that it's the same file. I would say 100%.

The REALLLY weird thing here is not that aMule expects always the same hash (which is obvious) but that the corrupted chunk has always THE SAME wrong hash!!!!