Page 1 of 1

[SOLVED] Boot after installation fails with encrypted partition

Posted: Tue Feb 26, 2019 10:28 am
by mike4711
I think since creating Arcolinux full iso arcolinux-v19.03.1.iso (https://github.com/arcolinux/arcolinux-iso) the installer finishes normally but rebooting fails.

My ISO build
all of your standard packages (no changes)
some of my own packages (e.g. libreoffice-fresh-de, aspell-de, hunspell-de, etc.)

My SSD Layout:
GPT
1st partition: EFI + BOOT, 510MB
2nd partition: root, 100G
3rd partition: home, encrypted, rest

This layout worked previously, even with encrypted root (and home).

Extrace from the boot screen messages:
Starting Cryptography Setu? (after the ? the rest is partly cut off, you see part of the UUID)
[Failed] Failed to start Cryptograp? (afte the ? the rest is partly cut off, you see part of the UUID)
[Depend] Dependency failed for /dev? (after the ? the rest is partly cut off, you see part of the UUID)

Cheers
Michael

Re: [OPEN] Boot after installation fails with encrypted partition

Posted: Wed Feb 27, 2019 6:37 am
by erikdubois
I hear from others that Calamares is not fully ready for this kind of setup.

Hence I just do the normal setup without encryption and we will have to wait for calamares to keep growing and developing.

Re: [OPEN] Boot after installation fails with encrypted partition

Posted: Thu Feb 28, 2019 8:10 am
by erikdubois
Check out the github to follow up the progress the calamares development team makes

https://github.com/calamares/calamares/issues/1073

Re: [OPEN] Boot after installation fails with encrypted partition

Posted: Fri Mar 01, 2019 3:29 pm
by teacher4711
I found the solution.

The calamares installer WAS fully functional before because I used this setup before without any hiccups

Problem:
What makes the first boot fail is that the /crypto_keybile.bin is not present.
The line in /etc/crypttab, which specifies that there is a /crypto_keyfile.bin, has to be altered.

Solution:
If you replace /crypto_keyfile.bin with 'none', the boot process does not show any errors and you have to enter a password to decrypt the encrypted partition.

I've noticed, however, that the crypto_keyfile.bin, which holds the encryption key, does not work the way it is supposed to.
When I setup Arch Linux and install a crypto_keyfile.bin, I am not asked for my password during the boot process and the crypto_keyfile handles disk encryption. With a calamares install, I have always been asked for a password during the boot process, which I shouldn't be if everything had been setup correctly by calamares.

I've posted this issue as a response to a similar question on disk encryption (github calamares). Hope this was the correct spot.

Thanks.
Michael

Re: [OPEN] Boot after installation fails with encrypted partition

Posted: Fri Mar 01, 2019 8:56 pm
by erikdubois
the only way forward is to give a damn and report it to the guys of calamares on their github

We can close this one then.