From: H <agents@meddatainc.com>
To: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Recovering RAID-1
Date: Sun, 13 Jun 2021 18:51:31 -0400 [thread overview]
Message-ID: <e6940ac5-9c2a-35bb-04fe-c80fe2a95405@meddatainc.com> (raw)
I am running CentOS 7 and would like to see if I can "recover" a lost(?) RAID-1 setup on two identical SSDs and would greatly appreciate some assistance.
Part of the history is that I many months ago used Intel fake RAID on the motherboard but I /think/ I may also have used software RAID... The motherboard was replaced and because there were some issues I eventually abandoned the fake RAID and did not have mdadm running at that time. Thus, I have been operating off the two identical disks in non-RAID mode but would now like to see if I can get back to having RAID-1 running using mdadm only. There have been a number of OS updates, new software installed and work done on the computer since but it is running fine.
Because I have no notes and really did not know what I had done before the above motherboard replacement I have to tread very carefully. Here is my current understanding:
- mdadm is installed on the system
- the two relevant disks are currently /dev/sdb and /dev/sdc (I also have two other disks in the system that are, for this purpose, irrelevant)
- gparted tells me that both disks are 238.47 GiB in size with:
-- /boot/efi of 260 MiB
-- /boot 1.00 GiB and formatted xfs
-- (LUKS) encrypted partition 247.22 GiB
-- unallocated 4.34 MiB
- gparted further shows a key symbol next to /dev/sdc1 and /dev/sdc2 and /dev/sdb3 but not /dev/sdb1, /dev/sdb2 and /dev/sdc3. Googling this it suggests that partitions with keys are in use and the ones with /no/ keys are /not/ in use?
- am I correct therefore that the system booted from /dev/sdc1 and /dev/sdc2 and using /dev/sdb3 for everything /but/ /boot and /boot/efi?
- cat /proc/mdstat does not show any RAID information
- my /uneducated/ guess is that there /might/ be some RAID-information in the last 4.34 MiB but I am not sure how to check it?
- my next /uneducated/ guess is that, if so, mdadm 0.90 was/could be used since that is the version that seems to use space at the end of the disk
I would very much appreciate if anyone can suggest how to check the last items? Once this has been verified the next step would be to get mdadm RAID-1 going again.
If any of the above is incorrect in whole or partially, please advise.
Thanks!
next reply other threads:[~2021-06-13 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 22:51 H [this message]
2021-06-14 8:17 ` Recovering RAID-1 antlists
2021-06-14 17:35 ` H
2021-06-16 18:02 ` Piergiorgio Sartor
2021-06-17 17:37 ` H
2021-06-17 18:22 ` 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=e6940ac5-9c2a-35bb-04fe-c80fe2a95405@meddatainc.com \
--to=agents@meddatainc.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