I have a custom sbs server that is giving me some strange issues.
Here is the server configuration:
Motherboard: Supermicro X8DTL-iF
CPU: 2 x Xeon E5620
RAM: 6 x 4096 DDR3 Buffered ECC
Network: 2 x Onboard Intel 82574L Gigabit NIC
Storage: 2 x 60GB OCZ Vertex 2 RAID via Intel Matrix RAID
OS: Server 2008 SBS Standard
Here is the issue I am having:
The system will run fine for days or even months without issue, but when the issue occurs the server becomes completely disconnected from the network. The server is not locked-up, but investigating the issue with local access shows both NICs are 'disabled'. I cannot manually enable them. The only remedy is to restart the operating system, doing so cause the NICs to show connected at reboot and the problem is resolved. Reviewing the event logs shows multiple information events from 'e1qexpress' with event ID '56'. They start at a specific time (no doubt when issue begins) and are logged about every 2 seconds until the system is restarted. There are no other events in System or Application logs that indicate trouble.
Oddly enough, the last time this occured (today), there was an event logged from 'iaStor' with event ID '9' that said "The Device, \Device\ide\iaStor0, did not respond within the timeout period". The Intel Matrix storage manager indicated the RAID1 volume was degraded. After restarting the system to fix the error with the network I ran an integrity verification task via the Matrix storage manager on the array twice without error. The array shows as healthy.
I'm not sure what the problem could be. The network, chipset, video drivers, and OS are all up to date. The server is on a power regulator and backup, so I don't think it could be power fluctuations. Could it be power spikes feeding into the network via the Nortel switch the system is attached to? Could the motherboard or chipset be failing?
The second LAN connection is unused, and it had been manually disabled in device manager. Today, I enabled it, but disabled all services and protocols for it in properties. That is all I can think of, that maybe the driver get's "confused" because the one connection is disabled and it screws up the other connection. Time will tell if this remedies the issue.