Discussion Locked

Mirrored Drive

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a mirrored drive that was running on a Win NT server w/Service pack 4 installed. The problem started when we noticed that the CPU using was continuously running 80-95%. When Disk Administration was opened it showed that the C: mirror was broken and the D: mirror was initializing. Once the drive used as the mirror was removed the CPU usage ran at a normal level. A new drive was purchased and when we tried to establish the mirror for these drives it showed the drive initializing (CPU usage levels high) this continued for a couple of hours before we removed the drive to regain normal CPU usage levels. This drive does work without the mirror setup. I am in the process of verifying that the first drive works in another system. The drives are fujitsu IDE drives they are running on the same ribbon cable and are configured in a master slave setup. The mirror setup did work on this system for about 1.5 years prior to this. If you have any helpful suggestions I am open to them.

Thanks
Rod

5 replies

by coolflip

Hello Rod,

Hmm..sounds like a conflicting resource. Was there an additional hardware installed to the server? Check your resources with system diagnostics to see if there is a resource that isn't supposed to be there.

Coolflip

by rodneywambold

I accepted this answer because it provided me with options to eliminate possible problem areas. The solution was to leave the drive in for a longer period of time allowing the mirror to complete the mirroring process. Thank you for your response.

by craig haunch

Rod,

Sounds like the first mirror had a faulty disk (d:) and you have done the correct thing by replacing it but I was curious to find you'd removed the new one because of the CPU usage. Depends on how big the drives are but the bigger the drivethe longer it takes to mirror and it does put the CPU usage up to high levels while doing the mirror. I would put the new drive back in last thing before you go home, set the mirror going and then when you come in the morning it should have finished and the cpu usage back to normal. If it is not then it could be the c drive that has a fault, runs ok on it's own but when trying to mirror it is picking up the fault. Give it a go and see what happens.

by rodneywambold

Thank you for your response. I did leave the drive in for a longer period of time and the mirror set registered as healthy after running for a couple of hours. When I replaced the drive the first time I was concerned about the processor running at that high of a level. I had to replace the processor when I was called in to troubleshoot the server blue screening. I didn?t want that to happen again. Again thank you for your response.

This discussion is closed to new replies.