On Tue, 14 Feb 2006 22:38:23 +0100
Pavel Cahyna <pcah8322@artax.karlin.mff.cuni.cz> wrote:

> On Tue, Feb 14, 2006 at 08:18:05PM +0000, Marcin Jessa wrote:
> > On Mon, 13 Feb 2006 12:01:35 +0100
> > Pavel Cahyna <pavel.cahyna@st.mff.cuni.cz> wrote:
> > > On Mon, Feb 13, 2006 at 11:38:09AM +0100, Marcin Jessa wrote:
> > > > It seems like my RAID1 on two SATA drives was damaged after I
> > > > accidently used reboot instead of shutdown -r. My kernel panics trying
> > > > to read raid drives after boot. The reason I typed reboot was just
> > > 
> > > This should not happen, regardless of reboot...
> > 
> > Yes, I fixed the raid parity with my custom made livecd and still got kernel panic.
> 
> What panic? Maybe the filesystem is corrupted. Try fsck from your livecd.

I have, it seemed healty. I ran raidctl -P raid0 as well since
parity status was marked as DIRTY.
I do not have any debugging info since I installed 3.0 sets 
over the old system directly on the raid.
I updated the system just a while ago and I am back on CURRENT.
I'll let you know if I can reproduce the problem and if 
something like this happens again.


Cheers,
Marcin.