All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricky Burgin <ricky@burg.in>
To: Sam Bingner <sam@bingner.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdraid autodetect partially failing after disk replacement
Date: Fri, 10 May 2013 05:52:59 +0100	[thread overview]
Message-ID: <8tj2wq0eu1swie7m884u2d8i.1368161579257@email.android.com> (raw)

Hi Sam,

Thanks for the response. Unfortunately that's not the case, that was one of the first things I checked. What variables are considered when adding or excluding drives to or from a raid via autodetection? This problem feels so esoteric that it might just be a bug... 

I'll keep on trying!

Ricky

Sam Bingner <sam@bingner.com> wrote:

>On May 8, 2013, at 3:20 PM, Ricky Burgin <ricky@burg.in> wrote:
>
>> Hello again,
>> 
>> Little bit of progress since I last dropped a message in (sorry for the
>> duplicate, didn't think the initial one got through).
>> 
>> The kernel has mdraid built into it and all disks are using 0.90
>> superblocks, all 'fd' partitions, but only 2 or 4 disks are being
>> recognised and applied to the freshly created raid array which works
>> fine when mounted on any other OS.
>> 
>> Any suggestions for what could cause disks to be overlooked by mdraid
>> before the root device is even attempted to be mounted would be very
>> helpful, I'm now totally at a loss as to what to do from here.
>> 
>> Kind regards,
>> Ricky Burgin
>> --
>> 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
>
>Is it possible that you still have 1.x superblocks on two drives that are being detected before the 0.9 superblocks on this OS?  I don't know if this is or is not possible, but that is the only strangeness I see from your prior posts etc.
>
>You should probably boot that version of CentOS's rescue mode and see if you have the same issues there... 
>
>Sam

             reply	other threads:[~2013-05-10  4:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10  4:52 Ricky Burgin [this message]
2013-05-10  5:52 ` mdraid autodetect partially failing after disk replacement Tregaron Bayly
  -- strict thread matches above, loose matches on Subject: below --
2013-05-09  1:20 Ricky Burgin
2013-05-10  4:08 ` Sam Bingner

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=8tj2wq0eu1swie7m884u2d8i.1368161579257@email.android.com \
    --to=ricky@burg.in \
    --cc=linux-raid@vger.kernel.org \
    --cc=sam@bingner.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.