Great, you also encrypted your system … Not my cup of tea, so maybe somebody else will pass around to give you some assistance.
Meanwhile here some hints related to that:
Solved.
In etc/default/grub the line GRUB_CMDLINE_LINUX_DEFAULT=… must contain the identifier as a device, not as a UUID. Even if that device has that UUID.
With the data from my OP:
I replaced
resume=/dev/disk/by-uuid/33333333-3333-3333-3333-333333333333
with
resume=/dev/mapper/crypt_sda2 and it works.
Probably (?) because the UUID of /dev/mapper/crypt_sda2 (from blkid) points to all btrfs subvolumes (in fstab), and even if /swap would be correctly identified, the physic…
You will need a Live Media Manjaro install and follow this to recover your system.
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 t…
And make sure you also read this
I just did a fresh Virtualbox VM with 22.0.5 as base and updated to today’s stable update of 2023-04-11. The install used the automatic install mode with LUKS encryption using a normal password.
Boot process:
grub loads and ask for the password
after entering that it takes a short while
the cryptomount -u error happens: [PATCH v5 5/9] cryptodisk: Improve cryptomount -u error message
waiting or pressing any key continues the boot process
Now I’ve to see what changed and how to get that messa…
1 Like