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

[UnAcknowledged]

Hi there,

First of all let me state I am by no means very good with Linux, it is something i enjoy and play about with in my spare time. I am not very good with commands, so be patient with me please.

So I have been running Manjaro for a long while and it has been working great. The latest update has borked my system though as i use the full LUKS Encryption. Upon entering my passphrase, the GRUB menu flashes for a millisecond, disappears and then I am met with

“error: no such cryptodisk found.”

“Press any key to continue.”

Now upon trying to press a key, the system freezes so it becomes impossible to really do anything. The best i get is if i type my password phrase wrong at encryption, that is only place I can type.

Anybody who can help will be great appreciated.

P.S I have searched before making this, but to be totally honest, a lot of the threads are people who have access to their grub menu and I do not have access. And other threads, go way beyond my understanding of Linux in general. So a step by step would be real handy.

Thanks very much.

[maycne.sonahoz]

@philm

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

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

• Check for modifications to /etc/default/grub
  Most notably, if you use LUKS with full disk encryption, you may need to:
  • check that GRUB_ENABLE_CRYPTODISK=y is not commented out
• Don’t use tools like grub-customizer as it may create issues with the grub.cfg file.
• Check if the UUID of your encrypted drive matches in your config files.
• 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.
• If you modified the above configuration, you then need to update the grub menu with sudo update-grub.
• A message “no such cryptodisk found” may appear on the following reboot, but should not prevent you from continuing by typing any key.

You may still want to have a liveUSB ready, in the rare case your bootloader does break, in which case you will need to reinstall grub .

For more details:

• [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

At this point, you would need to ready a liveUSB from another computer in order to fix your system.

[UnAcknowledged]

Cheers mate,

But i must say i need more than that. I have a liveUSB and i don’t really see where i can troubleshoot with it.

[bogdancovaciu]

@UnAcknowledged

i need more than that

This

[HowTo] Recovering from an interrupted update/upgrade

Difficulty: ★★☆☆☆ So you couldn’t wait until the update process had completed and you went for the reset/power button, didn’t you? And now you’re getting the message that you don’t have a kernel installed. Well, you’re not the only one — we’re seeing it happen all the time. So, here’s how to fix it, you impatient n00b. If you don’t happen to have a recent Manjaro installer USB/DVD/CD handy, direct your browser to this wonderful page, download…

[andreas85]

"no such cryptodisk found" error without breaking boot-up ?!

Those who have the issue should install this grub package and confirm it is working …

[inverser]

I get the same message, but when I press any key, the system continues to boot, God Save Linus.
Yesterday there were system updates and this message did not appear at boot, however, today I saw it again.

[philm]

You have two options:

• re-run update-grub which should remove the dashes from your UUID entry of crytomount lines in your /boot/grub/grub.cfg
• or re-install grub to your MBR/EFI: GRUB/Restore the GRUB Bootloader - Manjaro. This will add support also for UUIDs with dashes.

All in all the error is well explained already.

[inverser]

I didn’t see your message, but I installed a new kernel version (6.3) and the error message disappeared.
Thank U