From: Steven Dake <sdake@mvista.com>
To: Eurijk <eurijk@zefga.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid 5 on 2.5.50/2.5.51, dirty array, kernel panic
Date: Wed, 11 Dec 2002 11:31:25 -0700 [thread overview]
Message-ID: <3DF7847D.1050606@mvista.com> (raw)
In-Reply-To: 20021210233443.48053fe3.eurijk@zefga.net
Eurijk
Please run the dump through ksymoops -m System.map. Without this, its
quite difficult to tell where the failure occured.
Thanks
-steve
Eurijk wrote:
>I set up an IDE raid array as such:
> /dev/md1 hda1 hdc1 hde1 hdg1 RAID 1
> /dev/md0 hda2 hdc2 hde2 hdg2 RAID 5
>
>Installed slack, set up lilo, and waited for rebuilding to finish.
>Now to simulate a failure I shut it down and physically unhooked
>(**boom hellfire fury**! :D) /dev/hda. From everything I understand,
>the system should work just fine still.
>
>Bios detects hdc is still there, and auto boots off that. Kernel loads,
>good lilo did it's job :D, but...:
>
>...
>md: created md0
>...
>md: running: <hdg2><hde2><hdc2>
>md: md0: raid array is not clean -- starting background reconstuction
>...
>raid5: device hdg2 operational as raid disk 3
>raid5: device hde2 operational as raid disk 2
>raid5: device hdc2 operational as raid disk 1
>raid5: cannot start dirty degraded array for md0
>RAID5 conf printout:
> --- rd:4 wd:3 fd:1
> disk 1, o:1, dev:hdc2
> disk 2, o:1, dev:hde2
> disk 3, o:1, dev:hdg2
>raid5: failed to run raid set md0
>md: pers->run() failed ...
>md :do_md_run() returned -22
>md: md0 still in use.
>...
>raid1: raid set md1 active with 3 out of 4 mirrors
>...
>md: ... autorun DONE.
>Unable to handle kernel NULL pointer dereference at virtual address 00000088
> printing eip:
>c0289977
>(stack/register dump is here :D)
>...
> <0>Kernel panic: Attempted to kill init!
>
>The "cannot start dirty degraded array" was added in 2.5.34 I believe. I can't
>test a pre 2.5.34 since my 20271 was added in 2.5.37. >;-) I can test it using
>good ol' hda/hdb/hdc/hdd if it would be of some help.
>
>Let me know if I'm off my rocker!
>
>Thanks
>
>-eurijk!
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
>
next prev parent reply other threads:[~2002-12-11 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 7:34 Raid 5 on 2.5.50/2.5.51, dirty array, kernel panic Eurijk
2002-12-11 18:31 ` Steven Dake [this message]
2002-12-12 8:08 ` Eurijk
2002-12-13 20:22 ` Eurijk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3DF7847D.1050606@mvista.com \
--to=sdake@mvista.com \
--cc=eurijk@zefga.net \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).