From: Marc Widmer <metafor@gmail.com>
To: linux-raid@vger.kernel.org
Subject: raid md126, md127 problem after reboot, howto fix?
Date: Sun, 08 Feb 2015 20:03:51 +0100 [thread overview]
Message-ID: <54D7B317.5010809@gmail.com> (raw)
Hi List
I have no deep unterstand about raids, beside setting them up initially and
replacing disks if needed. So this error has never happened to me before:
After a reboot i have a really strange behaviour on my server. Disks are
not marked faulty, but raid is "fallend apart".
/proc/mdstat shows me:
md126 : active raid1 sda1[0]
10485696 blocks [2/1] [U_]
md127 : active raid1 sda2[0]
721558464 blocks [2/1] [U_]
md1 : active raid1 sdb1[1]
10485696 blocks [2/1] [_U]
md2 : active raid1 sdb2[1]
721558464 blocks [2/1] [_U]
wished would be something similar to:
md1 : active raid1 sdb1[1] sda1[0]
10238912 blocks [2/2] [UU]
md2 : active raid1 sdb2[1] sda2[0]
1942746048 blocks [2/2] [UU]
Currently only md1, md2 are running. nmon shows me, that only disks sdb is
active, sda is not doing anything.
I run debian squeeze.
I am a bit concerned what to do, because at the moment i run on one disk
only and if things go wrong i end up with a server not running (downtime)
and possible data loss (beside backups).
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?
Any help would be greatly appreciated as by now the only thing i had to do
was resyncing a disk after usual hd crash.
Best
marc
next reply other threads:[~2015-02-08 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 19:03 Marc Widmer [this message]
2015-02-08 21:29 ` raid md126, md127 problem after reboot, howto fix? 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
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=54D7B317.5010809@gmail.com \
--to=metafor@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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).