[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: installation on LVM on LUKS
From: |
Raffael Mancini |
Subject: |
Re: installation on LVM on LUKS |
Date: |
Fri, 3 Mar 2023 15:33:53 +0100 (CET) |
Hi Emmanuel,
You might want to look into adding missing modules to the initramfs
(https://guix.gnu.org/manual/en/html_node/Initial-RAM-Disk.html). I had to do
this so I could boot a system with Linux MD RAID.
Best regards,
Raffael
> Emmanuel Beffara <manu@beffara.org> hat am 02.03.2023 11:25 CET geschrieben:
>
>
> 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 ?
>
> --
> Emmanuel