From: Reindl Harald <h.reindl@thelounge.net>
To: Wols Lists <antlists@youngman.org.uk>, H <agents@meddatainc.com>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Transferring an existing system from non-RAID disks to RAID1 disks in the same computer
Date: Sun, 15 Jan 2023 10:02:29 +0100 [thread overview]
Message-ID: <9aab4088-3ba3-3c7c-4254-a0d829b06066@thelounge.net> (raw)
In-Reply-To: <37a150cb-286b-4137-bb72-08e2de21c851@youngman.org.uk>
Am 15.01.23 um 09:41 schrieb Wols Lists:
> Are your /boot and /boot/efi using superblock 1.0? My system is
> bios/grub, so not the same, but I use plain partitions here because
> otherwise you're likely to get in a circular dependency - you need efi
> to boot, but the system can't access efi until it's booted ... oops!
the UEFI don't care where the ESP is mounted later
from the viewpoint of the UEFI all paths are /-prefixed
that's only relevant for the OS at the time of kernel-install / updates
and the ESP is vfat and don't support RAID anyways
next prev parent reply other threads:[~2023-01-15 9:20 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 3:12 Transferring an existing system from non-RAID disks to RAID1 disks in the same computer H
2023-01-15 8:41 ` Wols Lists
2023-01-15 9:02 ` Reindl Harald [this message]
2023-01-15 9:20 ` Wols Lists
2023-01-15 9:39 ` Reindl Harald
2023-01-15 10:45 ` Wols Lists
2023-01-20 2:48 ` Phil Turmel
2023-01-15 11:31 ` Pascal Hambourg
2023-01-20 2:51 ` Phil Turmel
2023-01-20 19:27 ` Pascal Hambourg
2023-01-20 20:26 ` Wol
2023-01-20 21:01 ` Pascal Hambourg
2023-01-21 8:49 ` Wols Lists
2023-01-21 13:32 ` Pascal Hambourg
2023-01-21 14:04 ` Wols Lists
2023-01-21 14:33 ` Pascal Hambourg
2023-01-21 15:21 ` Wols Lists
2023-01-21 18:32 ` Pascal Hambourg
2023-01-21 18:39 ` Reindl Harald
2023-01-21 18:57 ` Pascal Hambourg
2023-01-21 19:08 ` Reindl Harald
2023-01-21 22:43 ` Pascal Hambourg
2023-01-21 22:56 ` Reindl Harald
2023-01-22 9:04 ` Pascal Hambourg
2023-01-22 11:25 ` Reindl Harald
2023-01-21 12:17 ` Reindl Harald
2023-01-21 14:15 ` Pascal Hambourg
2023-01-21 14:31 ` Reindl Harald
2023-01-21 14:38 ` Pascal Hambourg
2023-01-21 14:52 ` Reindl Harald
2023-01-21 15:17 ` Pascal Hambourg
2023-01-21 16:24 ` Reindl Harald
2023-01-21 18:52 ` Pascal Hambourg
2023-01-21 18:57 ` Reindl Harald
2023-01-21 20:04 ` Pascal Hambourg
2023-01-21 20:44 ` Reindl Harald
2023-01-21 22:56 ` Pascal Hambourg
2023-01-21 22:59 ` Reindl Harald
2023-01-21 23:04 ` Reindl Harald
2023-01-21 23:02 ` Reindl Harald
2023-01-22 9:22 ` Pascal Hambourg
2023-01-22 11:29 ` Reindl Harald
2023-01-21 21:20 ` Phil Turmel
2023-01-15 17:25 ` H
2023-01-22 5:05 ` H
2023-01-22 8:52 ` Pascal Hambourg
2023-01-22 17:19 ` Wol
2023-01-23 0:25 ` H
2023-01-23 3:44 ` Brad Campbell
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=9aab4088-3ba3-3c7c-4254-a0d829b06066@thelounge.net \
--to=h.reindl@thelounge.net \
--cc=agents@meddatainc.com \
--cc=antlists@youngman.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.