linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul <ocran@gmx.net>
To: linux-raid@vger.kernel.org
Subject: promise reconstruction problem raid1
Date: Fri, 05 Sep 2003 11:09:58 -0400	[thread overview]
Message-ID: <3F58A746.8010004@gmx.net> (raw)

Hello,
I have a raid 1 array, that has a fialed disk. I have repleaced the 
disk, and duplicated it with the promise fasttrack program. But when i 
boot my system, kernel 2.4.19 complains:
During boot, when the kernel is listing the arrays, it states that only 
one disk is in the array, when in fact there are two. Then it says code: 
Bad EIP value, and the warning fsck.ext3 for device /dev/ataraid/d1p1 
exited with signal 11. It then tells me to repair manually. Cuuld this 
possibly be a bad superblock? I am quite confused, and have tried 
several things. I have compiled different versions of the kernel, from 
2.4.18 to 2.4.21 but i have the same problem with all of them. I have 
even tried to compile them on another machine, still no luck. Has anyone 
succesfully done this?

Thanks,

Paul


                 reply	other threads:[~2003-09-05 15:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F58A746.8010004@gmx.net \
    --to=ocran@gmx.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).