On Thu, Jul 16, 2009 at 8:56 AM, Siju George <sgeorge...@gmail.com> wrote:
> On Wed, Jul 15, 2009 at 8:41 PM, Greg Oster<os...@cs.usask.ca> wrote: > > You cannot rebuild parity in this case because one of your disks has > > failed (parity re-writing can only happen if all the disks are 'good'). > > If you wish to attempt to rebuild that disk, you can do so > > with: raidctl -vR /dev/wd0d raid0 > > to do a reconstruct-in-place. > > > > Thank you so much Greg for the reply :-) > It worked . > > > Of course, finding out the real reason for why that disk has failed > > should also be on the top of your TODO list :) (e.g. if the disk is > > having physical read/write errors, you proably want to replace it > > before doing the rebuild. ) > > > > Both Disks booted properly when connected individually. any way I am > going to use smartmontools to check disk errors. > > Thanks a lot once again :-) > > --Siju > > If you have a Linux machine available, you could scan the disks with the "badblocks" utility, it is usually good at finding disk errors.
