bug#70826: luks-device-mapping-with-options breaks bootloader

2025-06-15 Thread Quentin Vincent via Bug reports for GNU Guix
Hi, I independently ran into and fixed this issue myself, but seeing Ludo's patch, I'll probably run with that. @Ludo: I tested your patch on my setup (inside a VM); it needed a few small fixups (an export was missing and the (apply ...) wasn't working for some reason), but other than that it wor

bug#70826: luks-device-mapping-with-options breaks bootloader

2024-08-11 Thread Tadhg McDonald-Jensen
In case it is relevant my disk is using GPT partition table with this layout: $ lsblk --output="NAME,MAJ:MIN,TYPE,MOUNTPOINTS,UUID" NAME MAJ:MIN TYPE MOUNTPOINTS UUID nvme0n1 259:0 disk ├─nvme0n1p1 259:1 part /boot 5190-E840 └─nvme0n1p2 259:2 part c0010d06-0bd1-4ae2-93e6-f2f89a3a670b └─cryptroot 2

bug#70826: luks-device-mapping-with-options breaks bootloader

2024-08-11 Thread Tadhg McDonald-Jensen
I have attached a config I just did `sudo guix system reconfigure` and confirmed it was missing the `insmod luks` in /boot/grub/grub.cfg Sorry for the delay, Tadhg McD-J On 2024-07-23 2:19 p.m., Tomas Volf wrote: > On 2024-05-25 10:30:49 -0400, Tadhg McDonald-Jensen wrote: >> That unfortunately d

bug#70826: luks-device-mapping-with-options breaks bootloader

2024-07-23 Thread Tomas Volf
On 2024-05-25 10:30:49 -0400, Tadhg McDonald-Jensen wrote: > That unfortunately doesn't fix the problem, > `luks-device-mapping-with-options` is a routine that returns the > `mapped-device-kind` so it won't check by equality. > > A possible solution is to check whether the `mapped-device-kind-close

bug#70826: luks-device-mapping-with-options breaks bootloader

2024-05-25 Thread Tadhg McDonald-Jensen
That unfortunately doesn't fix the problem, `luks-device-mapping-with-options` is a routine that returns the `mapped-device-kind` so it won't check by equality. A possible solution is to check whether the `mapped-device-kind-close` routines are the same as these are shared. diff --git a/gnu

bug#70826: luks-device-mapping-with-options breaks bootloader

2024-05-25 Thread Ludovic Courtès
Hi, Tadhg McDonald-Jensen skribis: > using the `luks-device-mapping-with-options` mapped device type defined in > (gnu system mapped-devices) causes grub or other bootloaders to not > properly attempt to mount the encrypted drive. This is caused by the > commit 39a9404 which identifies luks mapp

bug#70826: luks-device-mapping-with-options breaks bootloader

2024-05-13 Thread Tadhg McDonald-Jensen
using the `luks-device-mapping-with-options` mapped device type defined in (gnu system mapped-devices) causes grub or other bootloaders to not properly attempt to mount the encrypted drive. This is caused by the commit 39a9404 which identifies luks mapped devices by checking if the type is equal to