From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 40999@debbugs.gnu.org
Subject: bug#40999: GRUB prevents booting a degraded RAID1 array atop LUKS
Date: Sat, 07 Aug 2021 01:06:58 -0400 [thread overview]
Message-ID: <874kc14zd9.fsf@gmail.com> (raw)
In-Reply-To: <87o8r7kbbz.fsf@hurd.i-did-not-set--mail-host-address--so-tickle-me> (maxim cournoyer's message of "Fri, 01 May 2020 09:56:48 -0400")
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
Hello,
maxim.cournoyer@gmail.com writes:
> On a system where:
>
> 1) Each disks comprising the array is fully LUKS encrypted
> 2) Each mapped disk is made part of a Btrfs RAID1 array
>
> When attempting to boot the system after pulling out (in BIOS or using
> the cable) the drive to simulate a complete disk failure, GRUB hangs,
> prompting for the LUKS password of the disappeared drive and
> (unsurprisingly) failing to open it.
>
> This prevents booting in a degraded LUKS encrypted, Btrfs RAID1 on Guix
> System.
I retested this today, and the problem still occurs. Here's a
screenshot from the failed boot (GRUB):
[-- Attachment #2: IMG_20210807_004828_1.jpg --]
[-- Type: image/jpeg, Size: 1155457 bytes --]
[-- Attachment #3: Type: text/plain, Size: 178 bytes --]
Ideally, GRUB (or is it our boot script?) should be smart enough to
realize that oh, that's Btrfs RAID1, it ought to work in degraded mode,
so let's keep going.
Thanks,
Maxim
next prev parent reply other threads:[~2021-08-07 5:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 13:56 bug#40999: GRUB prevents booting a degraded RAID1 array atop LUKS maxim.cournoyer
2021-08-07 5:06 ` Maxim Cournoyer [this message]
2021-08-11 14:45 ` Giovanni Biscuolo
2021-08-12 2:25 ` Maxim Cournoyer
2021-08-13 15:05 ` Giovanni Biscuolo
2021-08-29 6:15 ` Maxim Cournoyer
2022-03-05 3:33 ` Maxim Cournoyer
2022-03-27 4:07 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kc14zd9.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=40999@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).