Julian Labuschagne writes: > > Then I had to test the server before putting it into a production > enviroment. So I switched of /dev/wd3a.
So at this point wd3a will get marked as failed... > The system halted itself when I did that... "oops". So it wasn't a clean shutdown, and so the parity bits won't have been marked as "clean".... > I started the system started and gave me the following error: > raid0: Error re-writing parity. Right. > When I run the command: raidctl -s raid0 > raid0 Components: > /dev/wd1a: optimal > /dev/wd2a: optimal > /dev/wd3a: failed > Spares: > /dev/wd4a: spare > Parity status: DIRTY > Reconstruction is 100% complete. > Parity Re-write is 100% complete. > Copyback is 100% complete > > I have tried running the following command: > raidctl -P raid0 > raid0: Parity status: Dirty > raid0: Initiating re-write of parity > raid0: Error re-writing parity! > > I'm not sure what is going on here my kernel is standard except for > raidframe support compiled in. I just can't seem to rebuild the array. > > Anybody run into this problem before? Any help would be appreciated. Everything is behaving normally. The system can't make sure the parity is up-to-date because it is missing a component. It is a bit of a mis-nomer to call the parity "DIRTY" at this point because, well, that's the only information you have to go on, and it's as good as it's going to get. But it's been left the way it is so that one can tell if the parity is "known good" or "known questionable"... In any event, 'raidctl -P' isn't going to do anything useful until you get wd3a (or its replacment) added back into the array.... Later... Greg Oster
