Description of the issue (screenshots if relevant):
I tryed to install OpenMandrivaLX 4.0 in a Virtualbox using a luks encrypted swap partition and a luks encrypted root partition.
Here is the summary displayed before the start of the installation:
Summary:
Location: Set timezone to Europe/Brussels The system language will be set toAmericanEnglish (United States).
The numbers and dates locale will be set toAmericanEnglish (United States).
Keyboard: Set keyboard model to Generic 105-key PC (Intl.) – Default Keyboard Model Set keyboard layout to English (US) Default
Partitions: Manual partitioning on disk /dev/sda (VBOX HARDDISK) New partition 8.6 GiB Luks Openmandriva55.4 GiB Luks
Create new MSDOS partition table on /dev/sda (VBOX HARDDISK)
Create new 8800MB partition on /dev/sda (VBOX HARDDISK) with file system luks
Flag 8800MB luks partition as swap
Create new 56729MB partition on /dev/sda (VBOX HARDDISK) with file system luks
Flag 56729 MB luks partition as root
Install OpenMandriva Lx on new ext4 system partition.
Install boot loader on /dev/sda
Install
The installation starts but aborts after a very short time with the message:
Installation Failed
The installer failed to create partition on disk 'VBOX HARDDISK'.
Create a new partition (55.40 GiB, luks) on '/dev/sda'
Job: Create new partition on device '/dev/sda'
Command: sfdisk --force --append /dev/sda
Job: Create file system 'luks' on partition '/dev/sda2'
Command: cryptsetup -s 512 --batch-mode --force-password --type luks 1 luksFormat /dev
sda2
Is this a known problem and can it be fixed?
Regards,
Albert
I’m trying to stick to what I know here. So first I have no personal experience with Luks.
This issue is not a known issue. Install with Luks file system would not be well tested in OM Lx 4.0 development if it was tested at all. There is nothing intentional about the lack of testing, this is just a consequence of using the few resources we have the best we can.
Most install testing during development was either EFI or Legacy boot primarily with ext4 but also some f2fs, btrfs, and xfs file system installs.
I’m hoping we can get a developer to tell us if Luks is really supported or not.
Hello, @Ben79: Thanks for verifying my problem. @Bequimao : In OpenMandrivaLx3.03 calamares can handle this setup (without a separate non encrypted /boot partition).
I also remember that OpenMandrivaLx3.03 couldn’t do it at the beginning of the release, it took some time to get it running.
Regards,
Albert
Hello Stephane,
I’m afraid, I don’t fully understand your answer.
Quick questions:
Is it possible to fix this problem or do we have to wait until other tools are updated?
Is there a manual procedure to go around this problem?
Regards,
Albert
Boot partition is not needed for MSDOS partition table.
For @vhelmont’s install:
For my test:
Check again 1st screen shot. Where is says “flag 300MB fat32 partition as boot”
Thanks @Bequimao you may have pointed to a work around. You can certainly create a partition as you want before running Calamares and then when you get to partitioner select to “keep” it instead of “format”. I have not tried this with luks encrypted partition myself.
@stephane thanks for the imformation link. The more I read about luks the more it seems like support is discombobulated. Post-edit: Or it could be considered higgledy-piggledy.
I don’t think it matters if Calamares comes with luks1 if it does not work. If it did work there would be nothing wrong with using luks1. It is not necessary to use the latest version of something. Sometimes users are better off not using latest version of some things.
OM’s Calamares partitioner page has a check box for encryption. That uses luks or is supposed to. So that should either work or it should be removed.
Something that worked in OM implementation of Calamares last time I tested it (maybe 6 or more months ago) now does not work. I’m going on memory in this statement as I have nothing written down about luks installation. But this did work at one time.
(I doubt luks or encrypted partitions are a major focus of OM developers at this time.)
If I understand you correctly, you would set up an luks encrypted partition for swap and a luks encrypted partition for root via the command line.
Then you would start the mandriva installer and install the 4.0 system in the earlier created encrypted partitions.
Questions:
When you are in the Mandriva installer, how will you unlock the encrypted partitions before the start of the install operation?
Did you already tried this work around and is it possible to share this procedure with me. I would like to learn how this can be done?
I tested Calamares some years ago with KAOS Linux. LVM or encryption was not supported then. I knew about full encrypting (including /boot) from the Arch Wiki, but that was above my paygrade then.
I chose a setup with explicit /boot. The cryptsetup devices where recognized and kept. The installation started and failed after some time with a different error message unlike Ben’s test.
Something like: rsync error, failed to copy /run/…/???.img
Unfortunatedly I failed to copy the screenshot to my hard drive.
The root partition is not filled
[root@mga7-upgr ~]# df -h /mnt
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/crypt_mlvm15 20G 53M 20G 1% /mnt
[root@mga7-upgr ~]#
@vhelmont so as it says in that bug report this will work if you install without swap. And swap is not normally needed nowadays though it may be needed for hibernate (and maybe suspend), but I don’t use hibernate myself.
Hello,
I tried to be clever by cloning an OpenMandrivaLx3.03 Virtualbox luks encrypted installation and install an OpenMandrivaLx4.0 system on top of it.
The OpenMandrivaLx4.0 installer recognized the luks partitions but there was no option to insert my luks key and open the partitions, so the installation failed.
Regards,
Albert