From: Wols Lists <antlists@youngman.org.uk>
To: David T-G <davidtg-robot@justpickone.org>,
Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: why won't this RAID5 device start?
Date: Sun, 28 Mar 2021 05:36:26 +0100 [thread overview]
Message-ID: <606007CA.7060809@youngman.org.uk> (raw)
In-Reply-To: <20210328021451.GB1415@justpickone.org>
On 28/03/21 03:14, David T-G wrote:
> Hi, all --
>
> I recently migrated our disk farm to a new box with a new OS build
> (openSuSE from KNOPPIX). Aside from the usual challenges of setting
> up the world again, I have a 3-device RAID5 volume that won't start.
> The other metadevice is fine, though; I think we can say that the md
> system is running. Soooooo ... Where do I start?
https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn
Sorry I don't have time to look deeper right now. If someone else
doesn't chime in first, I'll take a look when I get back from work.
Cheers,
Wol
next prev parent reply other threads:[~2021-03-28 3:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 2:14 why won't this RAID5 device start? David T-G
2021-03-28 4:36 ` Wols Lists [this message]
2021-03-28 19:27 ` Wols Lists
2021-03-30 3:13 ` David T-G
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=606007CA.7060809@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=davidtg-robot@justpickone.org \
--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