You are not logged in.
Units starts to fail (seeing with `systemctl status --failed`), mostly the systemd ones.
Crtl + Alt + Del will work to make the system reboot.
Then in boot it fail on many essential units and won't mount devices too.
Reverting back to 257.2 fixes it.
Last edited by brauliobo (2025-02-16 14:19:38)
Offline
Cannot reproduce. Please post the journal from an affected session.
Mod note: Moving to NC.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I've just run into the same issue going from 257.2 to 257.3.
There are no new journals after the new version was installed; the last bits I see are `systemd 257.3-1-arch running in system mode, some polkit spam, and the last line is `Queuing reload/restart jobs for marked units…`.
Systemd was beyond screwed to the point of not being able to enter a rescue OR emergency shell. Almost every service was failing to start.
Happy to provide whatever to debug this as I can reproduce.
Offline
@wormzy as @jupjohn mentioned, no journal logs are available immediately after the upgrade and in the boot not even `single` option works.
I have 2 other PCs and the upgrade worked there, so the issue has some specific trigger
Last edited by brauliobo (2025-02-15 01:51:46)
Offline
I also have encountered this issue with going to 257.3-1, services stopped working and system wouldn't boot after a restart.
Pastebin for my journal from upgrade until I rebooted, in case helpful: https://pastebin.com/LcBHhpJJ (note I upgraded using an ansible community script).
On latest 6.13.2-arch1-1
My original report of the issue including image of errors on boot and systemd packages I had to downgrade: https://bbs.archlinux.org/viewtopic.php?id=303429
Last edited by piperfw (2025-02-15 12:26:33)
Offline
Hey @brauliobo & @piperfw,
Could you guys attach as much information (what you've shared here & anything else you have) in the corresponding bug ticket here: https://gitlab.archlinux.org/archlinux/ … /issues/41
Trying to put it all in once place so we've got something to work with.
Cheers.
EDIT: if you don't have an account and want me to be the messenger, dump your comment in here and ask me to forward it on.
Last edited by jupjohn (2025-02-16 02:03:29)
Offline
Updated an Arch derivative including systemd and the same problem occured, loads of system files failed to load make system unusable. On inspection some files had disappeared altogether. I simply reinstalled as it had been on the PC for a few years. I've just updated Arch itself and no problems at all. (Same PC)
Offline
Do all with this problem use glibc-eac-bin ?
If so, that package replaces the glibc system library which is a Very Bad Idea and can cause all kind of issues.
boot to a live environment , install repo glibc and reboot .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Mistery solved. I've put glibc in the `IgnorePkg` section of `pacman.conf`, as glibc 2.41 is breaking a cuda program compilation.
By removing it from IgnorePkg and upgrading it first, systemd upgrade will work.
systemd 257.3 package must depend on glibc >= 2.41
Last edited by brauliobo (2025-02-16 14:24:06)
Offline
@jupjohn I can't login into Arch's gitlab, please comment there
Offline
A whole lot of things will depend on glibc updates. Just about everything compiled against the new version, in fact. Partial updates are bad, and that's probably the worst partial update possible.
Offline
Mistery solved. I've put glibc in the `IgnorePkg` section of `pacman.conf`, as glibc 2.41 is breaking a cuda program compilation.
What CUDA program is glibc 2.41 breaking. Was that not fixed by https://gitlab.archlinux.org/archlinux/ … c241.patch?
Last edited by loqs (2025-02-16 15:01:54)
Offline