From: Roman Mamedov <rm@romanrm.net>
To: "Stefanie Leisestreichler (Febas)"
<stefanie.leisestreichler@peter-speer.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 1 | Changing HDs
Date: Wed, 3 Sep 2025 20:45:21 +0500 [thread overview]
Message-ID: <20250903204521.44e91df1@nvm> (raw)
In-Reply-To: <5c8e3075-e45a-410e-a23a-cbf0e86bdfa6@peter-speer.de>
On Wed, 3 Sep 2025 13:55:05 +0200
"Stefanie Leisestreichler (Febas)" <stefanie.leisestreichler@peter-speer.de>
wrote:
> Hi.
> I have the system layout shown below.
>
> To avoid data loss, I want to change HDs which have about 46508 hours of
> up time.
Do you have a free drive bay and connector in your computer (or just the
connector)?
If so, the safest would be to connect all three drives, and then:
mdadm --add (new drive)
mdadm --grow -n3 (array)
mdadm --fail --remove (old drive).
mdadm --grow -n2 (array)
> I thought, instead of degrading, formatting, rebuilding and so on, I could
> - shutdown the computer
> - take i.e. /dev/sda and do
> - dd bs=98304 conv=sync,noerror if=/dev/sda of=/dev/sdX (X standig for
> device name of new disk)
Very peculiar dd line you give as an example here.
- calculator tells us 98304 is 96K, but why? Usually one would just use "1M"
or the like here for performance reasons, and shorter to remember and type.
- noerror is "continue after read errors", but do you want it to? I don't
think the regular dd has the logic to pad output to an exact amount
of unreadable data on input errors, and if not, then the result is useless.
If you expect input to have read errors, "ddrescue" should be used.
But that's all beside the point as I don't see a reason to rely on offline
migration with dd here either.
--
With respect,
Roman
next prev parent reply other threads:[~2025-09-03 15:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 11:55 RAID 1 | Changing HDs Stefanie Leisestreichler (Febas)
2025-09-03 12:19 ` Reindl Harald
2025-09-03 13:20 ` Stefanie Leisestreichler (Febas)
2025-09-03 14:00 ` Reindl Harald
2025-09-03 14:26 ` Stefanie Leisestreichler (Febas)
2025-09-03 21:59 ` Reindl Harald
2025-09-04 17:04 ` Stefanie Leisestreichler (Febas)
2025-09-03 12:35 ` Hannes Reinecke
2025-09-03 12:49 ` Stefanie Leisestreichler (Febas)
2025-09-03 15:45 ` Roman Mamedov [this message]
2025-09-03 16:58 ` Michael Reinelt
2025-09-03 17:28 ` Roman Mamedov
2025-09-03 17:47 ` Stefanie Leisestreichler (Febas)
2025-09-03 17:57 ` Pascal Hambourg
2025-09-03 19:19 ` Stefanie Leisestreichler (Febas)
2025-09-03 19:50 ` Wol
2025-09-04 17:06 ` Stefanie Leisestreichler (Febas)
2025-09-03 15:59 ` anthony
2025-09-04 17:13 ` Stefanie Leisestreichler (Febas)
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=20250903204521.44e91df1@nvm \
--to=rm@romanrm.net \
--cc=linux-raid@vger.kernel.org \
--cc=stefanie.leisestreichler@peter-speer.de \
/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