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

freewick · 2024-03-09 13:57:19

Yesterday I updated the system as usual and after the update I tried to login but systemd errors are coming with many daemons failing to start and after some time only cursor is visible.

The update is a new kernel update and may be it broke something but I dont know what to do and debug.

Even tty is unavailable as after pressing ctrl + alt+ f3 only prompt is appearing which is not taking any input. I don't know what broke so can some one help me please.

Even with fall back image in grub boot options I am getting the same issue. Until now there were no issue but only after yesterday I am getting this issue. Never broke this bad. Please help.

https://i.ibb.co/vPLZHSQ/IMG-20240309-171151.jpg

https://i.ibb.co/tCRfxk8/IMG-20240309-171110.jpg

https://i.ibb.co/RBF42xB/IMG-20240309-190331.jpg

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

ptchinster · 2024-03-09 20:59:19

Can you boot into a live environment? You can then use journalctl to view logs after mounting your hard drive.

seth · 2024-03-09 22:12:13

Please replace the oversized (and mostly boring) images w/ links.

There's probably some massive or fundamental file corruption breaking systemd or dbus.
From the iso, mount the root FS and run and post

sudo LC_ALL=C pacman -root /mnt -Qkk | grep -v ', 0 altered files' > /tmp/howbadisit.txt
cat /tmp/howbadisit.txt < curl -F 'file=@-' 0x0.st

freewick · 2024-03-10 00:28:15

seth wrote:

Please replace the oversized (and mostly boring) images w/ links.
There's probably some massive or fundamental file corruption breaking systemd or dbus.
From the iso, mount the root FS and run and post
sudo LC_ALL=C pacman -root /mnt -Qkk | grep -v ', 0 altered files' > /tmp/howbadisit.txt
cat /tmp/howbadisit.txt < curl -F 'file=@-' 0x0.st

Thanks for the reply. I am on my phone right now and will replace them once I get home. Also I have live Ubuntu pren drive. Is it possible to do something with it or do I have to burn arch iso into the pendrive and run this command? If I cant debug with ubuntu live media I will do it but is there an alternate command I can try from ubuntu media?

freewick · 2024-03-10 00:29:20

ptchinster wrote:

Can you boot into a live environment? You can then use journalctl to view logs after mounting your hard drive.

Thanks I will try that I have ubuntu live media and I will see what I can do with it.

seth · 2024-03-10 08:51:22

Ubuntu won't ship pacman, if the installed one cannot run or you cannot chroot into the installed system (depends on how much it's compromised) ubuntu won't help you.
You'd at least need pacman-static on top of it.
https://aur.archlinux.org/packages/pacman-static
https://pkgbuild.com/~morganamilo/pacma … 86_64/bin/

freewick · 2024-03-10 10:42:38

seth wrote:

Ubuntu won't ship pacman, if the installed one cannot run or you cannot chroot into the installed system (depends on how much it's compromised) ubuntu won't help you.
You'd at least need pacman-static on top of it.
https://aur.archlinux.org/packages/pacman-static
https://pkgbuild.com/~morganamilo/pacma … 86_64/bin/

Hi thanks for your support.
I booted using arch live iso media and mounted my original root partition and then ran the command you posted.

It says failed to initialoze alpm library.

I am attaching image for what I did.

https://i.ibb.co/6J8jJSw/IMG-20240310-160317.jpg

please help me. I will try to fix this error in the mean time.

seth · 2024-03-10 10:52:33

It says failed to initialoze alpm library.

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
The image shows nothing like this.

You can skip the sudo on the iso, you're root anyway (sorry, I'm using textblocks for this
And ultimately upload the generated textfile.

freewick · 2024-03-10 11:48:54

seth wrote:

It says failed to initialoze alpm library.
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
The image shows nothing like this.
You can skip the sudo on the iso, you're root anyway (sorry, I'm using textblocks for this
And ultimately upload the generated textfile.

Sorry I did not click the image after running the command but after running the command it says " failed to initialize alpm library"

I will try to do that again and run with out sudo and then post the results as I am back on windows just now after unable to figure it out

freewick · 2024-03-10 12:00:30

seth wrote:

It says failed to initialoze alpm library.
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
The image shows nothing like this.
You can skip the sudo on the iso, you're root anyway (sorry, I'm using textblocks for this
And ultimately upload the generated textfile.

Here is the updated image

https://i.ibb.co/StWxxjJ/IMG-20240310-172722.jpg

please help.

seth · 2024-03-10 12:16:31

Sorry, I managed to copypaste my own typo-mess..

LC_ALL=C pacman --root /mnt -Qkk | grep -v ', 0 altered files' > /tmp/howbadisit.txt
cat /tmp/howbadisit.txt | curl -F 'file=@-' 0x0.st

freewick · 2024-03-10 12:46:19

seth wrote:

Sorry, I managed to copypaste my own typo-mess..

LC_ALL=C pacman --root /mnt -Qkk | grep -v ', 0 altered files' > /tmp/howbadisit.txt
cat /tmp/howbadisit.txt | curl -F 'file=@-' 0x0.st

Thank you. This time the commands worked. Here is the log url

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

seth · 2024-03-10 14:10:31

This looks entirely harmless and doesn't explain the boot failure at all.

Try to boot the multi-user.target (2nd link below) and post the system journal.
If that doesn't work, you can access the journal of the installed system from the iso:

journalctl -D /mnt/var/log/journal -b -1
journalctl -D /mnt/var/log/journal -b -1 | curl -F 'file=@-' 0x0.st # to post it

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

seth wrote:

This looks entirely harmless and doesn't explain the boot failure at all.
Try to boot the multi-user.target (2nd link below) and post the system journal.
If that doesn't work, you can access the journal of the installed system from the iso:
journalctl -D /mnt/var/log/journal -b -1
journalctl -D /mnt/var/log/journal -b -1 | curl -F 'file=@-' 0x0.st # to post it

Thank you for helping me. I did as u said and here is the log

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

seth · 2024-03-10 17:54:38

Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Invalid group-name in /usr/share/dbus-1/system.d/asusd.conf +9: group="sudo"
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Invalid group-name in /usr/share/dbus-1/system.d/org.supergfxctl.Daemon.conf +9: group="sudo"
Mar 10 12:14:53 sanganaka dbus-broker-launch[703]: ERROR launcher_run_child @ ../dbus-broker-35/src/launch/launcher.c +326: Permission denied
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: ERROR launcher_run @ ../dbus-broker-35/src/launch/launcher.c +1412: Broken pipe
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]:       run @ ../dbus-broker-35/src/launch/main.c +152
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]:       main @ ../dbus-broker-35/src/launch/main.c +178
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Exiting due to fatal error: -32
Mar 10 12:14:53 sanganaka systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE

https://bbs.archlinux.org/viewtopic.php?id=292494
An alternative would be to replace dbus-broker-units w/ dbus-daemon-units.

Edit: I'm curious whether the script detects the problem with those files. If you don't mind you could run it from a chroot (or you can switch to dbus-daemon-units before, it doesn't require dbus-broker to be actually used)

Edit: and please post the two files

Last edited by seth (2024-03-10 17:56:55)

freewick · 2024-03-10 18:55:26

seth wrote:

Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Invalid group-name in /usr/share/dbus-1/system.d/asusd.conf +9: group="sudo"
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Invalid group-name in /usr/share/dbus-1/system.d/org.supergfxctl.Daemon.conf +9: group="sudo"
Mar 10 12:14:53 sanganaka dbus-broker-launch[703]: ERROR launcher_run_child @ ../dbus-broker-35/src/launch/launcher.c +326: Permission denied
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: ERROR launcher_run @ ../dbus-broker-35/src/launch/launcher.c +1412: Broken pipe
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]:       run @ ../dbus-broker-35/src/launch/main.c +152
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]:       main @ ../dbus-broker-35/src/launch/main.c +178
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Exiting due to fatal error: -32
Mar 10 12:14:53 sanganaka systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE

https://bbs.archlinux.org/viewtopic.php?id=292494
An alternative would be to replace dbus-broker-units w/ dbus-daemon-units.

Edit: I'm curious whether the script detects the problem with those files. If you don't mind you could run it from a chroot (or you can switch to dbus-daemon-units before, it doesn't require dbus-broker to be actually used)

Edit: and please post the two files

Thank you for helping me and debugging this issue. I am still a beginner and still learning stuff. So here is what I understand from your message.

I have to copy paste the script that your linked and run it after I mount the root file system as before using arch live media isn't it? and I think from what I understand the script produces to files which you want me to attach isn't it?

May I know how can I copy that entire thing and run it during arch installer live media as it is too long to type as I have no access to browser or script ?

Also if the script produces files what is their location. Should I upload them the same way like the journalctl log to that 0x0.sh site?

Please tell me if I understand it properly and guide me. Sorry for being a newbie.

Edit1 : Here is what I did to copy that code. I copypasted the code and put it in a file called dbus_debug.sh and put it in a folder in the usb drive of live arch media. Then I mounted the root directory as before and copied the file from usb to /mnt folder and kept it there. Then I cd into that directory and ran bash dbus_debug.sh. However it is giving me some syntax errors. Am I doing this correct?

Last edited by freewick (2024-03-10 19:15:20)

seth · 2024-03-10 19:31:11

You can also download it from http://0x0.st/HhSi.sh (just pasted it there)

However it is giving me some syntax errors. Am I doing this correct?

Possibly - depends on what you see - the script is meant to detect errors in dbus services.

dbus_debug.sh 2>&1 | curl -F 'file=@-' 0x0.st

should™ get you a URL with the output of the script that you can post here.

freewick · 2024-03-10 19:55:07

seth wrote:

You can also download it from http://0x0.st/HhSi.sh (just pasted it there)
However it is giving me some syntax errors. Am I doing this correct?
Possibly - depends on what you see - the script is meant to detect errors in dbus services.
dbus_debug.sh 2>&1 | curl -F 'file=@-' 0x0.st
should™ get you a URL with the output of the script that you can post here.

Thank you for quick reply. I think initially I got the parsing errors because I copied directly for browser to notepad in windows which I think for sure caused them. This time I downloaded the file u provided and renamed it dbus_debug_v2.sh and kept in the root folder and run it and this time it worked fine.

I couldnt able to upload as it is asked something for pipe quote . I am adding image for reference.

https://i.ibb.co/3fDvKsR/IMG-20240311-011920.jpg

seth · 2024-03-10 19:57:21

You've either a single quote too much or a double quote instead of a single quote there.
Edit: but w/o xmlstarlet you're also not getting much out of it, just post the two files that dbus-broker hates, I'll test them here.

Last edited by seth (2024-03-10 19:58:42)

freewick · 2024-03-10 20:07:30

seth wrote:

You've either a single quote too much or a double quote instead of a single quote there.
Edit: but w/o xmlstarlet you're also not getting much out of it, just post the two files that dbus-broker hates, I'll test them here.

Thank you for your patience. I am sorry I typed it wrong. This time I ran it correct by removing the double quote.

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

it is giving the same output as of the image.

I am feeling stupid but please I dont know what two files you are talking about. If u can tell me what commands to run or the location of them that would be great as I am feeling too stupid to figure out

Edit: you mean laucher.c and main.c of dbus-35 folder?. I will upload them

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

seth · 2024-03-10 20:11:43

Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Invalid group-name in /usr/share/dbus-1/system.d/asusd.conf +9: group="sudo"
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Invalid group-name in /usr/share/dbus-1/system.d/org.supergfxctl.Daemon.conf +9: group="sudo"
Mar 10 12:14:53 sanganaka dbus-broker-launch[703]: ERROR launcher_run_child @ ../dbus-broker-35/src/launch/launcher.c +326: Permission denied
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: ERROR launcher_run @ ../dbus-broker-35/src/launch/launcher.c +1412: Broken pipe
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: run @ ../dbus-broker-35/src/launch/main.c +152
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: main @ ../dbus-broker-35/src/launch/main.c +178
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Exiting due to fatal error: -32
Mar 10 12:14:53 sanganaka systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE

You can just curl them into 0x0.st
Have you meanwhile replaced dbus-broker-units? Otherwise you'll at least have to move them out of the way to make dbus-broker happy.

freewick · 2024-03-10 20:20:58

seth wrote:

Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Invalid group-name in /usr/share/dbus-1/system.d/asusd.conf +9: group="sudo"
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Invalid group-name in /usr/share/dbus-1/system.d/org.supergfxctl.Daemon.conf +9: group="sudo"
Mar 10 12:14:53 sanganaka dbus-broker-launch[703]: ERROR launcher_run_child @ ../dbus-broker-35/src/launch/launcher.c +326: Permission denied
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: ERROR launcher_run @ ../dbus-broker-35/src/launch/launcher.c +1412: Broken pipe
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: run @ ../dbus-broker-35/src/launch/main.c +152
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: main @ ../dbus-broker-35/src/launch/main.c +178
Mar 10 12:14:53 sanganaka dbus-broker-launch[702]: Exiting due to fatal error: -32
Mar 10 12:14:53 sanganaka systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
You can just curl them into 0x0.st
Have you meanwhile replaced dbus-broker-units? Otherwise you'll at least have to move them out of the way to make dbus-broker happy.

Thank you for bearing with me. I know I am feeling stupid but can you tell me how to curl them cause I am pretty new and dont know much.

Also how do I replace those whaterver dbus-broker-units please if you can.

Please I am new to this and never thought I have to do these but I am new to linux and used ubuntu for a while and I want to learn thats why I installed arch. Can you please tell me exactly which commands to run exactly and I will do it to curl the files and replace those dbus files . Please I am stupid but just this time I will learn after I fix this as to how to do it

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

seth · 2024-03-10 20:26:42

cat /usr/share/dbus-1/system.d/asusd.conf | curl -F 'file=@-' 0x0.st
cat /usr/share/dbus-1/system.d/org.supergfxctl.Daemon.conf  | curl -F 'file=@-' 0x0.st
pacman -S dbus-daemon-units # this will not replace the file but return to dbus-daemon, which will not commit suicide because of a sketchy service config

The files are apparently from the asusd and supergfx packages and if you need to know how to move files: "man mv"

freewick · 2024-03-10 20:37:57

seth wrote:

cat /usr/share/dbus-1/system.d/asusd.conf | curl -F 'file=@-' 0x0.st
cat /usr/share/dbus-1/system.d/org.supergfxctl.Daemon.conf  | curl -F 'file=@-' 0x0.st
pacman -S dbus-daemon-units # this will not replace the file but return to dbus-daemon, which will not commit suicide because of a sketchy service config

The files are apparently from the asusd and supergfx packages and if you need to know how to move files: "man mv"

Thank you so much for your patience. I ran those commands amd uploaded to 0x0

here are the urls and addind image to for reference.

http://0x0.st/HhSY.txt
http://0x0.st/HhSg.txt

https://i.ibb.co/C5mGQDD/IMG-20240311-020340.jpg

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

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"!

Last edited by seth (2024-03-10 20:42:44)

Arch Linux

#1 2024-03-09 13:57:19

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

#2 2024-03-09 20:59:19

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

#3 2024-03-09 22:12:13

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

#4 2024-03-10 00:28:15

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

#5 2024-03-10 00:29:20

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

#6 2024-03-10 08:51:22

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

#7 2024-03-10 10:42:38

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

#8 2024-03-10 10:52:33

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

#9 2024-03-10 11:48:54

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

#10 2024-03-10 12:00:30

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

#11 2024-03-10 12:16:31

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

#12 2024-03-10 12:46:19

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

#13 2024-03-10 14:10:31

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

#14 2024-03-10 15:13:15

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

#15 2024-03-10 17:54:38

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

#16 2024-03-10 18:55:26

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

#17 2024-03-10 19:31:11

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

#18 2024-03-10 19:55:07

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

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

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

#20 2024-03-10 20:07:30

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

#21 2024-03-10 20:11:43

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

#22 2024-03-10 20:20:58

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

#23 2024-03-10 20:26:42

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

#24 2024-03-10 20:37:57

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

#25 2024-03-10 20:41:38

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

Board footer