linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: James Lee <james.lee@cantab.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 array showing as degraded after motherboard replacement
Date: Tue, 07 Nov 2006 13:00:32 -0500	[thread overview]
Message-ID: <4550C9C0.7060705@tmr.com> (raw)
In-Reply-To: <ef2613f30611050858m562386a0m7966667f803f35fc@mail.gmail.com>

James Lee wrote:

> Hi there,
>
> I'm running a 5-drive software RAID5 array across two controllers.
> The motherboard in that PC recently died - I sent the board back for
> RMA.  When I refitted the motherboard, connected up all the drives,
> and booted up I found that the array was being reported as degraded
> (though all the data on it is intact).  I have 4 drives on the on
> board controller and 1 drive on an XFX Revo 64 SATA controller card.
> The drive which is being reported as not being in the array is the one
> connected to the XFX controller.
>
> The OS can see that drive fine, and "mdadm --examine" on that drive
> shows that it is part of the array and that there are 5 active devices
> in the array.  Doing "mdadm --examine" on one of the other four drives
> shows that the array has 4 active drives and one failed.  "mdadm
> --detail" for the array also shows 4 active and one failed.
>
> Now I haven't lost any data here and I know I can just force a resync
> of the array which is fine.  However I'm concerned about how this has
> happened.  One worry is that the XFX SATA controller is doing
> something funny to the drive.  I've noticed that it's BIOS has
> defaulted to RAID0 mode (even though there's only one drive on it) - I
> can't see how this would cause any particular problems here though.  I
> guess it's possible that some data on the drive got corrupted when the
> motherboard failed... 

I notice in your later post that the driver thinks this is a JBOD setup, 
can you either tell the controller to JBOD or force the driver to 
consider this a RAID0 single disk setup? I don't know what RAID0 on one 
drive means, but I suspect that having the controller in the mode you 
want is desirable. That might have been changed in the hardware failure.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979



      parent reply	other threads:[~2006-11-07 18:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-05 16:58 RAID5 array showing as degraded after motherboard replacement James Lee
2006-11-05 21:02 ` dean gaudet
2006-11-06  0:07   ` James Lee
2006-11-06  8:29     ` dean gaudet
2006-11-07  0:18       ` James Lee
     [not found]         ` <ef2613f30611071715q2a6776eaya219349d667b43b1@mail.gmail.com>
2006-11-08  1:16           ` James Lee
2006-11-08  7:52             ` dean gaudet
2006-11-07 18:00 ` Bill Davidsen [this message]

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=4550C9C0.7060705@tmr.com \
    --to=davidsen@tmr.com \
    --cc=james.lee@cantab.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).