During LUKS boot I get:
“error: no such cryptodisk found , perhaps a needed disk or cryptodisk module is not loaded.
Press any key to continue …”
But it boots up normally after that, whether I press a key or not.
What’s going on here? Is there a need to do anything? My (LUKS enabled) Manjaro is installed to a USB disk. Hard Disk on PC is a Windows disk but I guess it plays no role since I boot through USB when I start (LUKS) Manjaro
Have you tried following the update announcement wiki, or the forum search?
GRUB, LUKS and full disk encryption: ‘no such cryptodisk found’
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
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
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:
I could not understand those posts. But thanks.
I can boot. Booting is not the issue. The issue is the error message that I posted previously, it pops up during boot, but boot proceeds normally.
How about if I remove # from the following in grub.cfg?
The # is there on its own, should it be there? Is this causing the error?
Uncomment to enable booting from LUKS encrypted devices
Removing the # from the above and updating grub.cfg and rebooting removed the error message during boot and everything is normal now.
But you did understood them, because …
Removing the # from
… was mentioned in the second link from
For more details: on … the arch forum discussion.
April 17, 2023, 8:39am
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.