It's always better to prevent problems than to try and resolve them when they occur. And one or the primary failure points of a server (or a high-powered workstation) is the storage subsystem. This is because hard drives are mechanical doohickeys that are prone to sudden failure, with either accompanying operating system failure, data loss, or both.

Using RAID storage is supposed to help anticipate such catastrophes by providing a level of fault tolerance for your storage subsystem. But even RAID can have its problems, especially when you use some newer high-capacity hard drives in the near-terabyte range that have less than stellar reputations for reliability. A colleague found this out recently when one of the drives in his RAID 6 array failed after only a year of use. Since RAID 6 provides an extra level of redundancy over RAID 5 and can survive the loss of two drives without data loss, my colleague felt it was safe to contact the manufacturer and request a replacement drive for the one that failed.

Fortunately, by the time the replacement had arrived, no other drive had failed. My colleague then removed what he thought was the failed drive from the RAID array, only to discover he had removed a working drive instead. Now if he had been running RAID 5 at that point, he'd be toast. Fortunately, he was able to resolve the situation by (a) plugging the working drive he had removed back into the array (b) waiting for the array to rebuild the parity info (c) removing the actual failed drive and replacing it with the replacement from the manufacturer and (d) waiting for the rebuild of the second level parity info. Everything worked fine, but he got to bed quite late that night.

What's the solution to avoiding near-disasters like this? Simple: label the drives in your RAID array so you can match them to the ports on your controller card and to drive numbers in your controller's management software. And while you're at it, you may as well label all your drive cables as well, and your drive bays also. A little preventative maintenance like this can be a big time-saver by preventing you from doing something stupid when the heat is on.

ITworld.com

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine