brn
7 April 2023 10:30
86
Cross-posting as this topic seems to have more people, though technically not exactly the same thing (since my problem was having the message, but my computer did still boot). Hopefully that’s OK:
I’d tried everything people suggested in many places, and only one thing worked, but I’m pretty sure it’ll be temporary (until grub is updated):
Mentioned in [Stable Update] 2023-03-31 - Kernels, Plasma 5.27 LTS, Pamac, Phosh, Mesa, LibreOffice :
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.
Changing those 5 lines (with the cryptomount -u command) worked for me, as long as I don’t run sudo update-grub, because that will put back the malformed UUIDs.
Hopefully that will help others and potentially help fix this issue permanently (remove the dashes automatically for encrypted filesystems in the 'cryptomount -ucommand when building the/boot/grub/grub.cfg` file)? Where should I add this information for the involved developers to see?
2 Likes