public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Wol <antlists@youngman.org.uk>
To: "Stefanie Leisestreichler (Febas)"
	<stefanie.leisestreichler@peter-speer.de>,
	Roman Mamedov <rm@romanrm.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID 1 | Changing HDs
Date: Wed, 3 Sep 2025 20:50:55 +0100	[thread overview]
Message-ID: <ec124f5e-8849-49ce-bf8e-e537452c1dd3@youngman.org.uk> (raw)
In-Reply-To: <0bec82b1-ab30-4d3b-b254-a461d1039dbf@peter-speer.de>

On 03/09/2025 18:47, Stefanie Leisestreichler (Febas) wrote:
> I like this method, hopefully I have a free connector on the board.
> 
> But still two questions left:
> - Do I need to turn off the computer for the new (3rd) disk to be known? 
> If I remember correct I had try a hot spare in another scenario and 
> wasn't able to expose the new hard disk to be recognized by lsblk or 
> similar.

As others have said, if your mobo doesn't support hotplug, DON'T TRY IT!

Otherwise, use eSATA (or USB).>
> Also I see problems with the device naming as long as no hd uuids are 
> not used by having a drive appearing as /dev/sdx and with next reboot 
> as /dev/sdn. Are my concerns reasonable or am I just too afraid?
As others have said, it doesn't matter. Not sure if as the other person 
said md uses uuids, or if it just scans all partitions, and looks for a 
superblock.
What I would say (and it's not for raid1, but definitely raid 5/6) if 
you do have parity raid then make sure every time you change the config, 
generate an mdadm.conf file (or whatever it's called). While md doesn't 
use it, if you have a problem with your raid you will wish you had it!

As I say, you're raid 1, you don't need it now, but if you ever do 
change, DO IT!

Cheers,
Wol

  parent reply	other threads:[~2025-09-03 19:50 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
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 [this message]
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=ec124f5e-8849-49ce-bf8e-e537452c1dd3@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.net \
    --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