From: Sebastian Parschauer <sebastian.riemer@profitbricks.com>
To: Wols Lists <antlists@youngman.org.uk>,
Marc Widmer <metafor@gmail.com>,
linux-raid@vger.kernel.org
Subject: Re: raid md126, md127 problem after reboot, howto fix?
Date: Mon, 09 Feb 2015 11:33:53 +0100 [thread overview]
Message-ID: <54D88D11.4040207@profitbricks.com> (raw)
In-Reply-To: <54D88A7A.4000207@youngman.org.uk>
On 09.02.2015 11:22, Wols Lists wrote:
> On 09/02/15 09:55, Sebastian Parschauer wrote:
>>>> Any ideas what i should do? Howto put the raid back together, possibly in
>>>> live mode, without rebooting in rescue mode and risk long downtime?
>> Just stop all arrays which aren't in use at the moment and assemble them
>> manually. If they are already running degraded, then add the now
>> unassociated disks to their respective running arrays.
>>
>> $ mdadm --stop /dev/md126
>> $ mdadm --stop /dev/md127
>> $ mdadm /dev/md1 --add /dev/sda1
>> $ mdadm /dev/md2 --add /dev/sda2
>>
>> This could require some syncing but then everything should be normal again.
>
> This isn't just a Debian/Ubuntu problem - I run gentoo.
Okay.
> And isn't there a re-add option? That will hopefully just require a
> recovery rather than a total resync.
Yes, sure, --re-add should be tried first. If it doesn't work, then the
--add option will definitely work.
Cheers,
Sebastian
prev parent reply other threads:[~2015-02-09 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 19:03 raid md126, md127 problem after reboot, howto fix? Marc Widmer
2015-02-08 21:29 ` Wols Lists
2015-02-09 9:41 ` Sebastian Parschauer
2015-02-09 9:55 ` Sebastian Parschauer
2015-02-09 10:22 ` Wols Lists
2015-02-09 10:33 ` Sebastian Parschauer [this message]
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=54D88D11.4040207@profitbricks.com \
--to=sebastian.riemer@profitbricks.com \
--cc=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=metafor@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).