Joeteck
Retired
- Joined
- Oct 5, 2001
- Location
- Long Island
- Thread Starter
- #21
I still don't believe that, the fact you were able to just make a copy of the array no problem but it kept locking up on boot. I've been working with raid and controllers for many many years and the situation you described is 99% of the time bad controller ram.
Did you check smart status on those drives and run diags on them?? Its rare for enterprise drives to fail that quickly, and all enterprise drives do a KILLER good job of reporting problems, perhaps the monitoring you were in control of was inadequate.
Life as a administrator
Well, guess what, your wrong! Know how I know? I have no RAM on the controller. hahaha!
I've been working with RAID & controllers for many years too... 18 years as a network administrator to be exact and the President / CEO of my own PC repair company.
I don't have time to check the status of the drives when my goal is to get the server up and running. Incidentally it took four hours to do so... The drives have major issues... They already have an RMA number and ready to be replaced in a few weeks.
When I ran Diskeeper and analyzed the array it took about 15 seconds to display. Normally a nanosecond! And when I clicked to defrag, that's when it froze, because its trying to keep the mirror intact. Since it could not write to the other disk, it locked up. One disk was ok and booted into windows slowly, but still had issues.. So before I could not boot any longer, I chose to image the drive before I lose the entire server...