Luks encrypted device not mapped during boot

Support
21

One behavioral question from my side:

Since the current issue is not related to the heading, should I

  1. Create a new issue with a relevant heading
  2. Come back and continue/ conclude this issue, whenever I am able to confirm the solution (i.e. if my grub issues a resolved)

OR should I simply wait here?

Please provide me some guideline. Thanks!

22

Just to verify that this is correct:

you opened the encrypted volume on /dev/sda2 with:

cryptsetup open /dev/sda2 tmp

and then mounted it with:

mount /dev/mapper/tmp /mnt

and then mounted the ESP with:

mount /dev/sda1 /mnt/boot/efi

and then you chrooted:

manjaro-chroot /mnt /bin/bash
or
manjaro-chroot /mnt

(the /bin/bash is optional, you’ll get a sh-5.2 prompt without it, while you get a red root bash prompt with it)

You could adapt the title or create a new topic, with the relevant steps that you took as documented here, so that people will not have to go back here to see what was done.

23

Yes, these are my steps:

cryptsetup luksOpen /dev/sdat /tmp
mount /dev/mapper/tmp /mnt
mount /dev/sda1 /mnt/boot/efi
manjaro-chroot /mnt
24

That looks semi correct.

In the first line It should be just tmp - not /tmp
(it is just a name which you refer to, not a path
I used “encrypted” im my example to avoid confusion, to be clear)
and it should be /dev/sda2 - not /dev/sdat

What is (still) the issue now?

As to your question - I just added to my previous reply.
It may be better to start a new topic.

25

This is the current problem:

I follow your advise and create a new topic. As for this issue, I will test whenever I overcome this grub problem and mark the solution here. I think we found the root cause for the mapping issue, i.e. a wrong hooks configuration.

Yes, you are correct. Sorry for the typo!

This is also my bad, sorry for the typo again!

Thanks to all for your time!

26

As suggested, I created a follow-up issue:

27

Closed as abandoned topic.