From: Stewart Andreason <sandreas41@gmail.com>
To: linux-raid@vger.kernel.org
Subject: raid1 show clean but md0 will not assemble
Date: Thu, 7 Mar 2024 14:39:17 -0800 [thread overview]
Message-ID: <f2737b90-fb63-4909-b2d9-496390d2c199@gmail.com> (raw)
Hi, I am new to raid, but have many decades in tech.
I have a raid1 array that was working, but now gives conflicting
information, that I need some help understanding. Searching did not
answer for my specific situation.
I've put all the required output in a file instead of attaching here.:
http://seahorsecorral.org/bugreport/linux-raid-help-form.txt.gz
What confuses me is both drives report clean with mdadm --examine
so it does not look like a typical degraded situation.
I can not see clearly why they are out of sync. Is it timestamps, last
unmounted time, superblocks broken, etc. I would think if something was
altered it would say where that happened. That would get into what I was
doing when it broke, and make a longer story.
Model numbers specs show CMR, not shingled. Problems with portable
shingled drives is what moved me into creating a raid.
sdc is inactive, slot 0, (AA), and is out of date. I guess AA is from
the last time it was written to? So it was turned off in the correct
condition.
sdd is RO degraded mountable, slot 1, and (.A)
That indicates 0 is Missing. I understand missing from the current
array, but... it's right there.
I have set SCT Error Recovery Control to 7 seconds today, After the
problem occurred, so is a detail to be ignored.
I have tried this:
$ sudo mdadm --stop /dev/md0
mdadm: stopped /dev/md0
$ 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).
My questions:
Where are the Last-updated timestamps? Don't they match?
Is the correct way to fix this, to --force OR --delete and --add ?
What exactly would force do?
I can find nothing about what exactly that does. Presumably something
less than a whole disk copy like the 2nd option.
Do I need to --zero-superblock sdc first, without seeing a specific
error regarding the superblocks?
Thank you
next reply other threads:[~2024-03-07 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 22:39 Stewart Andreason [this message]
2024-03-07 22:58 ` raid1 show clean but md0 will not assemble Roman Mamedov
[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=f2737b90-fb63-4909-b2d9-496390d2c199@gmail.com \
--to=sandreas41@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 read-only IMAP folder(s) and NNTP newsgroup(s).