Systemd[1]: Failed to allocate manager object

General system Kernel, boot, graphics & hardware
1

After upgrading my system as normal, I rebooted my system as recommended by EOS, because a core package got upgraded as well.

Upon booting, I am met with this error:

Welcome to EndeavourOS dracut-059 (Initramfs)!

[    4.094166] systemd[1]: Failed to allocate manager object: No such file or directory
[!!!!!!] Failed to allocate manager object.
[    4.094551] systemd[1]: Freezing execution.

I also tried to boot with the fallback option, but it ultimately ends up doing the same thing. If there are any logs or anything else that might help determine the problem, please tell me.

2

I am in the same situation. Looking for answers.

3

Same here. I am trying some things like balancing and scrubbing my BTRFS and reinstalling kernels but I haven’t tried to reboot again yet.

4

Ok so I checked and found that systemd had a few things update with this last update.

I updated my Lenovo Legion Laptop and it rebooted with no issues.
I’m on ext4
Openbox
nvidia gpu

look at the boot log and see what errors are showing and post.

journalctl -b 0

5

How would I go about doing this, though? grub doesn’t have journalctl, and booting the LiveISO and trying that isn’t actually useful: it only shows errors coming from the LiveISO - and the computer doesn’t actually boot, this error being the very reason.

I thought of trying to rebuild initramfs-linux.img because the problem seems like it is coming from there. However, I am unsure of whether I should do it or not. I don’t want things to break even further.

6

arch-chroot from a live usb.

1 Like
7

Okay.

Assuming I did it correctly, this is the resulting output:

[root@EndeavourOS /]# journalctl -b 0
-- No entries --

I also tried journalctl -b -p err, just to be safe:

[root@EndeavourOS /]# journalctl -b -p err
-- No entries --

There seems to be nothing.

8

Hello people! I solved the problem!

Turns out I actually did need to rebuild initramfs-linux.img, just as I thought. For anyone else having this problem, just follow the post I linked earlier:

1 Like
9

I had this problem too and tried rebuilding the initramfs-linux.img by reinstalling the kernel from arch-chroot. This did not work so I downgraded systemd.

[2023-11-18T06:52:04+0000] [ALPM] downgraded systemd-libs (255rc2-2 -> 254.6-2)
[2023-11-18T06:52:13+0000] [ALPM] downgraded systemd (255rc2-2 -> 254.6-2)
[2023-11-18T06:52:13+0000] [ALPM] downgraded systemd-resolvconf (255rc2-2 -> 254.6-2)
[2023-11-18T06:52:13+0000] [ALPM] downgraded systemd-sysvcompat (255rc2-2 -> 254.6-2)
[2023-11-18T06:52:14+0000] [ALPM] transaction completed
[2023-11-18T06:52:14+0000] [ALPM] running '20-systemd-sysusers.hook'...
[2023-11-18T06:52:14+0000] [ALPM] running '30-systemd-catalog.hook'...
[2023-11-18T06:52:14+0000] [ALPM] running '30-systemd-daemon-reload.hook'...
[2023-11-18T06:52:14+0000] [ALPM-SCRIPTLET]   Skipped: Running in chroot.
[2023-11-18T06:52:14+0000] [ALPM] running '30-systemd-hwdb.hook'...
[2023-11-18T06:52:16+0000] [ALPM] running '30-systemd-sysctl.hook'...
[2023-11-18T06:52:16+0000] [ALPM-SCRIPTLET]   Skipped: Running in chroot.
[2023-11-18T06:52:16+0000] [ALPM] running '30-systemd-tmpfiles.hook'...
[2023-11-18T06:52:16+0000] [ALPM] running '30-systemd-udev-reload.hook'...
[2023-11-18T06:52:16+0000] [ALPM-SCRIPTLET]   Skipped: Running in chroot.
[2023-11-18T06:52:16+0000] [ALPM] running '30-systemd-update.hook'...
[2023-11-18T06:52:16+0000] [ALPM] running '90-dracut-install.hook'...
[2023-11-18T06:52:16+0000] [ALPM-SCRIPTLET] :: Building initramfs for linux-lts (6.1.62-1-lts)
[2023-11-18T06:52:46+0000] [ALPM-SCRIPTLET] :: Building fallback initramfs for linux-lts (6.1.62-1-lts)
[2023-11-18T06:52:48+0000] [ALPM-SCRIPTLET] dracut: dracut module 'nbd' depends on 'network', which can't be installed
[2023-11-18T06:52:48+0000] [ALPM-SCRIPTLET] dracut: dracut module 'nfs' depends on 'network', which can't be installed
[2023-11-18T06:52:48+0000] [ALPM-SCRIPTLET] dracut: dracut module 'nvmf' depends on 'network', which can't be installed
[2023-11-18T06:53:20+0000] [ALPM-SCRIPTLET] :: Building initramfs for linux (6.6.1-arch1-1)
[2023-11-18T06:53:39+0000] [ALPM-SCRIPTLET] :: Building fallback initramfs for linux (6.6.1-arch1-1)
[2023-11-18T06:53:40+0000] [ALPM-SCRIPTLET] dracut: dracut module 'nbd' depends on 'network', which can't be installed
[2023-11-18T06:53:40+0000] [ALPM-SCRIPTLET] dracut: dracut module 'nfs' depends on 'network', which can't be installed
[2023-11-18T06:53:40+0000] [ALPM-SCRIPTLET] dracut: dracut module 'nvmf' depends on 'network', which can't be installed
[2023-11-18T06:54:13+0000] [ALPM] running 'dbus-reload.hook'...
[2023-11-18T06:54:13+0000] [ALPM-SCRIPTLET]   Skipped: Running in chroot.

I tried updating systemd to 255rc2-2 and the problem reoccurred so it is this version of systemd that causes the problem for me.

Note: my system uses dracut.

Note 2: 19 November 2023 - My issue has now been resolved by upgrading dracut (059-3 → 059-4) which is now available in extra-testing.

10

I’m wondering where did you get the 255 version of systemd, I’m running pure arch and the newest version available to me is 254.6-2

11

It’s in core-testing.
They may have updated to the testing version.
I have too but no issue on my end.

1 Like
12

Ah ok, I see.

13

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.