Installing Manjaro Unencrypted boot and encrypted root

[linux-aarhus]

@fhins

Perhaps this is the missing step that I need?

No - it is not - not for an EFI based system.

You can verify if you are using an efi based system if the following command is successful or not

ls /sys/firmware/efi/efivars

@fhins

Option to use GPT on BIOS
A GPT partition table is the best option for all systems. This installer supports such a setup for BIOS system too.

It is possible to use GPT on BIOS boot but not all system firmware is supporting it.

And there is no advantages nor benefits in doing so.

It is possible to configure a GPT partitioned disk device to be bootable whether you are using efi or bios - the only advantage is that you can move disk between systems that has firmware support GPT.

So being able to create a bios-boot partition like instructed by Calamares does not indicate a missing link.

The fact that your system has intermittent failures point more to hardware issue than an installer issue.

You should be aware that when using encryption on a manually partitioned systerm - how the aforementioned guide shows - it becomes difficult to manually implement suspend and hibernation.

When your power settings include suspend and hibernation settings - this will create weird issues - most likely states where you need to ensure RAM has be cleared - reboot the system twice holding the powerbutton the second time to ensure clearing variables telling the systems NVRAM to resume from hibernation.

[mishmosh]

@fhins

How ever, I can hit the Esc key really fast to by pass the hanging. Then it goes to the login screen.

That’s exciting for two reasons:

1. Removing splash from the grub config will likely be a good workaround.

2. You can further diagnose the issue by looking for errors in:

journalctl -b 0 --no-pager

[fhins]

Sorry, I’m not following this.
I’m assuming I have to login as root?
“# list boots” not found when I type it in the terminal.

Here’s another thought.
I can login bypassing the splash screen by hitting the Esc key as soon as I enter the encryption password. Then I can edit the grub in etc/default/grub.
Is there anything I can uncomment or delete editing the grub file in order to bypass the splash and then do a “sudo update-grub”?

[mishmosh]

@fhins

Sorry, I’m not following this.
I’m assuming I have to login as root?

Sorry I made it confusing, I’ve simplified it. It will show a lot of lines! The --no-pager is to ensure full lines show if posting the result, take it off to have nicer scrolling etc.

Login as normal user, not root.

@fhins

I can login bypassing the splash screen by hitting the Esc key as soon as I enter the encryption password. Then I can edit the grub in etc/default/grub.
Is there anything I can uncomment or delete editing the grub file in order to bypass the splash and then do a “sudo update-grub”?

Edit /etc/default/grub and remove the word splash in the line:
GRUB_CMDLINE_LINUX_DEFAULT="..."

Then sudo update-grub as you said.

[fhins]

@mishmosh

That fixed the problem! You lose the pretty looking encryption box but that definitely the worked around. Hopefully they can fix this issue in the future ISOs!

Thanks a lot!

[mishmosh]

You’re welcome! although it just works around the problem … maybe try splash again after a future update.

[fhins]

Do you mean add the “splash” back on the line and update the grub again?

[mishmosh]

Yes, whenever you feel like experimenting. Or alternatively have a splash-shaped lump in the rug, haha

[fhins]

It actually saves you an extra second because it by passes the encryption box!

[linux-aarhus]

@fhins

That fixed the problem! You lose the pretty looking encryption box but that definitely the worked around.

That makes absolutely no sense to me.

Due to be an absolute nerd with electronic devices - I have use a fairly recent piece of hardware

Memory:
  RAM: total: 15.5 GiB used: 1.78 GiB (11.5%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges
    required.
CPU:
  Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache:
    L2: 1024 KiB
  Speed (MHz): avg: 1675 min/max: 400/4000 cores: 1: 2000 2: 2000 3: 2000
    4: 704 5: 2000 6: 2000 7: 700 8: 2000

The splash screen is implemented with 22.1.0 iso. So it must be a combination of that addition and your hardware as I have not been able to replicate the issue.

[mishmosh]

@linux-aarhus

The splash scrren is implemented with 22.1.0 iso. So it must be a combination of that addition and your hardware as I have not been able to replicate the issue.

I did find a post for a similar sounding problem on Arch: [SOLVED] Plymouth: not showing on boot or with --show-splash / Newbie Corner / Arch Linux Forums although its 3 years old, maybe still relevant

SOLUTION I am using EFISTUB and it turns out that the new kernel parameters set by efibootmgr weren’t taken into account… Just found out that I have to boot to the UEFI menu and lauch from there once, before the EFI entry is updated with the new parameters… so tried installing Plymouth again, and it now works perfectly

I’m unsure how to translate that into testable steps for Manjaro kde

[linux-aarhus]

The topic reference is not relevant in this situation as the poster was using systemd-boot - whereas Manjaro uses GRUB.

This usage of systemd-boot can be deducted from the sd- entries in the HOOKS line.

[Schorsch]

Yes, I’ve used the Manjaro How-to for changing to systemd-boot that was written by a famous an very active forum member
I made a first trial with the more modern ‘kernel-install’ approach and realized that the error did’nt disapear. Then I used the ‘manual’ way and switched the mkinitcpio hooks from ‘encrypt’ to ‘sd-encrypt’. So my boot procedure completly different now but the splash screen is not activated, jet.

’ This usage of systemd-boot can be deducted from the sd- entries in the HOOKS line.’
Please let me detail that:
Systemd-boot can can decrypt by using the ‘encrypt’ hook. There is no need to change to the ‘sd-boot’ hook. In this case the same decryption skripts are used that are called by grub. But when you change from ‘encrypt’ to ‘sd-encrypt’ then systemd starts the decryption. (I’ve repeated my installation a few times bevore I’ve learned that.)

[fhins]

@Shorsch,
I’d like to learn what you’re saying, but unfortunately I’m totally lost! Could you give me more specifics as how as you’re doing this?

[mishmosh]

@fhins I’m learning too, more reading material:

Boot process, how the pieces fit together

[HowTo] Understand EFI boot process with GPT via GRUB to manjaro

Welcome, if this info appears in a box please follow the link above the box. The information here is intended to help you understand and analyze the boot process during an EFI boot. You may be able to use the information here to find out why your manjaro isn’t booting. Only when you know the problem you can fix it with certainty. At the end of the post there are links to fix the problem. Klick on the black to expand a section (updated last 20220123) How the boot process works …

The systemd-boot tutorial mentioned by @Schorsch

[How To] Convert to systemd-boot

Convert GRUB to systemd-boot This tutorial has originally been written by @dalto and published at EndeavourOS forum (see link at the bottom). As the general principle applies to Manjaro as well, I have - with proper permission - reproduced the guide to fit into the Manjaro knowledge base. My rewrite is kept as close to the original as possible only replacing the original authors self reference with more generic phrases. Should you apply this to your system? That is a question I cannot answer …

similar issue with encrypted root, also bootsplash vs plymouth … this post and the following posts

[HowTo] Enable Bootsplash Provided by the kernel

I tried it in my VM as my testing. But that does not work with LUKS password prompt, but you must manually press any key to switch console for asking password. I tried to install mkinitcpio-encrypt-bootsplash from AUR but build failed. I’m sticking plymouth which supports displaying theme and prompting for password.