The only solution after trying many suggestions was to simply restart the "vz" service (definitely not preferable). Even doing an ifdown and ifup for venet0 did not help. ifup venet0 Bringing up interface venet0: Configuring interface venet0: net.ipv4.conf.venet0.send_redirects = 0 RTNETLINK answers: Network is down Some errors from log: CPT ERR: d2dc60........

This happened while an mdadm array was syncing, all access from writing a new blank file to opening a small .txt file was very slow: [222117.312078] kjournald starting. Commit interval 5 seconds [222117.685060] EXT3-fs (md0): using internal journal [222117.685096] EXT3-fs (md0): mounted filesystem with ordered data mode [222122.376847] kjournald starting. Commit interval 5 seconds [222122.602825] EXT3-fs (md2): using internal jour........

These were caused by a bad stick of Corsair RAM [] free_hot_cold_page+0xfc/0x150 [] __pagevec_free+0x14/0x1a [] release_pages+0x127/0x12f [] __pagevec_release+0x15/0x1d [] __invalid_mapping_pages+0x120/0x156 [........

I like dd, although it only reads it, usually a read test of the entire disk will uncover if your hard drive is bad in some parts. This is a good thing to do at least once a month, a lot of times bizarre program behavior, laginess and crashing/unnmounting problems etc.. are due to a failing disc and SMART won't know it or indicate a problem: We must also remember there's never a guarantee, I've found that ever since we moved to larger and more platters per drive with 1TB drives........

I think this will be useful to others because I have a server that kept crashing mysteriously during intense disk usage/RAID checks. It would only crash during the weekly RAID integrity check. ThenI noticed during a reboot that not all CPUs were being brought up, as a result this actually creates much higher temperatures with the output I got from sensors, just booting the system produced higher than normal temperatures. You can imagine that a full blown RAID check........