4

I have an Asus Sabertooth X79.

I often get corrupted files. I checked the RAM, but memtest finds no errors. To avoid the possibility of disk errors, I tried copying the files to tmpfs.

If I copy from the network, I get md5sum mismatches about once every 10 times using a 6Gb file. Copying from RAM to RAM, I didn't get mismatches.

I get a very high number of errors in ifconfig (compared to others PCs I just took as reference, which have 0 with much more traffic). Here is an example

RX packets:13972848 errors:200 dropped:0 overruns:0 frame:101

The motherboard is new, but do you think there're some problems with it? What could I use to test the (integrated) network adapter? What else do you think I should double check?

--edit--

I tried another NIC, it gives a lot of Corrupted MAC on Input. Disconnecting: Packet corrupt lost connection. I noticed that another PC downloads at 11.1MB/s without problems. This pc at 66.0 MB/s. Is there any way to try to limit the speed?

8
  • 3
    Might be better to ask this in Superuser of Server Fault?
    – TheXed
    Mar 18, 2013 at 14:39
  • Try to plug the computer in another switch/hub port. Did you try replacing the UTP cable? This can be caused by bad RJ-45 connectors. Also check the metallic contacts of your motherboard's female RJ-45 connector. Rusty contacts may cause packet loss. Mar 18, 2013 at 16:20
  • I tried another NIC, it gives a lot of Corrupted MAC on Input. Disconnecting: Packet corrupt lost connection. I noticed that another PC downloads at 11.1MB/s without problems. This pc at 66.0 MB/s. Is there any way to try to limit the speed? Mar 18, 2013 at 16:51
  • 3
    ~12MB/s means a connection speed of 100Mbps. Your PC is connected at 1Gbps, which is more sensible to electric interference and cable/connector quality. Try sudo ethtool -s eth0 speed 100 autoneg off to force a 100Mbps connection. Mar 18, 2013 at 17:02
  • 1
    I would check cables, and switches too.
    – Braiam
    Apr 4, 2014 at 2:55

1 Answer 1

0

You have the right tool with ifconfig - it is showing you the card packet errors.

You've tested correctly by trying another network card, and still getting errors, so eliminating card & driver issues.

So the problem is upstream - faulty switch or cable.

Keep swapping bits one at a time till you find the problem.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .