linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Karl Schricker <k_schricker@gmx.net>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Raid5 says it's rebuilding, but it lies :)
Date: Wed, 19 Apr 2006 10:32:21 +0100	[thread overview]
Message-ID: <444603A5.6060806@dgreaves.com> (raw)
In-Reply-To: <17477.37593.650885.214484@cse.unsw.edu.au>

Neil Brown wrote:
> On Wednesday April 19, k_schricker@gmx.net wrote:
>   
>> I have a raid5 configuration with 4 disks, of which all were active.  My
>> system froze due to a separate issue (firewire), so I had to power cycle. 
>> In the past, I've always been able to recover with fsck on /dev/md0, however
>> this time I was not, and I am unable to re-assemble the array now.
>>
>> I'm really hoping someone can help me with this.  I've been googling and
>> reading the mdadm manpage for 3 days and getting nowhere.
>>
>> After booting, I get 3 active disks and one faulty.  Theoretically with
>> raid5 I should be able to recover from this, right? :)  When I add it back
>> to the array, it changes to "spare rebuilding".  However it lies: no Rebuild
>> Status ever shows up (and I let it run overnight).
>>     
>
> Hmmm... there is certainly room for removing confusion from that
> "mdadm -D" is reporting.  However what you want to do it:
>
>  mdadm -S /dev/md0
>  mdadm -A /dev/md0 --force /dev/sd[abd]
>  mdadm /dev/md0 --add /dev/sdv
>   
Typo: this last line should be:

mdadm /dev/md0 --add /dev/sdc
                            ^

David



  reply	other threads:[~2006-04-19  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19  1:04 Raid5 says it's rebuilding, but it lies :) Karl Schricker
2006-04-19  1:31 ` Neil Brown
2006-04-19  9:32   ` David Greaves [this message]
     [not found] <44463EAF.7000901@harddata.com>
2006-04-19 16:44 ` Karl Schricker
2006-04-20  4:37 ` Karl Schricker

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=444603A5.6060806@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=k_schricker@gmx.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).