Do you see anything in the log? SCSI parity error, for example? With three identical drives on the same controller, that rules out a lot of issues that could arise. If you are seeing the same drive being marked bad over and over, and it takes days for that to happen, I would look at (1) termination, (2) heat, and (3) power supply problems, in that order. An interesting test would be to interchange the failing drive with either of the other two in terms of physical position along the SCSI bus cable, keeping its PUN (ID) and data unchanged. If the problem moves to a new drive or goes away entirely, that would suggested termination or heat. -- Mike On Fri, 7 Apr 2000 [EMAIL PROTECTED] wrote: > Background: > > This system have been very stable for 8 months. At xmas, we > upgraded to 2.2.14 and the newest raid patches. > > Problem: > > on the /dev/md2 raid volume, the /dev/sdb3 partition keeps getting > marked as failed. This happens consistently after about 1.5-2 days of use. > /dev/md2 is where I mount /usr/local on this system, which houses apache > and openldap, so I don;t think it is a cron job, or burst of activity that > marks it bad. > > When /dev/sdb3 is marked bad, I unmount /usr/local, raidhotremove > /dev/sdb3 from /dev/md2 and then fsck /dev/sdb3. The drive fsck's fine, so > I raidhotadd /dev/sdb3 /dev/md2 and watch /proc/mdstat to make sure it is > rebuilding. /dev/md2 rebuilds itself marks everything clean ( ie:[UUU]), > and proceeds to run for a couple of days and then seems to get marked as > failed: > > md2 : active raid5 sdb3[0](F) sdd3[2] sdc3[1] 1435392 blocks level > 5, 128k chunk, algorithm 2 [3/2] [_UU] > > > I don't know what the issue is. My suspicion is that I have a > hardware issue with /dev/sdb, but before I go out and buy new drives to > replace these existing ones I wanted to know if anyone had the > same/similar issues.
