all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sun, 27 Mar 2022 00:07:34 -0400	[thread overview]
Message-ID: <878rswvy0p.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")

Hi,

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.

It seems this is a problem not unknown to other (non-Btrfs) software
RAID as well, such as mdadm.  There was recently a fix for it in Ubuntu
[0].  It can probably provide cues about how to go to fix it in Guix
System.

[0]  https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980




      parent reply	other threads:[~2022-03-27  4: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
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 [this message]

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=878rswvy0p.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

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.