Can’t boot after this update. My installation is luks encrypted. Grub is working but when I try to boot Manjaro, my monitor turns off for a minute or two, then I’m thrown into emergency mode before being asked for my luks passphrase, with a timeout error “waiting for device /dev/.some_ID.” followe…

[image] Armus: I can decrypt and mount the luks partition like normal from a live stick. Hi, i moved your post to a dedicated topic, so you could get more help. Please post the output of inxi -zv8 as preformatted text. Also the log of the update from /var/log/pacman.log could show what went w…

On my notebook I run into the same trouble, while updating several other desktop systems went fine… Solution for me: Boot into a Timeshift snapshot, redo the update sudo pacman -Syu and directly afterwards update & install the Grub bootloader again sudo update-grub & sudo grub-install then reboot.

[image] TheInvisible: Solution for me Did you work out what the problem was though? It’s great you got it working again, but without determining what the problem was it doesn’t really help anyone and it’s just a guess that its the same problem. That said, restoring the previous state from a …

[image] TheInvisible: On my notebook I run into the same trouble, while updating several other desktop systems went fine Was it really the same issue? So on your notebook there is luks encryption and the log was [ TIME ] Timed out waiting for device./dev/. ... and the desktop systems have n…

The solution from Theinvisible does not make any sense, because he did everything in the snapshot. The only thing that is common with his normal boot is the reinstallation of grub, however that is also something a hook automatically does after update, so… Encrypted boot has always been way more pro…

There were two package updates that may be related: device-mapper and lvm2. Here’s the update log: [2026-05-27T16:49:52+0200] [PAMAC] synchronizing package lists [2026-05-27T16:51:17+0200] [ALPM] running '00-timeshift-autosnap.hook'... [2026-05-27T16:51:17+0200] [ALPM-SCRIPTLET] ==> skipping times…

@Armus Please provide your system information in case it reveals any contributors to your issue. Regards. ▶ [Mini-HowTo] Provide System Information

inxi -zv8: System: Kernel: 6.18.18-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 clocksource: tsc avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=de_DE keytable=de tz=UTC misobasedir=manjaro misolabel=MANJARO_KDEM_2604 quiet systemd.show_status=1 spl…

maybe this might fix it: [pkg-upd] 41-2: install/encrypt: add dlopen'ed libcryptsetup (a5d87d40) · Commits · Packages / core / mkinitcpio · GitLab Remember, we don’t test luks encryption on our basic os-update checks. most of our developers don’t use encryption … sudo pacman -U https://mirror.easyn…

I thought using encryption was pretty common. OK, how do I apply this to my system? I can’t access the console from emergency mode. I just realized that an information got lost by removing an unrelated post I replied to: My grub is unencrypted.

Manjaro Linux Forum

Can't boot after stable update 2026-05-27

Support System Updates

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled