From: Reindl Harald <h.reindl@thelounge.net>
To: f6azm@yahoo.fr, linux-raid@vger.kernel.org
Subject: Re: array transfer
Date: Mon, 22 Jan 2024 22:41:35 +0100 [thread overview]
Message-ID: <74d13294-1c86-45dc-a08a-8ba8663c5756@thelounge.net> (raw)
In-Reply-To: <576015710.2373821.1705949149866@mail.yahoo.com>
Am 22.01.24 um 19:45 schrieb J Massé:
> Hello,
> I have been using RAID1 with mdadm for years.
> Linux system and /home are on a SATA SDD.
> Most of of my data are on two 4To HDD in RAID1 managed with mdadm.
>
> In want to use a newly assembled PC with a new mother board, new Processor and Linux system and /home on a M2 SDD.
> How can I transfer my two HDD to the new PC remaining in RAID1 without loosing data.
> What is the procedure to follow?
just plug the drives into the new computer, connect them and power it on
- the RAID should be detected everywhere automatically as
/dev/md125/126/127 or so
prev parent reply other threads:[~2024-01-22 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <576015710.2373821.1705949149866.ref@mail.yahoo.com>
2024-01-22 18:45 ` array transfer J Massé
2024-01-22 21:41 ` Reindl Harald [this message]
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=74d13294-1c86-45dc-a08a-8ba8663c5756@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=f6azm@yahoo.fr \
--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).