LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (http://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   ICP raid controller, no automatic rebuild of raid 5 after replacing bad disk (http://www.linuxquestions.org/questions/linux-newbie-8/icp-raid-controller-no-automatic-rebuild-of-raid-5-after-replacing-bad-disk-775211/)

auclark@wsu.edu 12-12-2009 03:14 PM

ICP raid controller, no automatic rebuild of raid 5 after replacing bad disk
 
Hi;
I have a 5 disk raid 5 array that is composed of SATA A:0,1; SATA B: 0,1, and SATA C:0, and one of the disks (SATA A:0) recently went bad on me. I have an ICP raid controller that is about 5 years old. I replaced SATA A:0. After rebooting, i went into the controller and verified that it saw the disk in the hard-disk info section...there i noticed that in the "status" section, that the SATA C:0, SATA B:1 disks were listed as being "in array", the SATA A disks were blank, and the SATA B:0 disk was listed as "fragment". When I go into the "repair array" section, the controller tells me that there are no arrays that are in failure, error, or need to be rebuilt. This puzzles me, as I thought the controller would know that the array needs to be rebuilt after replacing the disk and I don't see a way to initiate a rebuild.

If i just let the server boot after replacing the disk, then I get back that there are the correct number of disks in the raid 5 and that it is ready, however, the screen then goes blank and i get a blinking cursor and the system seems to hang. There are no activity lights on any of the drives associated with the raid 5, which makes me think that the system is not rebuilding the array at this point.

Any information would be greatly appreciated as I am at the end of my experience level on this one.

Thank you;
Aurora

Quakeboy02 12-13-2009 10:20 AM

Did you add the new disk to the array before trying to repair the array?

auclark@wsu.edu 12-14-2009 08:12 AM

I have never tried to "repair the array" at all, actually. But something automatic may have happened that I am not aware of.

To give you a better timeline, when I first had the disk error and I rebooted the system, the server was able to "recover the journal" with the bad disk intact. After a couple of days, when I got the good disk in from the vender, I rebooted the server and went into the raid configuration utility and see what the serial number was on the bad disk, then i powered the server down again and pulled out the disks to correlate to their SN's. I then rebooted with the bad disk still in the array, b/c i wanted to look more online about what I needed to do once the disk was replaced. The server booted fine, then after about an hour it started throwing out errors and while users could log on, they could not access all or part of their home directories.

At this point, i went back to the server and the interface screen had a bunch of errors on /sda which is where the bad disk was. So, I powered down the server and replaced the disk and that is where I got to the point of my original email, with no rebuild occurring.

A

Quakeboy02 12-14-2009 10:54 AM

Well, it sounds like you have a motherboard RAID aka FAKERAID. If that's the case, go into the BIOS and add the new disk to the array. There should probably be a place to repair the array if adding it doesn't make it go through the repair procedure. It may take a long time, so don't get discouraged and shut it down in the middle of the repair.


All times are GMT -5. The time now is 04:42 PM.