[SOLVED] Verbose boot logging to identify blocking process

deltaecho · 2024-05-20 18:42:28

I'm sure it is purely correlation, but since upgrading to KDE 6 I've had trouble booting after just about every system update and I have not been able to identify the offending process. For example, right now I'm debugging why the loader cannot get past, "Loading initial ramdisk ...". My typical debugging workflow includes booting to a live Arch USB, arch-chroot'ing into the root partition, fiddling around with various kernel packages and configurations, recompiling the kernel, and rebooting. Sometimes I roll back or reinstall recent package updates. After an hour or two of debugging I can usually get it to boot successfully, but it hasn't been the same issue twice. Is there a way to enable verbose logging to see which process is blocking the loader, or some logs somewhere that may shed light onto what's going on?

Last edited by deltaecho (2024-05-21 20:34:42)

jl2 · 2024-05-21 08:28:22

you can set some kernel parameters:
* remove "quiet"
* add "loglevel=7" => dmesg debug messages
* "udev.log_level=debug" => udev
* add "systemd.show_status=true" => systemd

also, you might want to change the systemd target to rescue.target: https://wiki.archlinux.org/title/Systemd#Targets

Last edited by jl2 (2024-05-21 08:29:58)

deltaecho · 2024-05-21 20:34:10

These are exactly what I was looking for, thank you!

Arch Linux

#1 2024-05-20 18:42:28

[SOLVED] Verbose boot logging to identify blocking process

#2 2024-05-21 08:28:22

Re: [SOLVED] Verbose boot logging to identify blocking process

#3 2024-05-21 20:34:10

Re: [SOLVED] Verbose boot logging to identify blocking process

Board footer