At work we have a computer that is only used as a router, DHCP server, and Ghost server. All it does it hold ghost file images, hand out the images to clients that request them, and route the internet to those systems after they have the image.
Lately, this computer has been locking up - but ONLY when the HD is being accessed. I can leave it for a week running SETI and it won't lock up once - but if it's handing out an image to a computer, it will commonly pause for a few seconds, then go, then pause again, then go again, until it completely locks up. The System log will be filled with errors that baseically say "Atapi did not respond within the timeout period".
The computer is a Compaq Evo W6000 workstation, running 2003 Server.
At first, I assumed the HD must be failing. I replaced it with a new HD just yesterday, and after reinstalling the OS, the problem persists. My next thought was the IDE drivers. Naturally, I tried multiple IDE drivers. At first, I was using the Intel ones - but out of desperation I've even gone back to "Standard Dual Channel IDE Controller"; the generic windows one. This error persists.
I've tried the HD on the primary AND secondary IDE controllers as well; problem is there no matter which one I use.
ALSO I have tried more than one IDE cable.
I'm out of ideas at this point. Does anyone have any other things I could try? I'm about to get a PCI IDE controller and plug that in, to see if the problem will go away if I get it off the motherboard's IDE bus.
Lately, this computer has been locking up - but ONLY when the HD is being accessed. I can leave it for a week running SETI and it won't lock up once - but if it's handing out an image to a computer, it will commonly pause for a few seconds, then go, then pause again, then go again, until it completely locks up. The System log will be filled with errors that baseically say "Atapi did not respond within the timeout period".
The computer is a Compaq Evo W6000 workstation, running 2003 Server.
At first, I assumed the HD must be failing. I replaced it with a new HD just yesterday, and after reinstalling the OS, the problem persists. My next thought was the IDE drivers. Naturally, I tried multiple IDE drivers. At first, I was using the Intel ones - but out of desperation I've even gone back to "Standard Dual Channel IDE Controller"; the generic windows one. This error persists.
I've tried the HD on the primary AND secondary IDE controllers as well; problem is there no matter which one I use.
ALSO I have tried more than one IDE cable.
I'm out of ideas at this point. Does anyone have any other things I could try? I'm about to get a PCI IDE controller and plug that in, to see if the problem will go away if I get it off the motherboard's IDE bus.
Facebook
Twitter