Failed to boot after latest pacman -Syu
Hi all, I ran a `pacman -Syu` yesterday and when I boot, I'm greeted with: Failed to start Set Up Additional Binary Formats. The relevant portion of journalctl: Aug 14 21:43:53 beorn systemd[1]: Starting Set Up Additional Binary Formats... Aug 14 21:43:53 beorn systemd[1]: Update Boot Loader Random Seed was skipped because no trigger condition checks were met. Aug 14 21:43:53 beorn systemd[1]: Starting Create Volatile Files and Directories... Aug 14 21:43:53 beorn systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 429 (systemd-binfmt) Aug 14 21:43:53 beorn systemd[1]: sysinit.target: Found ordering cycle on systemd-vconsole-setup.service/start Aug 14 21:43:53 beorn systemd[1]: sysinit.target: Found dependency on sysinit.target/start Aug 14 21:43:53 beorn systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start Aug 14 21:43:53 beorn systemd[1]: Requested transaction contains an unfixable cyclic ordering dependency: Transaction order is cyclic. See system logs for details. Aug 14 21:43:53 beorn systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to queue mount startup job: Transaction order is cyclic. See system logs for details. Aug 14 21:43:53 beorn systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed with result 'resources'. Aug 14 21:43:53 beorn systemd-binfmt[429]: Failed to check if /proc/sys/fs/binfmt_misc is mounted: Host is down Aug 14 21:43:53 beorn systemd[1]: systemd-binfmt.service: Main process exited, code=exited, status=1/FAILURE Aug 14 21:43:53 beorn systemd[1]: systemd-binfmt.service: Failed with result 'exit-code'. Aug 14 21:43:53 beorn systemd[1]: Failed to start Set Up Additional Binary Formats. I tried `systemd-analyze verify sysinit.target proc-sys-fs-binfmt_misc.automount systemd-vconsole-setup.service` and it reported the same messages. systemd-vconsole-setup.service is the culprit. Since vconsole-setup isn't run, I can't login. Removing vconsole.conf had no effect. vconsole-setup is invoked by udevd, so I can't disable it (not that I want to). No other services appear to start after this failure (like lightdm). I'm stumped. Any thoughts on how to fix this? TIA, Dave
Have you changed the default units? Can you upload the output of systemctl cat sysinit.target proc-sys-fs-binfmt_misc.automount systemd-vconsole-setup.service and systemd-analyze dot sysinit.target proc-sys-fs-binfmt_misc.automount systemd-vconsole-setup.service If you are using chroot and systemctl and systemd-analyze complains "System has not been booted with systemd as init system", try systemd-nspawn from host. --- Paul M. Ärloch Debes praebere lingvam scriptvm vt hanc paginam inspicias. ------- Original Message ------- On Tuesday, August 15th, 2023 at 3:47 AM, David N Murray <dmurray@jsbsystems.com> wrote:
Hi all,
I ran a `pacman -Syu` yesterday and when I boot, I'm greeted with:
Failed to start Set Up Additional Binary Formats.
The relevant portion of journalctl:
Aug 14 21:43:53 beorn systemd[1]: Starting Set Up Additional Binary Formats... Aug 14 21:43:53 beorn systemd[1]: Update Boot Loader Random Seed was skipped because no trigger condition checks were met. Aug 14 21:43:53 beorn systemd[1]: Starting Create Volatile Files and Directories... Aug 14 21:43:53 beorn systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 429 (systemd-binfmt) Aug 14 21:43:53 beorn systemd[1]: sysinit.target: Found ordering cycle on systemd-vconsole-setup.service/start Aug 14 21:43:53 beorn systemd[1]: sysinit.target: Found dependency on sysinit.target/start Aug 14 21:43:53 beorn systemd[1]: sysinit.target: Unable to break cycle starting with sysinit.target/start Aug 14 21:43:53 beorn systemd[1]: Requested transaction contains an unfixable cyclic ordering dependency: Transaction order is cyclic. See system logs for details. Aug 14 21:43:53 beorn systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to queue mount startup job: Transaction order is cyclic. See system logs for details. Aug 14 21:43:53 beorn systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed with result 'resources'. Aug 14 21:43:53 beorn systemd-binfmt[429]: Failed to check if /proc/sys/fs/binfmt_misc is mounted: Host is down Aug 14 21:43:53 beorn systemd[1]: systemd-binfmt.service: Main process exited, code=exited, status=1/FAILURE Aug 14 21:43:53 beorn systemd[1]: systemd-binfmt.service: Failed with result 'exit-code'. Aug 14 21:43:53 beorn systemd[1]: Failed to start Set Up Additional Binary Formats.
I tried `systemd-analyze verify sysinit.target proc-sys-fs-binfmt_misc.automount systemd-vconsole-setup.service` and it reported the same messages. systemd-vconsole-setup.service is the culprit. Since vconsole-setup isn't run, I can't login. Removing vconsole.conf had no effect. vconsole-setup is invoked by udevd, so I can't disable it (not that I want to). No other services appear to start after this failure (like lightdm).
I'm stumped. Any thoughts on how to fix this?
TIA, Dave
On 8/15/23 00:21, memchr wrote:
Have you changed the default units? Can you upload the output of
systemctl cat sysinit.target proc-sys-fs-binfmt_misc.automount systemd-vconsole-setup.service
and
systemd-analyze dot sysinit.target proc-sys-fs-binfmt_misc.automount systemd-vconsole-setup.service
If you are using chroot and systemctl and systemd-analyze complains "System has not been booted with systemd as init system", try systemd-nspawn from host.
--- Paul M. Ärloch
Debes praebere lingvam scriptvm vt hanc paginam inspicias.
Thanks Paul. After I futzed around and learned how to invoke systemd-nspawn and collected the output, I re-reviewed defaults and found /etc/systemd/system/systemd-vconsole-setup.service.d/override.conf. The date of the file was when I built the system. I don't seem to have any notes about why I did that. I removed the file and the system booted fine. Thanks for your help. Dave
participants (2)
-
David N Murray
-
memchr