From: Leslie Rhorer <lesrhorer@att.net>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Corrupted RAID 1
Date: Thu, 13 Jul 2023 15:58:13 -0500 [thread overview]
Message-ID: <d44dd435-46e8-f40c-e8cf-24e6c6e93687@att.net> (raw)
In-Reply-To: d44dd435-46e8-f40c-e8cf-24e6c6e93687.ref@att.net
I have a corrupted bootable RAID 1 array on a pair of SDD drives, and I
fear I need some assistance. Actually, there are four partitions on
each drive, and two RAID 1 arrays were assembled from each drive. When
working properly, the second pair of partitions were mounted as / and
the first pair were mounted as /boot. The OS is Debian Buster. When I
attempt to boot the system, it goes directly to the GRUB prompt.
I pulled the drives and attached them to an active system. Mdadm
reports both partition tables to be intact with partition labels of fd,
83, ef, and 82, respectively and MBR magic of aa55. When I try to
assemble any array says the partitions exist but are not md arrays.
Fdisk reports the partition types as Linux raid autodetect, Linux, EFI,
and Linux swap / Solaris. The EFI partitions are marked bootable and
contain the following:
total 3472
-rwxr-xr-x 1 root root 108 May 28 2022 BOOTX64.CSV
-rwxr-xr-x 1 root root 84648 May 28 2022 fbx64.efi
-rwxr-xr-x 1 root root 152 May 28 2022 grub.cfg
-rwxr-xr-x 1 root root 1672576 May 28 2022 grubx64.efi
-rwxr-xr-x 1 root root 845480 May 28 2022 mmx64.efi
-rwxr-xr-x 1 root root 934240 May 28 2022 shimx64.efi
Any suggestions? I should say that the running system
(Bullseye) is not the same version as the failed one (Buster). Of
course the failed system does need to be upgraded, but there are
specific reasons why this is quite undesirable at this point.
next parent reply other threads:[~2023-07-13 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d44dd435-46e8-f40c-e8cf-24e6c6e93687.ref@att.net>
2023-07-13 20:58 ` Leslie Rhorer [this message]
2023-07-18 9:25 ` Corrupted RAID 1 Yu Kuai
2023-07-18 16:59 ` Wols Lists
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=d44dd435-46e8-f40c-e8cf-24e6c6e93687@att.net \
--to=lesrhorer@att.net \
--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