Can't boot encrypted Manjaro after installing Windows 10.

A tip about formatting code: Use three accents, then new line, than paste code, then new line and three accents again. Like this:

```
some code bla bla
```
3 Likes

I don't use encrytion, but try this TEST F here. Make sure you start install media in the right mode (uefi or bios-legacy - quickly glanced, I think it is bios-legacy in your case). And should you get it working, suggest you make a grub-rescue cd/usb with your grub.cfg embedded in it.

Good luck.

3 Likes

For the entire time I used the same UEFI livecd USB drive.

Take a picture or write down what comes after "Enter passphrase for hd#,gpt# (xxxx...): _"
20190917_121832

When looking for the actual hd#,gpt# be mindful that you might mistake your efi partition with the efi that's in the livecd USB/CD.

I thought the number in "crypto0" was dependent on your gpt# number, it's not. I did try "crypto2" unsuccessfully.

When looking for your own hd#,gpt# by running the "cyrptomount hd#,gpt#" you'll know you got the right one when you see:
"Attempting to decrypt master key...
Enter passphrase for hd#,gpt# (The UUID # you see when you are prompted for a password at the beginning of the boot)
20190917_184303

After running boot you should see:
20190917_184323
and boot to Manjaro.

Be sure to create the grub-rescue cd/usb that gohlip mentiond. It was the first thing I did as soon as I got to the desktop.
For some reason xorriso doesn't show up in Octopi, so I just ran

sudo pacman -S xorriso

Big thumbs up to gohlip and everyone else who chipped in.

I'll restart the computer and hope I don't have to come back in 2 minutes to take down the mission accomplished banner.

2 Likes

:sweat_smile:
20190917_192815

gohlip how do I use the grub rescue iso?
I made both the prompt and menu ones.
I think I need to delete /new_root: can't find UUID=ee80... since it doesn't match the one at boot.

I think the package xorriso is not in pacman repositories.
But I think it is in other distros.
No worries, the package required in place of xorriso is libisoburn
{Previously the package is named libisoburn-xxxx, and I forget what these 'xxxx' is}

[pop@Dec ~]$ pacman -Ss libisoburn
extra/libisoburn 1.5.0-2
    frontend for libraries libburn and libisofs
community/disomaster 5.0.0-1
    A libisoburn wrapper class for Qt
[pop@Dec ~]$ pacman -Ss xorriso
extra/libisoburn 1.5.0-2
    frontend for libraries libburn and libisofs
[pop@Dec ~]$ 

So install libisoburn and proceed. But fix the UUID first, make sure it boots up and then make the rescue-cd. Good luck.

[EDIT] - Confirm xorriso is in ubuntu paclkage, so as is libisoburn but named as 'libisoburn1'

pop@Aug:~$ apt search xorriso
xorriso/disco 1.5.0-1build1 amd64
  command line ISO-9660 and Rock Ridge manipulation tool

pop@Aug:~$ apt search libisoburn
libisoburn1/disco 1.5.0-1build1 amd64
  library to handle creation and inspection of ISO-9660 file systems

From my previous post I was able to boot to my Manjaro desktop and then I followed the steps from a grub-rescue cd/usb to make a simple grub rescue iso and a menu grub rescue iso.
Are the steps you're showing here to make the isos or to burn the isos?

To fix the UUID do I just delete any entries related to UUID=ee80d713... inside /etc/fstab and /boot/grub/grub.cfg ?

Or should I follow these steps https://www.reddit.com/r/archlinux/comments/7jne2m/device_not_found_new_root_not_file_system/dr7we8b/

nano /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
/dev/mapper/luks-b98b7c10-be38-4ad2-9386-db4c85e08436 /home          ext4    defaults,noatime,discard 0 2
UUID=D21E-4DD9                            /boot/efi      vfat    defaults,noatime 0 2
/dev/mapper/luks-17a2a4d7-50ad-464a-a5ac-b296631a8dae /              ext4    defaults,noatime,discard 0 1
/dev/mapper/luks-26c904e6-54b6-48bc-afe4-f11ae1e50291 swap           swap    defaults,noatime,discard 0 2
tmpfs

nano /boot/grub/grub.cfg

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

set menu_color_normal=light-gray/black
set menu_color_highlight=green/black

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod cryptodisk
insmod luks
insmod gcry_rijndael
insmod gcry_rijndael
insmod gcry_sha256
insmod ext2
cryptomount -u 17a2a4d750ad464aa5acb296631a8dae
set root='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'  ee80d713-9c90-4a29-94ca-64f1766ac102
else
  search --no-floppy --fs-uuid --set=root ee80d713-9c90-4a29-94ca-64f1766ac102
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Manjaro Linux' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-ee80d713-9c90-4a29-94ca-64f1766ac102' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_gpt
        insmod cryptodisk
        insmod luks
        insmod gcry_rijndael
        insmod gcry_rijndael
        insmod gcry_sha256
        insmod ext2
        cryptomount -u 17a2a4d750ad464aa5acb296631a8dae
        set root='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'  ee80d713-9c90-4a29-94ca-64f1766ac102
        else
          search --no-floppy --fs-uuid --set=root ee80d713-9c90-4a29-94ca-64f1766ac102
        fi
        linux   /boot/vmlinuz-4.19-x86_64 root=UUID=ee80d713-9c90-4a29-94ca-64f1766ac102 rw cryptdevice=/dev/sdg1:lvm loglevel=3 quiet
        initrd  /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
}
submenu 'Advanced options for Manjaro Linux' $menuentry_id_option 'gnulinux-advanced-ee80d713-9c90-4a29-94ca-64f1766ac102' {
        menuentry 'Manjaro Linux (Kernel: 4.19.69-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.69-1-MANJARO x64-advanced-ee80d>
                load_video
                set gfxpayload=keep
                insmod gzio
                insmod part_gpt
                insmod cryptodisk
                insmod luks
                insmod gcry_rijndael
                insmod gcry_rijndael
                insmod gcry_sha256
                insmod ext2
                cryptomount -u 17a2a4d750ad464aa5acb296631a8dae
                set root='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'
                if [ x$feature_platform_search_hint = xy ]; then
                  search --no-floppy --fs-uuid --set=root --hint='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'  ee80d713-9c90-4a29-94ca-64f1766ac102
                else
                  search --no-floppy --fs-uuid --set=root ee80d713-9c90-4a29-94ca-64f1766ac102
                fi
                linux   /boot/vmlinuz-4.19-x86_64 root=UUID=ee80d713-9c90-4a29-94ca-64f1766ac102 rw cryptdevice=/dev/sdg1:lvm loglevel=3 quiet
                initrd  /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
        }
        menuentry 'Manjaro Linux (Kernel: 4.19.69-1-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.69-1-MANJA>
                load_video
                set gfxpayload=keep
                insmod gzio
                insmod part_gpt
                insmod cryptodisk
                insmod luks
                insmod gcry_rijndael
                insmod gcry_rijndael
                insmod gcry_sha256
                insmod ext2
                cryptomount -u 17a2a4d750ad464aa5acb296631a8dae
                set root='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'
                if [ x$feature_platform_search_hint = xy ]; then
                  search --no-floppy --fs-uuid --set=root --hint='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'  ee80d713-9c90-4a29-94ca-64f1766ac102
                else
                  search --no-floppy --fs-uuid --set=root ee80d713-9c90-4a29-94ca-64f1766ac102
                fi
                linux   /boot/vmlinuz-4.19-x86_64 root=UUID=ee80d713-9c90-4a29-94ca-64f1766ac102 rw cryptdevice=/dev/sdg1:lvm loglevel=3 quiet
                initrd  /boot/initramfs-4.19-x86_64-fallback.img
        }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sdf1)' --class windows --class os $menuentry_id_option 'osprober-efi-D21E-4DD9' {
        insmod part_gpt
        insmod fat
        set root='hd5,gpt1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-ieee1275='ieee1275//disk@0,gpt1' --hint-bios=hd5,gpt1 --hint-efi=hd5,gpt1 --hint-baremetal=ahci5,gpt1  D21E-4DD9
        else
          search --no-floppy --fs-uuid --set=root D21E-4DD9
        fi
        chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
set timeout_style=menu
if [ "${timeout}" = 0 ]; then
  set timeout=10
fi
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/60_memtest86+ ###
if [ "${grub_platform}" == "pc" ]; then
    menuentry "Memory Tester (memtest86+)" --class memtest86 --class gnu --class tool {
        search --fs-uuid --no-floppy --set=root --hint='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'  ee80d713-9c90-4a29-94ca-64f1766ac102
        linux16 /boot/memtest86+/memtest.bin
    }
fi
### END /etc/grub.d/60_memtest86+ ###

The link "making grub-mkrescue" is to make the iso file.
To make the bootable usb, I normally use dd

sudo dd bs=4M if=anyname.iso of=/dev/sdd

ps: as usual, careful that you choose of=/dev/sdx carefully and 'x' and not 'xy'
and 'if=anyname.iso' is the path to the made iso file.
So from root, it may be "of=/home/<manjarouser>/anyname.iso"
Remember 'dd' is not called 'disk destroyer' for nothing.
But if in doubt, use a safer burning tool like k3b (kde) or brasero (gnome) or any other disk burner that comes with your DE.

Long ago, I burn to a cdrom or dvd, remember it takes less than 50 MB; but now I don't do this anymore but I don't have encryption (and I have another way for my many OS's and too complicated for just a few OS's).

As for the UUID, if you boot up from Manjaro's grub without any error message, that should be fine and usable for this grub-rescue cd. But print out in full this error message if you get it from the grub boot. I cannot see this message

If unsure, provide
sudo blkid
cat /etc/crypttab
cat /etc/fstab {if changed}

Oh... your fstab... not a good thing to have 'discard'
Make that

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
/dev/mapper/luks-b98b7c10-be38-4ad2-9386-db4c85e08436 /home          ext4    defaults,noatime 0 2
UUID=D21E-4DD9                            /boot/efi      vfat    defaults,noatime 0 0
/dev/mapper/luks-17a2a4d7-50ad-464a-a5ac-b296631a8dae /              ext4    defaults,noatime 0 1
/dev/mapper/luks-26c904e6-54b6-48bc-afe4-f11ae1e50291 swap           swap    defaults,noatime 0 2
# tmpfs


Note I removed 'discard' in all entries
I change /boot/efi pass from 0 2 to 0 0
and commented out tmpfs

Do again 'sudo update-grub' and see if error message is still there. I think your UUID is alright but without your /etc/crypttab and blkid, I'm not too sure. Just thinking that that should be correct somehow.

Good luck.

sudo blkid
/dev/nvme0n1p1: UUID="4aee0162-caa8-4ba8-90e7-422f514bebd7" TYPE="crypto_LUKS" PARTUUID="1d758fc9-854b-574a-8f40-b94fc5e78903"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/sda1: UUID="71a824ab-0637-4256-ae13-05837370b207" TYPE="crypto_LUKS" PARTUUID="000ea751-01"
/dev/sdb1: UUID="b98b7c10-be38-4ad2-9386-db4c85e08436" TYPE="crypto_LUKS" PARTUUID="3a8aa0af-ecc6-4067-8710-331b899f7487"
/dev/sdc1: UUID="2019-03-12-09-01-11-00" LABEL="M1804" TYPE="iso9660"
/dev/sdc2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="BB93-7505" TYPE="vfat"
/dev/sde1: UUID="ce3460e9-3be5-4d70-8f41-1c897bc8d53c" TYPE="crypto_LUKS" PARTUUID="9a2e14e1-452b-468c-920a-0118db0a4a48"
/dev/sdf2: UUID="AE2405DD2405A983" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="13aa7681-f160-42f9-8456-9b2bfb2beb84"
/dev/sdg1: UUID="D21E-4DD9" TYPE="vfat" PARTUUID="b00c57c5-828c-4f75-aa6d-82a51ebde768"
/dev/sdg2: UUID="17a2a4d7-50ad-464a-a5ac-b296631a8dae" TYPE="crypto_LUKS" PARTUUID="ee7d1d95-ab33-41f4-8eb6-be49b48bfddc"
/dev/sdg3: UUID="26c904e6-54b6-48bc-afe4-f11ae1e50291" TYPE="crypto_LUKS" PARTUUID="cdd81626-86e3-4148-ba96-ea2c68df5ce1"
/dev/mapper/crypto_LUKS: UUID="ee80d713-9c90-4a29-94ca-64f1766ac102" TYPE="ext4"
/dev/sdf1: PARTLABEL="Microsoft reserved partition" PARTUUID="9d51f56e-ae03-4200-90bd-2362e69ac4e9"
cat /etc/crypttab
# /etc/crypttab: mappings for encrypted partitions.
#
# Each mapped device will be created in /dev/mapper, so your /etc/fstab
# should use the /dev/mapper/<name> paths for encrypted devices.
#
# See crypttab(5) for the supported syntax.
#
# NOTE: Do not list your root (/) partition here, it must be set up
#       beforehand by the initramfs (/etc/mkinitcpio.conf). The same applies
#       to encrypted swap, which should be set up with mkinitcpio-openswap
#       for resume support.
#
# <name>               <device>                         <password> <options>
luks-b98b7c10-be38-4ad2-9386-db4c85e08436 UUID=b98b7c10-be38-4ad2-9386-db4c85e08436     /crypto_keyfile.bin luks
luks-17a2a4d7-50ad-464a-a5ac-b296631a8dae UUID=17a2a4d7-50ad-464a-a5ac-b296631a8dae     /crypto_keyfile.bin luks
luks-26c904e6-54b6-48bc-afe4-f11ae1e50291 UUID=26c904e6-54b6-48bc-afe4-f11ae1e50291     /crypto_keyfile.bin luks

I made the changes you said for /etc/fstab.

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
/dev/mapper/luks-b98b7c10-be38-4ad2-9386-db4c85e08436 /home          ext4    defaults,noatime 0 2
UUID=D21E-4DD9                            /boot/efi      vfat    defaults,noatime 0 0
/dev/mapper/luks-17a2a4d7-50ad-464a-a5ac-b296631a8dae /              ext4    defaults,noatime 0 1
/dev/mapper/luks-26c904e6-54b6-48bc-afe4-f11ae1e50291 swap           swap    defaults,noatime 0 2
# tmpfs
sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
Found Windows Boot Manager on /dev/sdg1@/EFI/Microsoft/Boot/bootmgfw.efi
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.

sdc1 is the livecd USB so it should be fine to have the error.

Rebooting to check the results.

I still get the same error message from the picture above:

mount: /openswap_keymount: no filesystem type specified.
Failed to open key file.
umount: can't unmount openswap_keymount: Invalid argument
ERROR: resume: no device specified for hibernation
mount: /new_root: can't find UUID=ee80d713-9c90-4a29-94ca-64f1766ac102.
sh: can't access tty; job control turned off
[rootfs ]#

I don't get it, do you run update-grub while on a Live USB session? You need to chroot the encrypted system first, then run update-grub from within chroot.

I booted the live usb session, ran the steps in How to chroot into an encrypted root partition to chroot into the encrypted system, and then ran "sudo update-grub" as the last step before rebooting.

Ok, then do it again, but run grub-install with correct target and then update-grub. In a chroot you are su, no need for a sudo command.

So you did not do 'update-grub' from the installed OS but chrooted to it? No wonder.
You had successfully booted into it using TEST F before. Can't you do it again?
And then do 'update-grub'?

Now, I need to get the 'raw' UUID of your root partition. In TEST F, it is $pqr.
So can you when doing TEST F to go into the installed OS, find that out for me and copy that out for us? That will be at steps here during TEST F.

grub> cryptomount hd4,gpt2
grub> set root=(crypto0)
grub> probe -u $root --set=pqr
grub> echo $pqr

Now, here's the entry I made for you to be put into your custom.cfg to boot.
You grub.cfg generated at chroot is wrong.

root=UUID=ee80d713-9c90-4a29-94ca-64f1766ac102 rw cryptdevice=/dev/sdg1:lvm loglevel=3 quiet

The UUID is wrong (should be the $pqr) and /dev/sdg1 is wrong.

Here's a menuentry i made pending confirmation of $pqr


menuentry 'Manjaro - 1  Linux' --class manjaro  {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_gpt
        insmod cryptodisk
        insmod luks
        insmod gcry_rijndael
        insmod gcry_rijndael
        insmod gcry_sha256
        insmod ext2
        cryptomount -u 17a2a4d750ad464aa5acb296631a8dae
        set root='cryptouuid/17a2a4d750ad464aa5acb296631a8dae'
        probe -u $root --set=pqr
        set abc=17a2a4d7-50ad-464a-a5ac-b296631a8dae
        linux   /boot/vmlinuz-4.19-x86_64 root=UUID=$pqr rw cryptdevice=UUID=$abc:luks-$abc root=/dev/mapper/luks-$abc
        initrd  /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
}        
     

But you can try it.

To put into custom.cfg,
Make that custom.cfg
sudo touch /boot/grub/custom.cfg
Open up that file and put in the above entry. Save file. That's it. No need to 'update-grub'
When you reboot, the entry will be there, at the bottom.

Reminder - I need $pqr. it is not
ee80d713-9c90-4a29-94ca-64f1766ac102

@manjarouser2364
This post is to @eugen-b. Don't worry about it.
@eugen-b
You have encryption and btrfs, last I remembered, you manually corrected for your grub.cfg as the generated grub.cfg is not done well. Are you on the default grub 2.04-6 ? If yes, can you try to do 'update-grub' and see if that works? Of course, back up your working grub.cfg.

Then try vanilla-grub and see if that works without needing correction. Let us know. Thanks.

ps: I suspect this OP on grub 2.04-6 may have problems. Others not on encryption or btrfs have reported issues as well.

It was a test install, I think I don't have it anymore.
When I make a test install again (I hope soon) I will try to do it as you requested.

1 Like

Thanks. You're a chum.

I'm currently on my actual Manjaro desktop.

grub> echo $pqr
ee80d713-9c90-4a29-94ca-64f1766ac102

20190918_074348

Then try my entry above.
Put it in custom.cfg. To test it out.
OH.. confirm that the test F from grub prompt works again (this time)
I think so. Just need your confirmation (to make me feel better)

A new option does show up at the bottom of the grub menu
20190918_083334
and running it does boot my main Manjaro desktop.

You still want me to do Test F?

Now boot this entry Manjaro -1

Let us know if this works.
I'm preparing another entry 'Manjaro -2 that will work, but I'll also explain why I don't like it.

Here it is...

$abc= raw
$pqr= decrypted

menuentry 'Manjaro - 2   Linux' --class manjaro  {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_gpt
        insmod cryptodisk
        insmod luks
        insmod gcry_rijndael
        insmod gcry_rijndael
        insmod gcry_sha256
        insmod ext2
        cryptomount hd4,gpt2
        set root=(crypto0)
        set pqr=ee80d713-9c90-4a29-94ca-64f1766ac102
        set abc=17a2a4d7-50ad-464a-a5ac-b296631a8dae
        linux   /boot/vmlinuz-4.19-x86_64 root=UUID=$pqr rw cryptdevice=UUID=$abc:luks-$abc root=/dev/mapper/luks-$abc
        initrd  /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
}        
        

Open up the same custom.cfg and add to it You can have as many entries in custom.cfg.

On why I don't like it...
WE have to use..

cryptomount hd4,gpt2

That may change.. with bios. It may become hd3,gpt2, hd2,gpt2 or hd1,gpt2 or go back to hd4,gpt2
And that is not consistent. It the entry don't work, you have to try with one of these .
But you can edit it manually at grub (press 'e') and try to boot.

I was hoping "cryptomount -u 17a2a4d7-50ad-464a-a5ac-b296631a8dae" will work so we don't have to change each time.

So we just have to have Manjaro -3 and hope it works then.

menuentry 'Manjaro - 3   Linux' --class manjaro  {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_gpt
        insmod cryptodisk
        insmod luks
        insmod gcry_rijndael
        insmod gcry_rijndael
        insmod gcry_sha256
        insmod ext2
        cryptomount -u 17a2a4d7-50ad-464a-a5ac-b296631a8dae
        set root=(crypto0)
        set pqr=ee80d713-9c90-4a29-94ca-64f1766ac102
        set abc=17a2a4d7-50ad-464a-a5ac-b296631a8dae
        linux   /boot/vmlinuz-4.19-x86_64 root=UUID=$pqr rw cryptdevice=UUID=$abc:luks-$abc root=/dev/mapper/luks-$abc
        initrd  /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img
}        
        
3 Likes

All 3 Manjaro options boot to the desktop.

Manjaro 1 and 2 show pretty much the same thing when starting:
20190918_090725

Manjaro 3 says:

error: no such cryptodisk found.
Press any key to continue...

but it eventually starts without having to press any key.
20190918_090405

Forum kindly sponsored by