From: Roman Mamedov <rm@romanrm.net>
To: Stewart Andreason <sandreas41@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid1 show clean but md0 will not assemble
Date: Fri, 8 Mar 2024 03:58:13 +0500 [thread overview]
Message-ID: <20240308035813.22ffb052@nvm> (raw)
In-Reply-To: <f2737b90-fb63-4909-b2d9-496390d2c199@gmail.com>
On Thu, 7 Mar 2024 14:39:17 -0800
Stewart Andreason <sandreas41@gmail.com> wrote:
> $ sudo mdadm --assemble --verbose /dev/md0 /dev/sdc1 /dev/sdd1
> mdadm: looking for devices for /dev/md0
> mdadm: /dev/sdc1 is identified as a member of /dev/md0, slot 0.
> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 1.
> mdadm: added /dev/sdc1 to /dev/md0 as 0 (possibly out of date)
> mdadm: added /dev/sdd1 to /dev/md0 as 1
> mdadm: /dev/md0 has been started with 1 drive (out of 2).
Please include "dmesg" output that's printed after running this command.
> Where are the Last-updated timestamps? Don't they match?
See the "Event" counters, one drive indeed has less than the other. But that
shouldn't be a problem as you use a bitmap and the outdated parts should
simply resync from the other drive.
As for the actual steps, when you are in this state as in your report, I'd try:
mdadm --re-add /dev/md0 /dev/sdc1
But to me it is puzzling why it got removed to begin with.
--
With respect,
Roman
next prev parent reply other threads:[~2024-03-07 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 22:39 raid1 show clean but md0 will not assemble Stewart Andreason
2024-03-07 22:58 ` Roman Mamedov [this message]
[not found] ` <ac42e2cf-b8a0-4072-949e-fe3d0d969f7c@gmail.com>
2024-03-08 0:55 ` Roman Mamedov
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=20240308035813.22ffb052@nvm \
--to=rm@romanrm.net \
--cc=linux-raid@vger.kernel.org \
--cc=sandreas41@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.