[SLL] How to troubleshoot corrupted wget/apt-get/bittorrent file transfers?

[Kurt Buff]

On Mon, Mar 9, 2009 at 16:46, Phil Mocek <pmocek-sll at mocek.org> wrote:
> I've recently noticed a pattern of something that has been
> happening on my Ubuntu Intrepid box since it was running Hardy or
> earlier.  When transferring files from outside my network, using
> wget, aptitude, or deluge (a Bittorrent client), I frequently find
> that the MD5 hash of the file I end up with doesn't match that of
> the original (or in the case of aptitude, dpkg complains of
> corrupted archives).
>
> Clearing apt's package cache and retrying later eventually results
> in getting a good file.  Deluge catches errors and re-transfers
> the bad parts.  Rsync consistently cleans up after a bad wget
> transfer.
>
> There's nothing fishy in the kernel ring buffer.  I'm using
> relatively new SATA drives with a 3Ware 9650 RAID controller.  On
> the array is a dm-crypt volume that contains an LVM PV that is
> allocated to a VG that contains multiple LVs.
>
> How should I troubleshoot this situation?
>
> --
> Phil Mocek

Hmmmm.....

Is this the only machine on your network, and if not, is it the only
machine on your network that's having this problem?

If there are other machines on your network, and they are getting good
downloads, then it's likely that machine that has a problem.

Otherwise, I'd slap wireshark on your box and see what's happening.
I'm no packet guru, but you'll likely see a bunch of errors that you
can track down to a particular piece of equipment.

I'd also like to know more about your network setup. Is it possible
that you have hardware problems in your router/switch/whatever?

But, one of the easiest things to try is a new NIC.

Kurt