All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <brad@fnarfbargle.com>
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: Sat, 28 Mar 2015 08:57:42 +0800	[thread overview]
Message-ID: <5515FC86.7030402@fnarfbargle.com> (raw)
In-Reply-To: <20150327173709.19022q59t5hxh4tx@webmail.uniserve.com>

md12 has claimed sda2 and md10 has sdb&c. Try this

mdadm --stop /dev/md12
mdadm --stop /dev/md10
mdadm --assemble --force /dev/md13 /dev/sd[abc]2



On 28/03/15 08:37, Dave Stevens wrote:
> Quoting Roger Heflin <rogerheflin@gmail.com>:
>
>> I don't know what to make of it.
>>
>> Everyone will ask you for this info:
>> mdadm --examine /dev/sdc2              and the same output against
>> /dev/sdb2
>
> ok, like this:
>
> # cat /proc/mdstat
>
> Personalities :
>
> md12 : inactive   sda2[0](S)
>      732467520 blocks
>
> md10 : inactive sdc2[2](S) sdb2[1](S)
>      1464935040 blocks
>
> unused devices: <none>
>
>
> ------------------------------ reboot ----------------------
>
> # mdadm -A /dev/md13 /dev/sdb2 /dev/sdc2
>
> mdadm : /dev/md13 assembles from 1 drive - not enough to start the array
>
> # cat /proc/mdstat
>
> Personalities :
>
> md13 : inactive sdc2[2](S) sdb2[1](S)
>
>      1464935040 blocks
>
> unused devices : <none>
>
> # mkdir aa
>
> # mount /dev/md13 aa
>
> mount: /dev/md13: can't read superblock
>
>
> Dave
>
>
>
>
>>
>> On Fri, Mar 27, 2015 at 12:33 PM, Dave Stevens <geek@uniserve.com> wrote:
>>> From:   Roger Heflin <rogerheflin@gmail.com>
>>> To:     Dave Stevens <geek@uniserve.com>
>>> Cc:     Linux RAID <linux-raid@vger.kernel.org>
>>> Subject: Re: no good deed goes unpunished...
>>> Date:   Thu, 26 Mar 2015 19:04:45 -0500
>>> Sender: linux-raid-owner@vger.kernel.org
>>>
>>> you should probably do cat /proc/mdstat
>>>
>>> It is likely that the livecd may have already tried to assemble it,
>>> and that the busy is because it is already in use.
>>>
>>> If it is already assembled and you want to redo it first you will need
>>> to stop the assembled array to be able to redo it.
>>>
>>> so this is what I did while running the live distro:
>>>
>>> # cat /proc/mdstat
>>>
>>> Personalities :
>>>
>>> md12 : inactive   sda2[0](S)
>>>         732467520 blocks
>>>
>>> md10 : inactive sdc2[2](S) sdb2[1](S)
>>>         1464935040 blocks
>>>
>>> unused devices: <none>
>>>
>>>
>>> It seemed to me that matters were needlessly complicated by possible
>>> residual issues from my earlier unsuccessful attempts so I rebooted.
>>>
>>>
>>> ------------------------------ reboot ----------------------
>>>
>>> # mdadm -A /dev/md13 /dev/sdb2 /dev/sdc2
>>>
>>> mdadm : /dev/md13 assembles from 1 drive - not enough to start the array
>>>
>>> # cat /proc/mdstat
>>>
>>> Personalities :
>>>
>>> md13 : inactive sdc2[2](S) sdb2[1](S)
>>>
>>>         1464935040 blocks
>>>
>>> unused devices : <none>
>>>
>>> # mkdir aa
>>>
>>> # mount /dev/md13 aa
>>>
>>> mount: /dev/md13: can't read superblock
>>>
>>> So I still don't see what to do. Advice welcome.
>>>
>>> Dave
>>>
>>>
>>>
>>> --
>>> "As long as politics is the shadow cast on society by big business,
>>> the attenuation of the shadow will not change the substance."
>>>
>>> -- John Dewey
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 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
>> --
>> 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
>>
>
>
>


-- 
Dolphins are so intelligent that within a few weeks they can
train Americans to stand at the edge of the pool and throw them
fish.

  reply	other threads:[~2015-03-28  0:57 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 [this message]
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
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=5515FC86.7030402@fnarfbargle.com \
    --to=brad@fnarfbargle.com \
    --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 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.