[Solved]Systemd failed error and unable to boot after kernel update

freewick · 2024-03-10 20:50:49

seth wrote:

Thanks for the files.
Can you now reboot?
Edit: hold on, you didn't run that in the chroot!
You installed the packages into the iso, that's not horrible, but won't help.
You've to chroot or use "--sysroot /mnt"!

So the command now is pacman -S dbus-daemon-units --sysroot/mnt ? . If the command is wrong can u please tell the exact chroot command to do it like before please.

also I moved both the conf files from system.d folder to root folder and saved them. is that fine?

Edit: after mounting root I read archwiki and used arch-chroot /mnt and then ran pacman -S dbus-daemon-units. Is that ok?

Last edited by freewick (2024-03-10 20:56:34)

seth · 2024-03-10 20:54:41

https://wiki.archlinux.org/title/Pacman … an_upgrade

How exactly did you install archlinux?
What instructions did you follow?

freewick · 2024-03-10 21:03:57

seth wrote:

https://wiki.archlinux.org/title/Pacman … an_upgrade
How exactly did you install archlinux?
What instructions did you follow?

I installed using arch wiki as well as followed a youtube video made by average linux user for reference.

I rebooted the system now after doing arch-chroot /mnt and then installing dbus-daemon-units and moved the asusd.conf and other .conf from system.d folder to some other alternate folder in /mnt i.e file system so the files are safe.

I rebooted and still getting errors and then blank screen with cursor and no tty just like before

seth · 2024-03-10 21:05:49

Do you have an updated journal?

freewick · 2024-03-10 21:13:01

seth wrote:

Do you have an updated journal?

I ran the journal command you gave earlier again here is the link

http://0x0.st/HhQA.txt

Last edited by freewick (2024-03-10 21:13:48)

freewick · 2024-03-10 21:15:10

sorry I am typing from my phone while sittinf in front of my laptop at 4 so cant type properly but I want to fix Arch at this point

seth · 2024-03-10 21:22:14

That journal stopped at

Mar 11 00:52:26 sanganaka systemd[1]: Mounted FUSE Control File System.
Mar 11 00:52:26 sanganaka systemd[1]: Mounted Kernel Configuration File System.
Mar 11 00:52:26 sanganaka systemd-journald[367]: Time spent on flushing to /var/log/journal/d7b6e4d7c0214b4fb82f44ee473cc1b0 is 5.798ms for 1278 entries.

Don't reboot w/ the power button.
Try to switch the TTY or restrict the boot to the multi-user.target, 2nd link below.

freewick · 2024-03-10 21:26:32

seth wrote:

That journal stopped at
Mar 11 00:52:26 sanganaka systemd[1]: Mounted FUSE Control File System.
Mar 11 00:52:26 sanganaka systemd[1]: Mounted Kernel Configuration File System.
Mar 11 00:52:26 sanganaka systemd-journald[367]: Time spent on flushing to /var/log/journal/d7b6e4d7c0214b4fb82f44ee473cc1b0 is 5.798ms for 1278 entries.
Don't reboot w/ the power button.
Try to switch the TTY or restrict the boot to the multi-user.target, 2nd link below.

I am currently in arch live media session. I will type reboot and remove pendrive and see what happens and will update u in 5 mins.

freewick · 2024-03-10 21:35:07

seth wrote:

That journal stopped at
Mar 11 00:52:26 sanganaka systemd[1]: Mounted FUSE Control File System.
Mar 11 00:52:26 sanganaka systemd[1]: Mounted Kernel Configuration File System.
Mar 11 00:52:26 sanganaka systemd-journald[367]: Time spent on flushing to /var/log/journal/d7b6e4d7c0214b4fb82f44ee473cc1b0 is 5.798ms for 1278 entries.
Don't reboot w/ the power button.
Try to switch the TTY or restrict the boot to the multi-user.target, 2nd link below.

I just rebooted and booted into arch and then I got bunch of failed to initialize systemd error messages and after that a blank screen with cursor appeared just like before. I tried to access tty by pressing ctrl+alt+f3 and a prompt came with same systemd failed to start errors and errors are still coming and probably will take a lot of time and there is no way to reboot or shut down without the use of power button

ctrl+alt+f1 is showing some failed systemd failed errors
ctrl+alt+f2 is showing blank screen with mouse.
ctrl+alt+f3 is showing some other failed systemd service errors

should I go back to live installation and post journal again by pressing power button?

seth · 2024-03-10 21:44:47

Do not use the power button!
Try whether frenetic use of ctrl+alt+del reboots and if not, try whether you can boot the multi-user or rescue target.
Otherwise enable and use https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

freewick · 2024-03-10 21:52:51

seth wrote:

Do not use the power button!
Try whether frenetic use of ctrl+alt+del reboots and if not, try whether you can boot the multi-user or rescue target.
Otherwise enable and use https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

yes ctrl+alt+delete worked and system went reboot and even then some service errors came. Should I boot into live and post journal here?

seth · 2024-03-10 21:53:29

Yes…

freewick · 2024-03-10 22:01:28

seth wrote:

Yes…

Here is the journal log

https://0x0.st/HhQg.txt

PS: Thank you so much for being online and helping me. I know what I signed up for when I installed arch and because of people like you people like me can figure things and learn. Thank you for making linux better and hopefully one day I can help others like you are helping me.

seth · 2024-03-10 22:14:23

Mar 11 03:18:32 sanganaka systemd-tmpfiles[696]: Detected unsafe path transition / (owned by 999) → /var (owned by root) during canonicalization of var/lib/dbus.
Mar 11 03:18:32 sanganaka systemd-tmpfiles[696]: Detected unsafe path transition / (owned by 999) → /run (owned by root) during canonicalization of run/dbus.

You chown'ed the root FS to UID 999 - mount the the root of the installed system to /mnt, make sure it's correct

stat /mnt

will tell you it belongs to 999.

chown root:root /mnt
chmod 755 /mnt

The re-check

stat /mnt

Also restore the two dbus configs, they're probably not the problem.
Reboot, if you still get problems, post an updated journal.

freewick · 2024-03-10 22:35:46

seth wrote:

Mar 11 03:18:32 sanganaka systemd-tmpfiles[696]: Detected unsafe path transition / (owned by 999) → /var (owned by root) during canonicalization of var/lib/dbus.
Mar 11 03:18:32 sanganaka systemd-tmpfiles[696]: Detected unsafe path transition / (owned by 999) → /run (owned by root) during canonicalization of run/dbus.
You chown'ed the root FS to UID 999 - mount the the root of the installed system to /mnt, make sure it's correct
stat /mnt
will tell you it belongs to 999.
chown root:root /mnt
chmod 755 /mnt
The re-check
stat /mnt
Also restore the two dbus configs, they're probably not the problem.
Reboot, if you still get problems, post an updated journal.

Omg it it finally worked. I am currently typing from the arch session. I am so happy right now . Thank you so much

So the issue seem to be permissions?

here is the new log

https://0x0.st/Hh1K.txt

I moved the conf files to systemd directory and they are there but when I booted I am getting some error

https://i.ibb.co/cDHxkDD/IMG-20240311-035143.jpg

when I booted I got this error from the app which controls power profiles for asus laptops which I installed from https://asus-linux.org/manual/

https://i.ibb.co/W0tSjj4/Screenshot-20240311-040113.png

should I have to do any thing to make it work like before? like reinstall or edit system.d files again?

once again thank you so much.

Last edited by freewick (2024-03-10 23:10:17)

seth · 2024-03-10 22:59:43

pacman -Qo /usr/share/dbus-1/system.d/asusd.conf  /usr/share/dbus-1/system.d/org.supergfxctl.Daemon.conf
id

freewick · 2024-03-10 23:10:32

seth wrote:

pacman -Qo /usr/share/dbus-1/system.d/asusd.conf  /usr/share/dbus-1/system.d/org.supergfxctl.Daemon.conf
id

I reinstalled them and enabled their service using systemctl and they worked like before.
Omg finally the night mare is over. Thank you for helping me. I will mark the post as solved.

PS : How do I become good like you like how to debug how to read errors something like that. Can point me where to start like resources or courses ot curriculum so that I can hopefully debug or give people like you a better info to debug? Once again thank you so much seth

seth · 2024-03-11 08:09:07

1. try stuff
2. break stuff
3. fix stuff
4. repeat

The "Detected unsafe path transition" was actually in the first journal you sent, but the dbus-broker crash-situation (and because dbus failure was the prominent symptom) threw me off.
"good" (surgical) would have been to read the entire journal, but swatting away the most obvious (potential) problems until you hit the crux is less of a chore

Arch Linux

#26 2024-03-10 20:50:49

Re: [Solved]Systemd failed error and unable to boot after kernel update

#27 2024-03-10 20:54:41

Re: [Solved]Systemd failed error and unable to boot after kernel update

#28 2024-03-10 21:03:57

Re: [Solved]Systemd failed error and unable to boot after kernel update

#29 2024-03-10 21:05:49

Re: [Solved]Systemd failed error and unable to boot after kernel update

#30 2024-03-10 21:13:01

Re: [Solved]Systemd failed error and unable to boot after kernel update

#31 2024-03-10 21:15:10

Re: [Solved]Systemd failed error and unable to boot after kernel update

#32 2024-03-10 21:22:14

Re: [Solved]Systemd failed error and unable to boot after kernel update

#33 2024-03-10 21:26:32

Re: [Solved]Systemd failed error and unable to boot after kernel update

#34 2024-03-10 21:35:07

Re: [Solved]Systemd failed error and unable to boot after kernel update

#35 2024-03-10 21:44:47

Re: [Solved]Systemd failed error and unable to boot after kernel update

#36 2024-03-10 21:52:51

Re: [Solved]Systemd failed error and unable to boot after kernel update

#37 2024-03-10 21:53:29

Re: [Solved]Systemd failed error and unable to boot after kernel update

#38 2024-03-10 22:01:28

Re: [Solved]Systemd failed error and unable to boot after kernel update

#39 2024-03-10 22:14:23

Re: [Solved]Systemd failed error and unable to boot after kernel update

#40 2024-03-10 22:35:46

Re: [Solved]Systemd failed error and unable to boot after kernel update

#41 2024-03-10 22:59:43

Re: [Solved]Systemd failed error and unable to boot after kernel update

#42 2024-03-10 23:10:32

Re: [Solved]Systemd failed error and unable to boot after kernel update

#43 2024-03-11 08:09:07

Re: [Solved]Systemd failed error and unable to boot after kernel update

Board footer