[SOLVED] Failed to allocate manager object: No such file or directory

liaminventions · 2023-12-09 04:22:27

I recently ran a system update (i forgot what had to update, but systemd might have updated, though i am not sure.), hibernated about an hour later, and tried to boot again.
I was then greeted with the following after attempting to boot:

[ 0.580657 ] systemd[1]: Failed to allocate manager object: No such file or di
rectory
[!!!!!!] Failed to allocate manager object.
[ 0.580684 ] systemd[1]: Freezing execution.

here's an image of what it looks like:
refrence image

i don't really know what this means, but systemd won't init anymore.

i then booted into the installer usb and ran fsck on my ssd, the home partition seems to be intact.

i also chrooted in to double check that the drive still works, and it does.

just in case there was a partial update or something, i tried pacman -Syu in the chroot and it said there was nothing to do

anyone have any idea how i could get my computer working again? thanks for your time.

Last edited by liaminventions (2023-12-09 23:49:04)

liaminventions · 2023-12-09 15:33:01

it seems that a similar issue is looked at here: https://forum.endeavouros.com/t/systemd … ject/47932
though it was solved by rebuilding the initrd, that didn't work for me. i also updated grub.

i also tried switching back to linux from linux-zen, no difference (i still can't boot)

liaminventions · 2023-12-09 16:02:17

UPDATE: i just downgraded the systemd package to version 254.6-2, and now I can boot again!
(the version before was 255-1)

i think that i should keep this thread open though because this is an issue with the newest version of systemd

i accedentally just downgraded the systemd package though, and not all of its deps, so there are a lot of issues. i'll see what i can do to downgrade everything else and get my system working again.

Last edited by liaminventions (2023-12-09 16:02:34)

just4arch · 2023-12-09 16:03:46

I had a similar issue.
With 255 installed, try booting with debug kernel parameter and link the screenshot.

Do you get output from the following command (255 as well)?

lsinitcpio /boot/initramfs-linux.img | grep systemd-executor

(substitute for your kernel and EFI partition mount)

Last edited by just4arch (2023-12-09 16:07:11)

liaminventions · 2023-12-09 16:44:00

oh no, now my system is completely broken, fsck said there was a lot to fix, and now i'm scared to boot again. mkinitcpio won't generate an image correctly due to a ton of errors and the journal is complete spam

journalctl -r

mkinitcpio -P

i made the mistake of booting with just that systemd package downgraded... i think i completely broke everything now

i really should not have booted with 254-2...

i updated systemd back to 255-1 but i can't mkinitcpio anymore

do i have to reinstall my entire os at this point?

Last edited by liaminventions (2023-12-09 17:15:10)

liaminventions · 2023-12-09 17:12:04

just4arch wrote:

I had a similar issue.
With 255 installed, try booting with debug kernel parameter and link the screenshot.

i was able to mkinitcpio after removing linux and switching back to linux zen.

boot with debug (it looks pretty bad)

just4arch wrote:

Do you get output from the following command (255 as well)?
lsinitcpio /boot/initramfs-linux.img | grep systemd-executor
(substitute for your kernel and EFI partition mount)

i don't get any output for it

Last edited by liaminventions (2023-12-09 17:16:14)

seth · 2023-12-09 17:38:27

Did you try to explicitly regenerate the initramfs?

liaminventions · 2023-12-09 17:49:22

seth wrote:

Did you try to explicitly regenerate the initramfs?

yes, when i upgraded systemd back to 255-1 i had to

liaminventions · 2023-12-09 18:06:20

there are so many system files missing after the half-broken boot with systemd 254.6-2, i think the only option to continue from here is to back up and reinstall arch…

is there anyway i could fix the system files without reinstalling the OS?

if not its ok, reinstalling shouldn’t be that bad

just4arch · 2023-12-09 19:35:31

liaminventions wrote:

oh no, now my system is completely broken, fsck said there was a lot to fix, and now i'm scared to boot again. mkinitcpio won't generate an image correctly due to a ton of errors and the journal is complete spam

welp, same error that I had, but if you filesystem (or disk?) is mangled, you want to fix that first.
Just downgrading systemd worked for me, so make sure your hardware is ok (smartctl).

If your disk and filesystem are fine, you can assess the damage:

LC_ALL=C pacman -Qkk 2>&1 | grep -v -e ', 0 altered files'

As for the cause of this error, make sure you aren't overriding the systemd mkinitcpio hook.

liaminventions · 2023-12-09 20:05:04

just4arch wrote:

liaminventions wrote:
oh no, now my system is completely broken, fsck said there was a lot to fix, and now i'm scared to boot again. mkinitcpio won't generate an image correctly due to a ton of errors and the journal is complete spam
welp, same error that I had, but if you filesystem (or disk?) is mangled, you want to fix that first.
Just downgrading systemd worked for me, so make sure your hardware is ok (smartctl).
If your disk and filesystem are fine, you can assess the damage:
LC_ALL=C pacman -Qkk 2>&1 | grep -v -e ', 0 altered files'

that returned a lot of output… it didn’t seem to change the debug screen at all though

output of that command

just4arch wrote:

As for the cause of this error, make sure you aren't overriding the systemd mkinitcpio hook.

I don’t think so, if I was there would be a file in mkinitcpio.d or mkinitcpio.conf.d that says something about that, and there is not.

seth · 2023-12-09 20:50:30

Please don't copy & paste out of the pager, the file your posted has a bunch of artifacts.
Most of that is some AUR packages being fucked around with, but not system-critical.

backup file: mkinitcpio: /etc/mkinitcpio.conf (MD5 checksum mismatch)

Post that file.

mkinitcpio won't generate an image correctly due to a ton of errors

and the output of that

mkinitcpio … 2>&1 | tee /tmp/mkinitcpio.log

just4arch · 2023-12-09 21:10:58

liaminventions wrote:

mkinitcpio -P

But maybe include a version with mkinitcpio -v -P, too.
I'm probably barking up the wrong tree, but there's definitely a file missing in your initramfs (systemd-executor).

seth · 2023-12-09 22:02:35

==> ERROR: file not found: '/lib/modules/6.6.4-arch1-1/kernel/security/keys/encrypted-keys/encrypted-keys.ko.zst'
==> ERROR: file not found: '/lib/modules/6.6.4-arch1-1/kernel/net/sunrpc/sunrpc.ko.zst'
==> ERROR: file not found: '/lib/modules/6.6.4-arch1-1/kernel/net/sunrpc/auth_gss/auth_rpcgss.ko.zst'
==> ERROR: file not found: '/lib/modules/6.6.4-arch1-1/kernel/net/tls/tls.ko.zst'

The kernel installation certainly was corrupt (this is not reflected in the posted package integrity check, might be because of copypasta) but only affected the initramfs-linux-fallback.img and isn't "a ton of errors" either.

liaminventions · 2023-12-09 22:13:15

seth wrote:

backup file: mkinitcpio: /etc/mkinitcpio.conf (MD5 checksum mismatch)

Post that file.

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

seth wrote:

mkinitcpio … 2>&1 | tee /tmp/mkinitcpio.log

mkinitcpio -P | tee /tmp/mkinitcpio.log | curl -F ‘file=@-‘ 0x0.st

just4arch wrote:

But maybe include a version with mkinitcpio -v -P, too.
I'm probably barking up the wrong tree, but there's definitely a file missing in your initramfs (systemd-executor).

something odd happened with that one
mkinitcpio -v -P | tee /tmp/mkinitcpio.log | curl -F ‘file=@-‘ 0x0.st

sorry for the late reply

seth · 2023-12-09 22:16:50

Timeout, you're also not capturing stderr.
The idea was more like

mkinitcpio -vP 2>&1 | tee /tmp/mkinitcpio.log
cat /tmp/mkinitcpio.log | curl -F ‘file=@-‘ 0x0.st

liaminventions · 2023-12-09 22:21:27

seth wrote:

Timeout, you're also not capturing stderr.
The idea was more like
mkinitcpio -vP 2>&1 | tee /tmp/mkinitcpio.log
cat /tmp/mkinitcpio.log | curl -F ‘file=@-‘ 0x0.st

here it is

seth · 2023-12-09 22:30:05

This is systemd-255, but the executor isn't added.
What if you downgrade systemd and systemd-libs again?

just4arch · 2023-12-09 22:33:41

liaminventions wrote:

just4arch wrote:
As for the cause of this error, make sure you aren't overriding the systemd mkinitcpio hook.
I don’t think so, if I was there would be a file in mkinitcpio.d or mkinitcpio.conf.d that says something about that, and there is not.

-> Running build hook: [/etc/initcpio/install/systemd]

Nailed it!
Remove, try again...

liaminventions · 2023-12-09 22:43:57

here is an updated version of the …pacman -Qkk… command output (/etc/pacman.conf broke now, it’s empty…)

seth wrote:

This is systemd-255, but the executor isn't added.
What if you downgrade systemd and systemd-libs again?

i would have to fix pacman.conf, which i have to anyway..

just4arch wrote:

Nailed it!
Remove, try again.

that worked! i can boot now

so that file must’ve been overriding the /usr/lib/… version? weird… i’m not sure where the override came from

well now i still have to fix all my global config files, i’ll keep this thread updated..

just4arch · 2023-12-09 23:02:21

liaminventions wrote:

that worked! i can boot now

yay!

liaminventions wrote:

so that file must’ve been overriding the /usr/lib/… version?

Exactly, the new version includes a few incompatible changes, eg. the systemd-executor.

liaminventions wrote:

weird… i’m not sure where the override came from

Best guess, enabling root - diff your version if you kept it with the packaged version.

liaminventions wrote:

well now i still have to fix all my global config files, i’ll keep this thread updated..

As your problem is solved, I'd suggest to mark this thread as solved (by prepending [solved] to the titel of your first post) and start a new one for the cleanup, if you need further advice.

And you still might want to take a good look at smartctl and maybe post a full journal, there might be an issue with your drive?

liaminventions · 2023-12-09 23:48:01

just4arch wrote:

As your problem is solved, I'd suggest to mark this thread as solved (by prepending [solved] to the titel of your first post) and start a new one for the cleanup, if you need further advice.

ok, i'll do that.

trying to fix it myself first by re-writing the missing global config files now...

just4arch wrote:

And you still might want to take a good look at smartctl and maybe post a full journal, there might be an issue with your drive?

here's the output of sudo smartctl -x /dev/nvme0n1p2

here's the most recent journal of the current session (journalctl -b)

note: i did hibernate in this session, so any errors/info about that would be in there as well.

there is an issue that i do know about; when i suspend/hibernate, there is a non-fatal (i think) error that says: "kernel: nvme 10000:e1:00.0: PCI INT A: no GSI"
i've tried to get rid of this error before, it seems to be just an issue with the fact that i'm using an hp 15-dy2024nr laptop...

Last edited by liaminventions (2023-12-10 00:37:48)

liaminventions · 2023-12-10 03:28:55

update: I fixed all the system-wide config files!

it seems that the contents of some of the config files were swapped. (eg. the contents of /etc/systemd/resolv.conf were copied to /etc/systemd/sleep.conf, etc..)

i used that "LC_ALL=C pacman -Qkk 2>&1 | grep -v -e ', 0 altered files'" command to help find the files that were changed, and then found the original version from searching in the systemd github repo and in the trees that are in the archlinux/svntogit-packages github repo

btw, thanks everyone soo much for your help!!

Last edited by liaminventions (2023-12-12 13:36:07)

Arch Linux

#1 2023-12-09 04:22:27

[SOLVED] Failed to allocate manager object: No such file or directory

#2 2023-12-09 15:33:01

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#3 2023-12-09 16:02:17

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#4 2023-12-09 16:03:46

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#5 2023-12-09 16:44:00

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#6 2023-12-09 17:12:04

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#7 2023-12-09 17:38:27

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#8 2023-12-09 17:49:22

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#9 2023-12-09 18:06:20

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#10 2023-12-09 19:35:31

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#11 2023-12-09 20:05:04

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#12 2023-12-09 20:50:30

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#13 2023-12-09 21:10:58

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#14 2023-12-09 22:02:35

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#15 2023-12-09 22:13:15

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#16 2023-12-09 22:16:50

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#17 2023-12-09 22:21:27

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#18 2023-12-09 22:30:05

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#19 2023-12-09 22:33:41

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#20 2023-12-09 22:43:57

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#21 2023-12-09 23:02:21

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#22 2023-12-09 23:48:01

Re: [SOLVED] Failed to allocate manager object: No such file or directory

#23 2023-12-10 03:28:55

Re: [SOLVED] Failed to allocate manager object: No such file or directory

Board footer