From: Nix <nix@esperi.org.uk>
To: Stefanie Leisestreichler <stefanie.leisestreichler@peter-speer.de>
Cc: Wols Lists <antlists@youngman.org.uk>, linux-raid@vger.kernel.org
Subject: Re: Setup Recommendation on UEFI/GRUB/RAID1/LVM
Date: Mon, 20 Apr 2020 12:05:32 +0100 [thread overview]
Message-ID: <87eesito1v.fsf@esperi.org.uk> (raw)
In-Reply-To: <f3139daa-37d5-a965-d204-0ef5d9fe4f3f@peter-speer.de> (Stefanie Leisestreichler's message of "Mon, 20 Apr 2020 11:45:44 +0200")
On 20 Apr 2020, Stefanie Leisestreichler said:
> On 18.04.20 01:06, Nix wrote:
>> Boot000B* Current kernel HD(1,GPT,b6697409-a6ec-470d-994c-0d4828d08861,0x800,0x200000)/File(\efi\nix\current.efi)
>> Boot000E* Current kernel (secondary disk) HD(1,GPT,9f5912c7-46e7-45bf-a49d-969250f0a388,0x800,0x200000)/File(\efi\nix\current.efi)
>> Boot0011* Current kernel (tertiary disk) HD(1,GPT,8a5cf352-2e92-43ac-bb23-b0d9f27109e9,0x800,0x200000)/File(\efi\nix\current.efi)
>> Boot0012* Current kernel (quaternary disk) HD(1,GPT,83ec2441-79e9-4f3c-86ec-378545f776c6,0x800,0x200000)/File(\efi\nix\current.efi)
[...]
>
> Is there any reason why one could not have another entry for each disk (8 entries in this example in total instead of the 4 being
> listed) like:
>
> Boot000B* Current kernel HD(1,GPT,b6697409-a6ec-470d-994c-0d4828d08861,0x800,0x200000)/File(\efi\nix\old.efi)
>
> and so on to support booting the old kernel in case something went wrong?
None! I have one entry each for old/stable kernel on the current disk,
but it just gets quite verbose and repetitive with six disks, and the
two (other disks, old kernels) serve different purposes: I'm going to
want to boot off another disk if the kernel works but something went
wrong with the disk, and I'm going to want to boot an old kernel if the
kernel has gone wrong, in which case probably the disk is fine and I can
just boot off the current disk. If I find when booting a new kernel that
it breaks the disk and I have to boot an old kernel off another disk,
I'll just use the EFI shell to do it. :)
--
NULL && (void)
next prev parent reply other threads:[~2020-04-20 11:05 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 [this message]
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
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=87eesito1v.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=antlists@youngman.org.uk \
--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).