Fail to boot after update - 20220811

Support
1

Hi there, it’s my first post here so I apologize if I’m missing something but I’m having almost the same problem as the original post which is that after trying to repair my system via chroot (and doing the system update )the screen just gets stock on dell’s logo.

I’ve tried everything until this part of the thread (some commands didn’t worked like mhwd -l && mhwd -li) but, when I run journalctl -b-1 -p3 --no-pager, this is the output:

[manjaro /]# journalctl -b-1 -p3 --no-pager
Aug 04 00:10:46 peter kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x20 (or later)
Aug 04 00:10:46 peter kernel: dw_dmac INTL9C60:00: Missing DT data
Aug 04 00:10:49 peter libvirtd[529]: internal error: Missing udev property 'ID_VENDOR_ID' on '1-1.1'
Aug 04 00:10:49 peter libvirtd[529]: internal error: Missing udev property 'ID_VENDOR_ID' on '1-1.5'
Aug 04 00:10:49 peter libvirtd[529]: internal error: Missing udev property 'ID_VENDOR_ID' on '1-1.6'
Aug 04 00:10:49 peter libvirtd[529]: internal error: Missing udev property 'ID_VENDOR_ID' on '1-1.8'
Aug 04 00:10:55 peter kernel: sd 4:0:0:0: [sdb] No Caching mode page found
Aug 04 00:10:55 peter kernel: sd 4:0:0:0: [sdb] Assuming drive cache: write through
Aug 04 00:11:43 peter agetty[1130]: tty4: invalid character conversion for login name
Aug 04 00:15:34 peter systemd-cryptsetup[1275]: Device luks-b5bde9d0-fb81-4b62-9ae6-a9b1943bc32c is still in use.
Aug 04 00:15:34 peter systemd-cryptsetup[1275]: Failed to deactivate: Device or resource busy

By the way, this is the output from mhwd -l and mhwd -li

[manjaro /]# mhwd -l   
mhwd: error while loading shared libraries: libx86emu.so.3: cannot open shared object file: No such file or directory
[manjaro /]# mhwd -li
mhwd: error while loading shared libraries: libx86emu.so.3: cannot open shared object file: No such file or directory

And this is the output for the kernel

[manjaro /]# mhwd-kernel -li
Currently running: 5.15.53-1-MANJARO (linux515)
The following kernels are installed in your system:
   * linux414
   * linux515
   * linux59
2

you should create a new topic…
and no, you dont have the same problem;
you get stuck at luks, either because there is some program not properly shutdown, or its a kernel issue - trying different kernel, or downgrading kernel
you are running 2 eol kernels: linux414 and linux59, so select the 5.15 in the grub menu and try booting with it

3

Is this a virtual machine or is it your host

There appears to be an error with your container

and it seems there is files missing - which could be a failing disk or an update transaction killed before all hooks was processed.

4

oh …
thanks for clarifying that it is not the same problem, I’ll try what you are mentioning and if it doesn’t work, I’ll better open a new topic.

5

It’s my host, I’ve been running Manjaro for over 3 years and it’s the first time something like this happens :'v and maybe is important to mention that when I enter via chroot, the update process doesn’t show any problem.