Unable to boot to desktop after latest update

Since last unstable update, I can’t get Manjaro to boot to desktop. Grub boots and I can choose 6.x kernel or 5.x kernel, then the computer logo flashes 7 times and at the 7th time gets stuck at the computer logo.
Any idea how to fix this?

maybe the update got interrupted… boot into manjaro live usb, connect to internet, enter chroot:
manjaro-chroot -a
(this command doesnt work with btrfs or encryption, you have to chroot manually);
rerun update:
pacman-mirrors --fasttrack 5 && pacman -Syyu
any errors from it?

Any idea/pointer as to the cause? You’re using unstable - so I’m assuming you’re somewhat knowledgable in these technical things…

  • And checked at least some logs? ([HowTo] Find error logs)
  • Are there some pacnew files you forgot to merge?
  • What were the packages updated during your last unstable update?
  • Does reverting any of those help your situation?

I’ve done that and now it’s much worse, doesn’t even get to grub menu…

were there any errors when you rerun the update?

No errors during the update. Even chrooted again to reinstall grub and generate grub.cfg and everything went ok, still can’t access grub menu.

I choose boot device from F11 boot select menu, choose the proper Manjaro drive, enter LUKS password, then “Slot 0 opened” (takes longer than usual) then the pc logo flashes 7 times and stays still.

Doesn’t look like I can get any log or dmesg on screen, help if possible.

Can still boot to Windows doesn’t look like anything of that was touched.

should mentioned that you are using encryption… so were you properly chrooted?
you can check logs from the failed boot:
journalctl -b-1 -p5 --no-pager

do I need to chroot again to see that log I guess, or can I just mount the root partition without chrooting?
I can’t check journalctl from the system which is currently failing.

yes you have to chroot…
and how did you chrooted, post the commands here…

The followed steps are simple:

1.Select live manjaro usb from boot menu with F11 (manjaro-kde-21.3.7-220816-linux515.iso)
2.Boot with open source drivers
3.Connect the drive that holds manjaro (turns out to be sdc)
4.Open terminal and run (/mnt is empty)

$ sudo -i
# cryptsetup luksOpen /dev/sdc2 manjaro  #enter passphrase
# mount /dev/mapper/manjaro /mnt/
# mount /dev/sdc1 /mnt/boot/efi/
# manjaro-chroot /mnt/

Will attach the log shortly.

and post with logs also output from:
cat /etc/mkinitcpio.conf

First log:

[manjaro /]# cat /etc/mkinitcpio.conf
# vim:set ft=sh
# 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)

# 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

# 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.

# 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 keymap encrypt filesystems"

# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.

# Additional options for the compressor

there are 2 hooks missing, but maybe that is how it should be on your system…

ok, so you are using ZFS, that could be also the reason… you have alos xorg dumped cores…
try reinstalling:
pacman -S zfs-utils

Is your /boot also encrypted? Otherwise, including the key file into the unencrypted boot partitions defeats the encryption totally.

reinstallling the zfs kernel modules didn’t fix anything, still not getting to grub menu.

yes /boot is encrypted the one which is not is /boot/efi/ which is a different physical partition.

I don’t believe it has something to do with zfs. It fails starting X11 and occurred after an update
More likely is the Nvidia driver. Did you already clear this?

Clear what? How can I fix it?
Maybe because of the switch I made?

You never resolved the other thread. :woman_shrugging: