linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Dave Stevens <geek@uniserve.com>, Roger Heflin <rogerheflin@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: no good deed goes unpunished...
Date: Fri, 27 Mar 2015 21:28:02 -0400	[thread overview]
Message-ID: <551603A2.4080808@turmel.org> (raw)
In-Reply-To: <20150327173709.19022q59t5hxh4tx@webmail.uniserve.com>

Hi Dave,

{Convention on kernel.org is reply-to-all, trim quotes, and avoid
top-posting.  Please trim.}

On 03/27/2015 08:37 PM, Dave Stevens wrote:
> # cat /proc/mdstat
> 
> Personalities :
> 
> md12 : inactive   sda2[0](S)
>     732467520 blocks
> 
> md10 : inactive sdc2[2](S) sdb2[1](S)
>     1464935040 blocks

If your livecd tried to be helpful by assembling arrays, but couldn't
complete, you end up with partially-assembled inactive arrays like shown
above.  The member devices shown are *busy*, under the expectation that
the remaining device(s) will show up soon. :-)

As Roger tried to suggest, you need to run:

mdadm --stop /dev/md10
mdadm --stop /dev/md12

That'll release the member devices you need.  However, the device
assembly pairs above look suspicious.  I suggest you show mdadm -E for
those devices again to make sure you work with the correct two disks.
(sda and sdc from the original report.)

Then you can do:

mdadm --assemble --force --verbose /dev/mdX /dev/sdY2 /dev/sdZ2

with the correct substitutions for X, Y, and Z.

If that doesn't work, show the output.

Phil

  parent reply	other threads:[~2015-03-28  1:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 17:33 no good deed goes unpunished Dave Stevens
2015-03-27 18:42 ` Roger Heflin
2015-03-28  0:37   ` Dave Stevens
2015-03-28  0:57     ` Brad Campbell
2015-03-31 21:41       ` Dave Stevens
2015-03-31 21:52         ` Phil Turmel
2015-03-31 21:54           ` Phil Turmel
2015-03-31 23:31             ` Dave Stevens
2015-03-31 21:55           ` Dave Stevens
2015-03-28  1:28     ` Phil Turmel [this message]
2015-03-28  2:14       ` Dave Stevens
  -- strict thread matches above, loose matches on Subject: below --
2015-03-26 23:52 Dave Stevens
2015-03-27  0:04 ` Roger Heflin

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=551603A2.4080808@turmel.org \
    --to=philip@turmel.org \
    --cc=geek@uniserve.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rogerheflin@gmail.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 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).