LUKS Error after latest major update Manjaro KDE

[anon89812132]

Have you tried following the update announcement wiki, or the forum search?

@philm

2023-03-31

GRUB, LUKS and full disk encryption: ‘no such cryptodisk found’

Following grub’s update, new configuration may be needed to be manually applied:

• Based on the manual , unlike filesystem UUIDs, UUIDs for encrypted devices must be specified without dash separators. So check /boot/grub/grub.cfg for entries like cryptomount -u 3722dfb2-3b32-414b-bd59-4329fa92b6a9 and try to remove the dash separators. You have to redo that whenever you update a kernel or call update-grub on your own. You can read more about it here
• A message “no such cryptodisk found” may appear on the following reboot, but should not prevent you from continuing by typing any key. This happens if you forgot to remove the dashes in /boot/grub/grub.cfg after update-grub got called.

We may add a alpm-hook to grub package to do that monkey job for you automatically. As an alternative you may reinstall grub , as the newer version can handle both cases, including the dashes.

For more details:

• Can’t boot LUKS encrypted install after 2023-03-31 stable update - #95 by philm
• [SOLVED] error: no such cryptodisk found / Newbie Corner / Arch Linux Forums
• Can’t boot LUKS encrypted install after 2023-03-31 stable update
• [Stable Update] 2023-03-31 - Kernels, Plasma 5.27 LTS, Pamac, Phosh, Mesa, LibreOffice - #159 by hifive
• [Unstable Update] 2023-02-17 - Plasma 5.27 LTS, GNOME, Python - #50 by Skunkie
• Can’t boot LUKS encrypted install after 2023-03-31 stable update - #54 by philm