Siduction Forum > Installation - Support

 UEFI plus dm-crypt

(1/3) > >>

oneself:
Hi,


I'm tying to install Siduction on a laptop that seems to only support UEFI (Lenovo t480) using full disk encryption.  I've used full disk encryption in the past successfully with Siduction, but the added UEFI is throwing me for a loop.  I've done the following:

* I've created an UEFI partition using parted (formatted as vfat32).
* Created an encrypted partition on the rest of the disk.
* Divided it up using lvm to include a root, home, etc. partitions.This is where I get into some trouble, when I use the latest installer that's available on the desktop (calamares, patience), it will not recognize the lvm partitions for some reason.  So, I can't tell it where my root, home, etc. partitions are.  I've also tried using cli-installer.  That works fine, however, it will not let me set a custom path for the UEFI partition.  So, I cannot mount it during the install and nothing gets install there.


Is there a different installer I can try?  Am I use the default installer incorrectly?  Can I get the right files into the UEFI partition manually?


Thank you for any help.

devil:
There is and always will be the text-installer called cli-installer. That should work for you

ReinerS:
Hmm, I reinstalled my laptop not too far ago with Lvm, luks/dmcypt via clamares and it works.
regards
Reiner

melmarker:
calamares is not ready for dm-crypt right now. This is intentional. And right now i'm veto to activate crypt support - this will change if calamares is able to handle our preferred way to do encryption (LVM2+LUKS). We can talk about it again when cala fully support this way of doing things. Second this will depend on people who are able and willing to support it. Without i'm not convinced that enabling crypt is a good idea.

Beside of that: For supported hardware (UEFi, SSD) i just recommend transparent  hardware encryption instead.

Final: devil mentioned the cli-installer. cli-installer works just fine for this use case. There is a big but: With the upcoming release the cli-installer will not work anymore unless someone fix it for usr-merged systems. usr-merge will be default with our upcoming release. We accept patches.

oneself:
I think a little more details to understand what I'm doing wrong.

I don't think I need calamares to support encryption outright, I just need it to support lvm.  I've setup encryption manually myself behind the scenes, but when I start up the installer it does not see the lvm partitions.  It just shows me two partitions, the efi partition and one large partition which cover the entire rest of the drive (this is the one that has lvm on it).  Is this expect?  Am I doing something wrong.


As for cli-installer.  I've tried that as well.  The problem I am getting into is that I believe that the efi partition needs to be mounted under /boot/efi, but the cli-installer does not allow me to set a custom path for mounting.  Is this right?  Can I mount the efi partition somewhere else? or is there some other workaround?


Could someone that has gotten cli-installer to work tell me what steps they've taken?  Which partition did you mount on /boot and where did you mount your efi partition?  Where did you install the bootloader during the installation "MBR" or "partition"?  Did you run efibootmgr manually afterwards?  If so, what was the command?

Navigation

[0] Message Index

[#] Next page