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