linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: NeilBrown <neilb@suse.de>
Cc: John Valarti <mdadmuser@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Server down-fail​ed RAID5-asking for some assistance
Date: Sun, 24 Apr 2011 12:57:56 +0100	[thread overview]
Message-ID: <4DB41044.5020404@anonymous.org.uk> (raw)
In-Reply-To: <20110424184130.1692bce5@notabene.brown>

On 24/04/2011 09:41, NeilBrown wrote:
> On Sun, 24 Apr 2011 01:06:52 -0600 John Valarti<mdadmuser@gmail.com>  wrote:
[...]
>> Here you go. I warn you it is a bit long!
>
> Thanks.  Length is no problem.
>
> Only it doesn't make sense at all.  I cannot see how mdadm would possibly be
> generating just those messages.
> It appear to be rejecting each device for some reason, but it not reporting
> why it is rejecting the device...
>
> What version of mdadm is this?
>     mdadm --version
>
> I should have asked that before.

I think John said 2.6.9 on the CentOS 5.5 rescue media. I think it's 
time to try something more recent: John, could you try SystemRescueCD 
from http://www.sysresccd.org/ and run
   mdadm -Evvs
and if that shows your RAID5 members again,
   mdadm -Afvv /dev/md1

Cheers,

John.


  reply	other threads:[~2011-04-24 11:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 18:29 Server down-fail​ed RAID5-asking for some assistance John Valarti
2011-04-21 19:59 ` David Brown
     [not found]   ` <BANLkTim18Sx6JdZO5PiAqnrakDPzy5PNJQ@mail.gmail.com>
2011-04-22  2:32     ` John Valarti
2011-04-22  2:57       ` Server " NeilBrown
2011-04-22  3:31         ` John Valarti
     [not found]         ` <BANLkTin0SoBzRAear8Jt+26MnVJWouXoNA@mail.gmail.com>
     [not found]           ` <20110423074411.78fef94f@notabene.brown>
     [not found]             ` <BANLkTik_ZY4uoV3E=ua1p+tUD9g8xqQDVg@mail.gmail.com>
     [not found]               ` <20110423184824.55ee7893@notabene.brown>
     [not found]                 ` <BANLkTi=sCfFFfmZTzj2g8-aDNhDqVK8e-A@mail.gmail.com>
     [not found]                   ` <20110424075101.6763309f@notabene.brown>
2011-04-24  0:07                     ` John Valarti
2011-04-24  0:37                       ` John Robinson
2011-04-24  1:49                         ` John Valarti
2011-04-24  2:12                           ` John Robinson
2011-04-24  2:28                             ` John Valarti
2011-04-24  2:58                               ` NeilBrown
2011-04-24  6:30                                 ` John Valarti
2011-04-24  2:54                       ` NeilBrown
2011-04-24  7:06                         ` John Valarti
2011-04-24  8:41                           ` NeilBrown
2011-04-24 11:57                             ` John Robinson [this message]
2011-04-24 12:29                               ` NeilBrown
2011-04-24 16:04                                 ` John Valarti
2011-04-24 16:15                                   ` John Valarti
2011-04-24 16:31                                     ` Mathias Burén
2011-04-24 18:41                                       ` John Valarti
2011-04-22 11:19       ` David Brown

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=4DB41044.5020404@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=mdadmuser@gmail.com \
    --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).