On 10:38, Jon Nelson wrote: > <4>md: kicking non-fresh sda4 from array! > > what does that mean? sda4 was not included because the array has been assembled previously using only sdb4 and sdc4. So the data on sda4 is out of date. > I also have this: > > raid5: raid level 5 set md0 active with 2 out of 3 devices, algorithm 2 > RAID5 conf printout: > --- rd:3 wd:2 fd:1 > disk 1, o:1, dev:sdb4 > disk 2, o:1, dev:sdc4 This looks normal. The array is up with two working disks. > Why was /dev/sda4 kicked? Because it was non-fresh ;) > md0 : active raid5 sda4[3] sdb4[1] sdc4[2] > 613409664 blocks level 5, 64k chunk, algorithm 2 [3/2] [_UU] > [==>..................] recovery = 13.1% (40423368/306704832) > finish=68.8min speed=64463K/sec Seems like your init scripts re-added sda4. > 65-70KB/s is about what these drives can do so the rebuild speed is just peachy. If the rebuild completes successfully, you're ok again. There's nothing you have to do. Andre -- The only person who always got his work done by Friday was Robinson Crusoe
Attachment:
signature.asc
Description: Digital signature
