From: Nix <nix@esperi.org.uk>
To: Stefanie Leisestreichler <stefanie.leisestreichler@peter-speer.de>
Cc: G <garboge@shaw.ca>, linux-raid@vger.kernel.org
Subject: Re: Setup Recommendation on UEFI/GRUB/RAID1/LVM
Date: Sat, 18 Apr 2020 00:10:05 +0100 [thread overview]
Message-ID: <87h7xhemk2.fsf@esperi.org.uk> (raw)
In-Reply-To: <c6be03e8-7726-f184-7752-b41732a9e015@peter-speer.de> (Stefanie Leisestreichler's message of "Tue, 14 Apr 2020 18:14:00 +0200")
On 14 Apr 2020, Stefanie Leisestreichler outgrape:
> On 14.04.20 18:00, G wrote:
>> Since you are running disks less than 2TB I would suggest a more rudimentary setup using legacy bios booting. This setup will not
>> allow disks greater than 2TB because they would not be partitioned GPT. There would still be an ability to increase total storage
>> using more disks. There would be raid redundancy with the ability for grub to boot off either disk.
>>
>> Two identical partitions on each disk using mbr partition tables.
>
> Thank you for your thoughts and input.
> I would prefer using uefi/gpt in favor of legacy setup even you are
> totally right about the 2TB border.
Agreed. I avoided GPT like the plague for ages (shoddy early-2010s
motherboard firmware), but once I switched to it it was so much easier
to manage than old-style BIOS, and so much easier to deal with when
disaster struck, that I'd never consider going back. Does the BIOS have
anything like an EFI shell? No, no it doesn't. Can you hack your own
device drivers up if need be and throw them into place for more recovery
options? No, no you can't.
Can you play DOOM before the OS starts in your BIOS-based system -- oh
wait, sane people don't do that, do they. But you can't get higher
availability for truly important functions than that!
<https://doomwiki.org/wiki/Doom_UEFI>
next prev parent reply other threads:[~2020-04-17 23:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 13:02 Setup Recommendation on UEFI/GRUB/RAID1/LVM Stefanie Leisestreichler
2020-04-14 14:20 ` Wols Lists
2020-04-14 14:27 ` Reindl Harald
2020-04-14 15:12 ` Stefanie Leisestreichler
2020-04-14 17:35 ` Wols Lists
2020-04-14 19:13 ` Stefanie Leisestreichler
2020-04-14 19:36 ` Wols Lists
2020-04-17 23:06 ` Nix
2020-04-20 9:23 ` Stefanie Leisestreichler
2020-04-20 9:45 ` Stefanie Leisestreichler
2020-04-20 11:05 ` Nix
2020-04-20 12:01 ` Stefanie Leisestreichler
2020-04-16 1:50 ` David C. Rankin
2020-04-16 11:16 ` Wols Lists
2020-04-16 1:58 ` David C. Rankin
2020-04-14 16:00 ` G
2020-04-14 16:14 ` Stefanie Leisestreichler
2020-04-17 23:10 ` Nix [this message]
2020-04-24 19:15 ` Phillip Susi
2020-04-24 20:24 ` Nix
2020-04-14 16:20 ` Reindl Harald
2020-04-14 16:41 ` Stefanie Leisestreichler
2020-04-16 17:00 ` G
2020-04-14 18:14 ` Phillip Susi
2020-04-14 19:00 ` Stefanie Leisestreichler
2020-04-14 20:05 ` antlists
2020-04-17 23:24 ` Nix
[not found] ` <394a3255-251c-41d1-8a65-2451e5503ef9@teksavvy.com>
2020-04-15 15:53 ` Stefanie Leisestreichler
2020-04-15 16:10 ` Stefanie Leisestreichler
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=87h7xhemk2.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=garboge@shaw.ca \
--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;
as well as URLs for NNTP newsgroup(s).