Originally Posted by RobDog888
Great link Steve., Thanks.
Good news guys. I got the failed drive added to my server on the second try. It was the slave drive in the mirror. Yes, steve, I am running a software raid 1 mirror where each drive is a mirror copy of the other. I have one mirror for my OS and another mirror for my D drive data (dual mirrors consisting of 4 drives). I like mirrors since this is now my 3 HD failure in just over 2 years. I can access all my C drives data now and am going to be copying it over to the server's drive later. At least now I can relax a bit. :) I spent most of the day doing some spring cleaning and stuff. Too tired to really get into all of it right now. I did have a good breakfast, lunch, and dinner. :)
According to my Promise FasTrack utility, it was the secondary drive but as I found from trying to add it to my server it wasnt. It was the primary one that was bad. Whew, dodged a real bad bullet here. This is why I only run RAID Mirrors :D
Looks like there may be a link between defragging and the promise controller but I only use the windows defragger. Seems each of the times I had the hd failures I had done a defrag recently.
Now I need to either look for a replacement of the bad one or 2 new different maybe larger drives ASAP.