With this configuration of mkinitcpio.conf, the issue is resolved.
KDE, Kernel 5.4.77, encrypted root fs.
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES="/crypto_keyfile.bin"
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect block filesystems)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev block lvm2 filesystems)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard encrypt openswap resume filesystems fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
I also ran into problems with this update and encryption – receiving the error @waranty92 is mentioning (“ERROR /dev/…/luks… not found”) and thus being unable to boot the system. Shout out to @waranty92@openminded who have been discussing related issues on this thread and hinting at the missing encrypt hook.
For me the problem could be solved by:
Boot from USB
Mount encrypted drive and chroot into Manjaro
Change the HOOKS line in /etc/mkinitcpio.conf from
Why was the encrypt hook removed from /etc/mkinitcpio.conf during update in the first place? This may be undesired behaviour, especially if the currently running system is using encryption?
Why were all kernels/fallback initramfs affected? I had hoped, that after an update problem like this, I would be able to boot selecting another GRUB entry and to fix the system without requiring a bootable USB drive (which one may not always have handy).
I would try re-downloading the configs from pia. There were some major changes to openvpn in 2.5.0 that would require changes to configurations. If that doesn’t work then you may need to roll openvpn back to the prior version until pia updates their configurations to work with the updated version of openvpn. Here is a link to how to downgrade to the prior version of openvpn.
You would also want to add openvpn to the “ignore upgrades for” section in the preferences under advanced tab in the pamac gui until pia updates their configurations and you can continue on with the current version of openvpn.
Before launching this update and upgrading Thunderbird (with Enigmail) from its version 68.12 to the 78.4.3 one, I would like to know if someone has tested this migration from Enigmail to the Thunderbird key management. On this forum, I can only find:
But it does not necessarily mean that it works well…
Thanks for your attention.
After a while I discovered it was an issue with plasma and the fish shell, I solved it by chshing to zsh (bash works too) and setting konsole to start /usr/bin/fish in profile settings. This is a bug with the way fish works, and they don’t seem to care for fixing it.
A problem has been detected with this installation of MKVToolNix:
The versions of mkvmerge (51.0.0) and the GUI (1..) differ.
Certain functions won't work correctly in this situation. Please re-install MKVToolNix or fix the problem manually.
I could not load my DE after the update (just a black screen) but i could switch to a TTY. I went back to kernel 5.8 and was able to boot fine. Confirmed my nvidia driver was at 450.
I booted back into kernel 5.9 and from the TTY I reinstalled the nvidia-450 driver ( mhwd -i pci video-nvidia-450xx ). I confirmed when it prompted to reinstall nvidia-450.
This resolved the issue for me, hope that helps someone
Had to restore from the lvm snapshot. All the initramfs fail because of “unknown filesystem type” while trying to mount /new_root. I wonder they can’t find /dev/mapper/root_lv anymore, ext4 on lvm2.
/etc/mkinitcpio.conf has
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
And previously worked like a charm. Ideas?
Some hooks that may be required for your system like lvm2 , mdadm , and encrypt are NOT enabled by default. Read the #HOOKS section carefully for instructions.
Forgot to check package list so 5.9 was installed (which doesn’t work with nvidia drivers yet)
5.8 no longer works after update
Failed to start kernel modules
Failed to start CLI Netfilter Manager
Failed to mount /boot/efi
Dependency failed for Local File System
In an attempt to fix it, I booted from usb and tried to do a grub reinstalled (the usual fix when I have boot issue in the past). Now the grub menu no longer shows up and it goes straight to the lastest version that doesn’t work (Failed to load Light Display Manager). Removed linux-latest / 5.9 manually, but grub and 5.8 still doesn’t seem to work anymore (also tried to downgrade grub).
Grub no longer recognize my nvme drive while doing probing (windows dual boot)
Anyone else having similar issue? Any idea on how to fix this?
amd r5 2600x cpu / nvidia 2060 super gpu. nvme boot drive (both os)
