I have a fairly new server ( <3 months old) that seems to drop a drive out of the RAID 5 configuration every once in a while. This has happened twice so far - close to once a month. The sever is all Intel server board SE7520BD2V. The RAID controller is SRCS28X and I'm running 5 x 250GB Seagate drives in a RAID 5 with one hot spare (total 6 drives in the sever). It came pre-installed with Windows Server 2003 SBS - which I had to re-install - including loading the RAID controller driver from CD.
The first time a drive "fell" out of the array, the hot spare immediately took it's place and began a rebuild. I got on the phone with Intel tech support - drive 5 showed that it was not in the array - nor a hot spare. With their utility, I identified drive 5 and according to Intel's tech, pulled it out of the server. The sever blue-screened and shut down. We went into the BIOS version of the utility and were able to add the drive back into the array (big whew!). Anyway, I tell this because the drives do not identify where they should be. Drive 0 identifies as drive 1 and drive 1 as drive 0. 2 and 3 are swapped and 4 and 5 are swapped. So now they're labled correctly on the outside of the server. I haven't had a chance to verify yet, but I'll be the back plane is mis-wired. So, do I want or need to fix this??? If I change the cables and also change the drives, do I run the risk of losing the array? This is a production server in a small company, so it's very bad when it's down.
The second time when a drive "fell" out of the array (about a month later), I just let the spare rebuild. The one then showed ready, and I added it back in a the new hot spare. It did have a media error of 113, but the Intel techs don't know what the media error codes mean. Right now the server seems to be running fine, but if you watch the drive lights, they all go out every few minutes and come back on one by one. Would the mis-cabling cause these problems???
Has anyone ever seen this type of behavior or have suggestions on how to proceed???