Re: What is the best way to set up RAID-1 on new Ubuntu install

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Wol <antlists@xxxxxxxxxxxxxxx> 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




[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux