Can't boot LUKS encrypted install after 2023-03-31 stable update

[ivoshm]

After today’s update and reboot I got the following message

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

but reboot continued and worked.

I found a solution that worked for me in the Unstable thread at [Unstable Update] 2023-02-17 - Plasma 5.27 LTS, GNOME, Python - #50 by Skunkie (THX @Skunkie)

[Uberpanda]

Just performed the following steps :

• Uncommented GRUB_ENABLE_CRYPTODISK=y from /etc/default/grub
• update-grub
• mkinitpcio -P

No changes in the kernel panic for 5.4 and 4.19.

[philm]

Personally I don’t use luks and also don’t test it therefore. I only know we pushed the grub update on which I fixed some script to been able to load on older grub MBR installs. As I see it you have to check that all settings needed to load luks are given. Part of that might be the reinstall of grub into MBR. Check this post and see if you missed any step.

[Tobiwan]

If you have

error: no such cryptodisk found , perhaps a needed disk or cryptodisk module is not loaded.

Don’t reinstall grub - it broke my system. I can’t boot anymore.

[cgramms]

Had a small issue, after post-update reboot I ended up in a completely black screen. But launching applications worked fine, so the system was working but no wallpaper and no control panels. After deleting the ~/.cache folder and another reboot everything seems to work fine.

[philm]

@Tobiwan: you may check this post for your luks issue. I also have updated the troubleshoot guide.

[lexay]

I had similar error wihout the “module is not loaded” part

1. I have my grub bootloader encrypted but not my volumes so thats what I did to solve that error:
   commented out /etc/default/grub:

…
#GRUB_ENABLE_CRYPTODISK=y
…

and then sudo update-grub. but now the default manjaro grub theme is not loaded weirdly enough, though it is enabled in /etc/default/grub.

2. I also tried to clear /etc/crypttab file, because I dont have encrypted volumes and I remember this file to be empty in my case. Then I reenabled GRUB_ENABLE_CRYPTODISK=y in /etc/default/grub and sudo update-grub. That did not help and that error: no such cryptodisk found reappeared and so did the manjaro grub theme .

OS boots as usual after pressing any key though. No major errors in logs.

[Tobiwan]

It derailed so fast so quickly (like in xkcd: Success)

Current problem: I read on Reddit that maybe an erroneous entry in /boot/efi or /boot/grub is causing the “out of range pointer”.

So I deleted (I intended to rename them but moved them both the same location ) these folders. (I’m using only one partition for /, home and boot + I’m also using LUKS)

And now grub-install fails: grub-install: error: /boot/efi doesn’t look like an EFI partition. After 20min of googling I found no way to fix this.

Sadly the older BTRFS snapshot does not contain an valid efi.

What can I do?

This were my previous actions:

• boot into live usb OS
• cryptsetup luksOpen /dev/nvme0n1p2 my_encypted_device
• mount -o subvol=@ /dev/mapper/my_encypted_device /mnt
• manjaro-chroot /mnt /bin/bash
• …

[stephane]

see this

Grub rescue: unknown filesystem

see this topic if you need to chroot for grub restore sudo su cryptsetup luksOpen /dev/sdaX crypto ( here volume mapper encrypted ) cryptsetup luksOpen /dev/sdaY swap ( case out encrypted ) mount /dev/mapper/crypto /mnt mount /dev/sda1 /mnt/boot/efi ( if you need Efi ) mount -t proc proc /mnt/proc mount -t sysfs sys /mnt/sys mount -o bind /dev /mnt/dev mount -t devpts pts /mnt/dev/pts/ chroot /mnt grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --rech…

and this

Computer won't boot after Kernel update

[manjaro@manjaro ~]$ sudo manjaro-chroot -a ==> Detected systems: --> 0) Windows --> 1) Manjaro:linux:btrfs:UUID=c16bedf5-da02-4346-bdea-17c05dcadeca ==> Select system to mount [0-1] : 1 ==> ERROR: You can't mount 1! If I type 0 instead of 1 I get the same: [manjaro@manjaro ~]$ sudo manjaro-chroot -a ==> Detected systems: --> 0) Windows --> 1) Manjaro:linux:btrfs:UUID=c16bedf5-da02-4346-bdea-17c05dcadeca ==> Select system to mount [0-1] : 0 ==> ERROR: You can't mount 0!

[Zesko]

@Tobiwan

Sadly the older BTRFS snapshot does not contain an valid efi.

What can I do?

This were my previous actions:

• boot into live usb OS
• cryptsetup luksOpen /dev/nvme0n1p2 my_encypted_device
• mount -o subvol=@ /dev/mapper/my_encypted_device /mnt
• manjaro-chroot /mnt /bin/bash
• …

You need to mount your efi partition to /mnt/boot/efi

Can you show us lsblk -f

[Tobiwan]

I was able to boot Manjaro:

• boot from live usb stick
• instead of selecting “boot with open source / proprietary drivers” (How to install and run Manjaro Linux - YouTube) I selected “detect EFI bootloaders”
• there was two .efi files on the same disk. One called system+something and the other Manjaro+something. The system one was broken but the Manjaro one did work

[Tobiwan]

@ stephane I will try this again after I backup some important data

@Zesko This is lsblk -f from my now working OS

NAME                                          FSTYPE      FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                                          
|-sda1                                        ntfs                       6230467F304659E5                                    
|-sda2                                        vfat        FAT32          E61E-3D10                                           
|-sda3                                                                                                                       
`-sda4                                        BitLocker   2                                                                  
sdb                                                                                                                          
|-sdb1                                                                                                                       
`-sdb2                                        ntfs              Volume   CAC2B439C2B42B97                                    
sdc                                                                                                                          
|-sdc1                                                                                                                       
`-sdc2                                                                                                                       
  `-veracrypt1                                ntfs                       3ED4C14CD4C1075D                      838.5G    85% /mnt/veracrypt1
sdd                                                                                                                          
|-sdd1                                        exfat       1.0   Ventoy   991D-3E9E                                           
`-sdd2                                        vfat        FAT16 VTOYEFI  B228-8EFB                                           
sr0                                                                                                                          
sr1                                                                                                                          
nvme0n1                                                                                                                      
|-nvme0n1p1                                   vfat        FAT32 NO_LABEL B253-C727                             298.7M     0% /boot/efi
|-nvme0n1p2                                   crypto_LUKS 1              205e4e87-163d-4dae-bd7c-3cda9971fa7f                
| `-luks-205e4e87-163d-4dae-bd7c-3cda9971fa7f btrfs                      e7d503ab-58a1-4148-bbc9-9dccf89b6a20  427.7G    76% /var/log
|                                                                                                                            /home
|                                                                                                                            /var/cache
|                                                                                                                            /
`-nvme0n1p3                                   crypto_LUKS 1              8b452496-c619-4399-b0f5-0e387d52567b                
  `-luks-8b452496-c619-4399-b0f5-0e387d52567b swap        1     swap     a038d7b2-6bad-495b-812e-9e3c33303bf3                [SWAP]

And you are right Zesko - /boot/efi is not an folder, it is the first partition of nvme0n1. I should have figured that out myself.

[Zesko]

For you using Grub and Btrfs with encryption

$ cryptsetup luksOpen /dev/nvme0n1p2 my_encypted_device
$ mount /dev/mapper/my_encypted_device -o subvol=@       /mnt
$ mount /dev/nvme0n1p1 /mnt/boot/efi
$ mount /dev/mapper/my_encypted_device -o subvol=@log    /mnt/var/log
$ mount /dev/mapper/my_encypted_device -o subvol=@cache  /mnt/var/cache
$ mount /dev/mapper/my_encypted_device -o subvol=@home   /mnt/home
$ manjaro-chroot /mnt

Then follow:

@Skunkie

Added cryptodisk to grub preload modules in /etc/default/grub

GRUB_PRELOAD_MODULES="cryptodisk part_gpt part_msdos"

Updated grub and rebuild initramfs

$ sudo mkinitcpio -P
$ sudo update-grub

This alone did not fix the error, I then reinstalled grub.

sudo grub-install

Error gone and everything boots as normal.

[Tobiwan]

I did not use cryptsetup + mount + manjaro-chroot because I was able to boot into my OS with some tricks.

update-grub seems to work

But mkinitcpio throws some errors. How can I remove the preset for 6.0? The kernel application and mhwd-kernel do not list it as installed (I think because the kernel was removed) EDIT: I will move /etc/mkinitcpio.d/linux60.present to my desktop

==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux60.preset: 'default'
  -> -k /boot/vmlinuz-6.0-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.0-x86_64.img
==> ERROR: specified kernel image does not exist: '/boot/vmlinuz-6.0-x86_64'
==> Building image from preset: /etc/mkinitcpio.d/linux60.preset: 'fallback'
  -> -k /boot/vmlinuz-6.0-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.0-x86_64-fallback.img -S autodetect
==> ERROR: specified kernel image does not exist: '/boot/vmlinuz-6.0-x86_64'

But for my current kernel 6.2 there are no errors

==> Building image from preset: /etc/mkinitcpio.d/linux62.preset: 'default'
  -> -k /boot/vmlinuz-6.2-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.2-x86_64.img --microcode /boot/amd-ucode.img
==> Starting build: '6.2.8-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
  -> Running build hook: [openswap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.2-x86_64.img'
bsdtar: Failed to set default locale
bsdtar: Failed to set default locale
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux62.preset: 'fallback'
  -> -k /boot/vmlinuz-6.2-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-6.2-x86_64-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.2.8-1-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
  -> Running build hook: [openswap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.2-x86_64-fallback.img'
bsdtar: Failed to set default locale
bsdtar: Failed to set default locale
==> Image generation successful

And grub-install fails too:

Installing for x86_64-efi platform.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: error: disk `hostdisk//dev/nvme0n1p1' not found.

What can I fix this error?

I’m currently to afraid to reboot just for testing

[Zesko]

@Tobiwan

How can I remove the preset for 6.0?

rm /etc/mkinitcpio.d/linux60.preset

@Tobiwan

Installing for x86_64-efi platform.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: warning: disk does not exist, so falling back to partition device /dev/nvme0n1p1.
grub-install: error: disk `hostdisk//dev/nvme0n1p1' not found.

What can I fix this error?

Can you show us df -H /boot/efi in chroot?

[Tobiwan]

Can you show us df -H /boot/efi in chroot?

I see - the one website explicitly says “Boot from a rescue disk and reinstall grub from there!”. Give me a sec

[Tobiwan]

@Zesko grub-install have worked in chroot (and I forget to execute and write down the result of df -H /boot/efi - but I think this is no longer necessary). So I guess I have successfully reinstalled grub.

@Zesko Can you fix the typo in sudo mkinicpio -P to sudo mkinitcpio -P for the next person who will execute this command?

The current situation is, that my mainboard detects two possible boot methods.

• The first method (I think it is /efi/boot/bootx64.efi) that usually worked will caused the critical 452: out of range pointer: 0x95a5c020 error in (I guess) grub - see https://forum.manjaro.org/uploads/default/optimized/3X/3/7/37bacf5fa71afa8d0a0419c4faeb9e8a100bb516_2_666x500.jpeg.
• But the second method (I think it is /efi/Manjaro/grubx64.efi) works without a problem.

So my current workaround will be to change the boot order of my mainboard. I will google to check if there is a better solution.

[ruziel]

I had the same error trying to boot an encrypted system & followed the steps to reinstall Grub. Unfortunately, now I am just in some weird loop where it keeps taking me to the boot menu where all I can do is select my main SSD & it starts all over again.

I am trying to find a solution online but finding it very confusing. I think I need to some how mount my encrypted disk & chroot into it. I’m lost currently! I do have a Timeshift restore point but don’t know how to get to it.

Thanks, Ruziel

[Tobiwan]

@ruziel Can you

• create a live Manjaro usb stick? (Normally used to install or test Manjaro). E.g. with Ventoy
• boot from the USB stick
• select “Detect EFI bootloaders”
• and select the /efi/Manjaro/grubx64.efi?

I was able to boot into my normal OS and access my personal files.

But if you want to chroot/reinstall grub, you have to select “Boot with * drivers”.

[ruziel]

@Tobiwan Thanks! Okay, so I’m into my system. I’m just unsure how to fix my system from here. There seem to be several approaches suggested. When I followed the “sudo mkinitcpio -P” and then updated Grub, that’s when my problems got worse. Before that, I could at least boot into my system. I have a Timeshift restore point. Should I apply that & try the update again? Thanks a lot for your help. Ruziel…