We have numerous clients that seem to have the same issue and it's really hurting us. Each of these clients has a TD200 and something called a CRU which is a hot swap removable SATA HDD. This enclosure connects to a PCI card (not PCIe) via a SATA cable. We have tried numerous cards but each one acts the same: When the drive is reinserted and activated for the next day's backup, the network interface goes down. You cannot ping even a gateway. Sometimes you can get the network running again by running a repair on the NIC, other times it requires a full server reboot.
We have this issue on numerous TD200 units, not just one. Our only solution (as a workaround) was to use an eSATA port and go external. Hot swapping in this manner seems to do nothing to the network. We have used the CRU system in countless servers and it has been a workhorse for years. Only with the advent of the TD200 are we having this issue. We have not created this issue in a Windows 2003 Server environment, only 2008, but it happens in both 64bit and 32bit platforms. So we are not sure if it is Operating system-related. We do know that we did not have this issue in our TD100 units.
Here is what we have tried...
1) Different PCI Cards (Siig, Wiebetek, Addonics)
2) New Nic Drivers (Broadcom)
3) New PCI card drivers from the manufacturers
4) Examination and changing of BIOS settings.... noteably, the Thunk Service and 19H interrupt settings in the Legacy area (We have no idea how the thunk service may effect anything)
5) Different Hard drives (sizes and firmware)
If anyone can shed some light on this issue, or have anything else we can try, please let us know as this effects many of our clients. We need help and we'll take anything! Thanks in advance.
