From: RJ Marquette <rjm1@yahoo.com>
To: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Requesting help recovering my array
Date: Wed, 24 Jan 2024 00:59:56 +0000 (UTC) [thread overview]
Message-ID: <804226557.24031.1706057996425@mail.yahoo.com> (raw)
In-Reply-To: <c520a673-9b61-448c-999d-7e1b0b57c098@penguinpee.nl>
That's an interesting theory. I did update Debian a few days ago and hadn't rebooted before the hardware upgrade. So it might not have anything to do with the hardware upgrade. That would make a lot more sense.
When you say manually, is that adding the devices to the conf file then running mdadm --assemble?
Thanks.
--RJ
On Tuesday, January 23, 2024 at 06:00:32 PM EST, Sandro <lists@penguinpee.nl> wrote:
On 23-01-2024 17:16, RJ Marquette wrote:
> It's like mdadm was assembling them automatically upon bootup, but that
> stopped working with the new motherboard for some reason.
Just a hunch, since you wrote that you updated your system as well:
https://bugzilla.redhat.com/show_bug.cgi?id=2249392
If that's affecting you, `blkid` will be missing some information
required for RAID assembly during boot. On the other hand, I was able to
assemble my RAID devices manually.
-- Sandro
next prev parent reply other threads:[~2024-01-24 1:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <432300551.863689.1705953121879.ref@mail.yahoo.com>
2024-01-22 19:52 ` Requesting help recovering my array RJ Marquette
2024-01-22 21:39 ` Reindl Harald
2024-01-22 22:13 ` RJ Marquette
2024-01-22 23:49 ` Reindl Harald
2024-01-23 0:09 ` RJ Marquette
2024-01-23 1:52 ` RJ Marquette
2024-01-23 16:06 ` David Niklas
2024-01-23 16:09 ` RJ Marquette
2024-01-23 16:16 ` RJ Marquette
2024-01-23 22:50 ` Sandro
2024-01-24 0:59 ` RJ Marquette [this message]
[not found] ` <d051abe3-af97-47a4-a087-432c91beb57e@yahoo.com>
2024-01-24 9:11 ` Sandro
2024-01-24 3:19 ` David Niklas
2024-01-24 12:17 ` RJ Marquette
2024-01-24 17:06 ` Sandro
2024-01-24 18:06 ` RJ Marquette
2024-01-24 21:20 ` Roger Heflin
2024-01-24 21:31 ` RJ Marquette
2024-01-24 21:44 ` Roger Heflin
2024-01-24 22:21 ` Robin Hill
2024-01-24 22:37 ` Roger Heflin
2024-01-25 1:13 ` RJ Marquette
2024-01-25 1:57 ` Roger Heflin
2024-01-25 9:49 ` Pascal Hambourg
2024-01-25 11:49 ` RJ Marquette
2024-01-25 14:57 ` Pascal Hambourg
2024-01-25 15:08 ` RJ Marquette
2024-01-25 17:43 ` Roger Heflin
2024-01-25 18:33 ` RJ Marquette
2024-01-25 22:37 ` Roger Heflin
2024-01-25 22:53 ` Roger Heflin
2024-01-25 23:00 ` Roger Heflin
2024-01-26 15:15 ` RJ Marquette
2024-01-26 15:25 ` Reindl Harald
2024-01-26 16:03 ` RJ Marquette
2024-01-26 23:45 ` RJ Marquette
2024-01-27 8:41 ` Pascal Hambourg
2024-01-27 12:30 ` RJ Marquette
2024-02-19 20:48 ` Pascal Hambourg
2024-01-25 17:06 ` Reindl Harald
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=804226557.24031.1706057996425@mail.yahoo.com \
--to=rjm1@yahoo.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 NNTP newsgroup(s).