Subject: Re: configuring raid5 array with raidframe problem..
To: None <firstname.lastname@example.org>
From: Greg Oster <email@example.com>
Date: 09/09/2004 10:12:25
andrej misovic writes:
> Greg Oster wrote:
> > There will almost always be complaints about hosed components and
> > what-not when doing an initial configuration -- the "-C" option says
> > "ignore those errors and configure anyway".
> >>next initialization steps I didn't make,
> >>because I think, it was unnecessary to gone ahead..
> > If you continue on and do the "-I" step, I think you'll find things
> > are working just fine.
> I did that, but it isn't fine..
> here is output from messages:
> Sep 9 17:22:38 /netbsd: raid0: IO Error. Marking /dev/wd3a as failed.
This indicates an error with wd3a. There should be some
indication of the error in /var/log/messages.
What does "disklabel wd3" say?
What does "dd if=/dev/rwd3a of=/dev/null bs=1m count=1" say?
> Sep 9 17:22:38 /netbsd: Unable to correct parity in VerifyParity:
> can't write the stripe
> Sep 9 17:22:38 /netbsd: Could not correct bad parity
> Sep 9 17:22:38 /netbsd: raid0: Error re-writing parity!
> Sep 9 17:23:19 /netbsd: raid0: WARNING: raid0: total sector size in
> disklabel (241254720) != the size of raid (482509312)
> any ideas?
> /when I ran raidctl -iv after that, it just appear on screen and go away
> in few second../
> >> jabber: firstname.lastname@example.org <<
> >> e-mail: email@example.com <<
> // just visit> http://www.nirvanaclub.sk