From: Phil Turmel <philip@turmel.org>
To: "Neil ." <neil.perrie@gmail.com>,
Emery Guevremont <emery.guevremont@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Lost raid 5 volume
Date: Sun, 14 Dec 2014 11:23:30 -0500 [thread overview]
Message-ID: <548DB982.7010503@turmel.org> (raw)
In-Reply-To: <CADhQzuo57BoMT_fLVHd=ufGR6ztSFaRqsRLZtFSwvii+YzAcLQ@mail.gmail.com>
Good morning Neil,
[Etiquette on kernel.org is to trim replies and either bottom-post or
interleave.]
On 12/13/2014 11:30 PM, Neil . wrote:
> smartctl says Overall health...: passed for all drives.
This is good, but not relevant. Lots of desktop drives will report this
even though they are part of the problem. Please show the complete
output of "smartctl -x" for the two troublesome drives. Maybe also for
the other two.
> Update Time : Sat Dec 6 14:00:02 2014
> Events : 3
> Update Time : Sat Dec 6 14:00:02 2014
> Events : 3
> Update Time : Sun Dec 7 11:18:06 2014
> Events : 8
> Update Time : Sun Dec 7 11:18:06 2014
> Events : 8
This looks strange. It suggests that the two drives failed well before
your reboot. If you have dmesg from Saturday afternoon, that might be
enlightening.
However, as a raid 5, you are stuck unless you include at least one of
the two stale drives. The correct tool for this is forced assembly:
mdadm --assemble --force --verbose /dev/mdX /dev/sd[abcd]2
If it fails, show its output.
Whether it fails or not, you need to investigate why the drives were
dropped. Simultaneous drops suggest a hardware problem.
Phil
next prev parent reply other threads:[~2014-12-14 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-13 0:48 Lost raid 5 volume Neil .
2014-12-14 0:06 ` Emery Guevremont
2014-12-14 4:30 ` Neil .
2014-12-14 16:23 ` Phil Turmel [this message]
[not found] ` <CAB_L8sYNbdDnWCDwiyAmH+73J67o6dBy0G3QBsYTsPA-my6atg@mail.gmail.com>
[not found] ` <CADhQzurRYoJJcM2yephWeyyEdTy8XsRROZP400i7UdYPeYXTzA@mail.gmail.com>
[not found] ` <CAB_L8sbo3SDUjch-kqFi3wZduQ2tcTSvs4MSabSLYodg7duahw@mail.gmail.com>
[not found] ` <CADhQzuos53RXQZpxepWG7v6dAc9EMseDYx4PbuXjj+4nSnCkJQ@mail.gmail.com>
[not found] ` <CAB_L8saPqvR8HjqBFUvK+10H4Nou_yOrby5iPFkeiSiNj=RSww@mail.gmail.com>
2014-12-15 13:37 ` Neil .
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=548DB982.7010503@turmel.org \
--to=philip@turmel.org \
--cc=emery.guevremont@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neil.perrie@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.