Re: installation on LVM on LUKS

[Roman Scherer <roman.scherer@burningswell.com>]

[-- Attachment #1: Type: text/plain, Size: 2577 bytes --]


Hi Emmanuel,

did you add the cryptsetup-static and lvm2-static packages to the
packages field of your operating system?

Apart from that, I think you also need to add the dm-crypt module to the
initrd-modules field of the of the operating system.

I'm not sure about your other question, but from what I understand the
reason why the kernel and the initrd live in the store and not in the
EFI partition might be that you actually would need to put the kernel
and the initrd for *each* system generation onto the EFI partition, so
you can boot different system generations. And that would fill up the
EFI partition pretty quickly.

I hope that helps.

Roman

Emmanuel Beffara <manu@beffara.org> writes:

> Hello,
>
> I am currently trying to install Guix System on my laptop and I am facing an
> issue with the bootloader configuration.
>
> I use full-disk encryption with a single encrypted partition, split into
> several logical volumes using LVM, plus an extra non-encrypted partition for
> EFI boot material:
>
> 	nvme0n1              259:0    0 953,9G  0 disk
> 	├─nvme0n1p1          259:1    0 953,4G  0 part
> 	│ └─manivelle        254:0    0 953,4G  0 crypt
> 	│   ├─storage-swap   254:1    0    32G  0 lvm   [SWAP]
> 	│   │ [...]
> 	│   └─storage-guix   254:5    0    64G  0 lvm   /
> 	└─nvme0n1p2          259:2    0   487M  0 part  /boot
>
> I attach the system configuration, which I derived from the desktop template.
>
> Everything installed fine EXCEPT that Grub fails to load its LVM volume, hence
> the root partition is not found. Indeed, the produced grub.cfg has no mention
> of lvm anywhere. If I adjust it by inserting "insmod lvm" somewhere, either at
> the start or in a menuentry, or if I do that by hand in the Grub shell, then
> the system starts and works fine.
>
> Did I miss something in the configuration ?
>
>
> As a related point, this setup requires entering the decryption password
> twice: once so that Grub can load the kernel from the store, and once so that
> the kernel can open the volume itself. I understand the situation is known,
> but it could be avoided, for instance, by copying the kernel and initrd
> somewhere in the EFI partition so that they could be loaded directly. Besides,
> for some reason, Grub is extremely slow at opening the partition: it takes
> around 30 seconds to start after I correctly enter the password, whereas the
> kernel boots in just a few seconds after I enter the password for it.
>
> Any thoughts on this ?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 528 bytes --]