From: Phil Turmel <philip@turmel.org>
To: Daniel Sanabria <sanabria.d@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: missing arrays after OS upgrade
Date: Tue, 24 Mar 2015 20:03:07 -0400 [thread overview]
Message-ID: <5511FB3B.8030607@turmel.org> (raw)
In-Reply-To: <CAHscji03jWu3EF0KUG45Hv4Y2t5beJmEoe9uWMfR=wGz_dkBbw@mail.gmail.com>
On 03/24/2015 06:48 PM, Daniel Sanabria wrote:
> Hi,
>
> One of our servers went trough an OS upgrade (from fedora20 to
> fedora21) and althou some of the arrays seem to be auto-detected one
> of them seem to be missing.
You may have had some device names reordered. Building a config that
relies on the names is common but unwise.
With such a thin report, there's not much to go on. Please run lsdrv
[1] and paste its output in a reply.
Then add the contents of /proc/mdstat, the relevant-looking parts of
dmesg, and your mdadm.conf file.
We may need more later, but this will permit intelligent follow-up
questions.
Phil
[1] https://github.com/pturmel/lsdrv
next prev parent reply other threads:[~2015-03-25 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 22:48 missing arrays after OS upgrade Daniel Sanabria
2015-03-25 0:03 ` Phil Turmel [this message]
2015-03-25 11:49 ` Daniel Sanabria
2015-03-25 12:15 ` Phil Turmel
2015-03-27 9:40 ` Daniel Sanabria
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=5511FB3B.8030607@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=sanabria.d@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