public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeffery Small <jeff@cjsa.com>
To: linux-raid@vger.kernel.org
Subject: Re: What is the best way to set up RAID-1 on new Ubuntu install
Date: Thu, 4 Sep 2025 04:54:42 -0000 (UTC)	[thread overview]
Message-ID: <109b62i$e2l$1@dymaxion.cjsa2.com> (raw)
In-Reply-To: 37f99719-4bb1-489c-8246-e6dffc8b0bf9@youngman.org.uk

Wol <antlists@youngman.org.uk> writes:

>On 03/09/2025 22:04, Jeffery Small wrote:
>> I will be installing Xubuntu 24.04.3 on a newly built system having two
>> 4TB Samsung M.2 SSDs which will be mirrored using RAID-1.  My question is
>> what is the better way to set up the mirror.  I'll have 128GB of RAM and
>> will be using a swapfile after installation.
>> 
>> Method #1: After the UEFI partition is created on both disks, create GPT
>>             /boot, / and /home partitions on each SSD and then create
>> 	   three separate mirrors:
>> 
>> 	   md0: /boot
>> 
>> 	   md1: /
>> 
>> 	   md2: /home
>> 
>> Method #2: After the UEFI partition is created on both disks, mirror md0
>> 	   using the rest of the free space.  Then create GPT partitions
>> 	   directly on the mirror:
>> 
>> 	   md0p1: /boot
>> 
>> 	   md0p2: /
>> 
>> 	   md0p3: /home
>> 
>> This will be a straightforward desktop workstation, with no encryption or
>> support for multiple OS installs.  Are there advantages or possible pitfalls
>> with either approach?
>> 
>> I'm also considering eliminating the boot and home partitions and just
>> using a single root partition which feels strange after using UNIX for over
>> 40 years. From a raid perspective does this also have advantages/pitfalls?
>> 
>DON'T mirror /boot. Unless you use 0.9 layout. It just makes setting up 
>the boot more complicated. If anything goes wrong, 0.9 allows you to 
>boot with no raid support.

>128GB of ram? Why bother with a swapfile? Okay, I would create two 128GB 
>swap partitions and set them equal priority, but that's me.

>And what are you doing about /var? Does it really belong in the / partition?

>With a 4TB setup, especially with a workstation, combining /, /var. and 
>/home might be a sensible option. As I say, keep /boot out of it, but a 
>single 3.5TB partition for everything else makes a lot of sense. How 
>likely are you to run out of disk space? Highly unlikely? Then go for 
>it! Remember most of the advice about Unix partitioning stems from the 
>fact that K&R or T or whoever it was created the initial partitioning 
>scheme simply because they were running out of space on a (by today's 
>standards) tiny disk drive. Why stick with what they were forced to do?

>Cheers,
>Wol

Wol, thanks for the reply.  What is a 0.9 layout?  I've never heard of
that before.  I'm confused about why to not mirror the boot partition.
Other articles I've read on the subject suggest doing this.  What is the
problem?

Now maybe we are having a communication problem mixing up the initial
UEFI partition (mounted at /boot/efi) which does get set up on each SSD
independently and is definitely NOT mirrored, and the actual boot partition
(mounted as /boot) which is where GRUB and kernel are installed.  If I
made one big mirrored / partition, /boot could just be included along with
everything else.

As I say, I'm just trying to avoid future problem from something that I
didn't anticipate from the start.

Regards,
--
Jeff

  reply	other threads:[~2025-09-04  4:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 21:04 What is the best way to set up RAID-1 on new Ubuntu install Jeffery Small
2025-09-03 21:32 ` Wol
2025-09-04  4:54   ` Jeffery Small [this message]
2025-09-04 22:55     ` Wol
2025-09-05  3:12       ` Reindl Harald
2025-09-05  4:40         ` Jeffery Small
2025-09-06  2:16         ` Dragan Milivojević
2025-09-05  6:03       ` Pascal Hambourg
2025-09-04  7:41 ` Adam Niescierowicz
2025-09-04  9:22   ` Michael Reinelt

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='109b62i$e2l$1@dymaxion.cjsa2.com' \
    --to=jeff@cjsa.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