[SOLVED][ODROID c1] System unbootable after systemd update

[slydder]

Is anyone else facing issues booting up Odroid c1 after latest systemd update?

Logs:
$this->bbcode_second_pass_code('', '
Packages (3) systemd-245-3 systemd-libs-245-3 systemd-sysvcompat-245-3

Total Download Size: 5.22 MiB
Total Installed Size: 22.79 MiB
Net Upgrade Size: 1.55 MiB

:: Proceed with installation? [Y/n]
:: Retrieving packages...
systemd-libs-245-3-armv7h 392.7 KiB 1402 KiB/s 00:00 [#############################################################] 100%
systemd-245-3-armv7h 4.8 MiB 1368 KiB/s 00:04 [#############################################################] 100%
systemd-sysvcompat-245-3-armv7h 8.0 KiB 0.00 B/s 00:00 [#############################################################] 100%
(3/3) checking keys in keyring [#############################################################] 100%
(3/3) checking package integrity [#############################################################] 100%
(3/3) loading package files [#############################################################] 100%
(3/3) checking for file conflicts [#############################################################] 100%
(3/3) checking available disk space [#############################################################] 100%
:: Processing package changes...
(1/3) upgrading systemd-libs [#############################################################] 100%
(2/3) upgrading systemd [#############################################################] 100%
(3/3) upgrading systemd-sysvcompat [#############################################################] 100%
:: Running post-transaction hooks...
( 1/10) Creating system user accounts...
( 2/10) Updating journal message catalog...
( 3/10) Reloading system manager configuration...
( 4/10) Updating udev hardware database...
( 5/10) Applying kernel sysctl settings...
( 6/10) Creating temporary files...
( 7/10) Reloading device manager configuration...
( 8/10) Arming ConditionNeedsUpdate...
( 9/10) Updating linux initcpios...
(10/10) Reloading system bus configuration...
Job for dbus.service failed.
See "systemctl status dbus.service" and "journalctl -xe" for details.
error: command failed to execute correctly
')

Output of journalct -xe:
$this->bbcode_second_pass_code('', '
Mar 18 15:33:21 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:21 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:22 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:22 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:22 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:24 user_x systemd[1]: Reexecuting.
Mar 18 15:33:24 user_x systemd[1]: systemd 245-3-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +AC>
Mar 18 15:33:24 user_x systemd[1]: Detected architecture arm.
Mar 18 15:33:25 user_x systemd[1]: systemd-update-done.service: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
Mar 18 15:33:25 user_x systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
Mar 18 15:33:28 user_x systemd[1]: Reloading.
Mar 18 15:33:35 user_x systemd-sysctl[662]: Not setting net/ipv4/conf/all/rp_filter (explicit setting exists).
Mar 18 15:33:35 user_x systemd-sysctl[662]: Not setting net/ipv4/conf/default/rp_filter (explicit setting exists).
Mar 18 15:33:35 user_x systemd-sysctl[662]: Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists).
Mar 18 15:33:35 user_x systemd-sysctl[662]: Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists).
Mar 18 15:33:35 user_x systemd-sysctl[662]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Mar 18 15:33:35 user_x systemd-sysctl[662]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).
Mar 18 15:33:35 user_x systemd-sysctl[662]: Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory
Mar 18 15:33:35 user_x systemd-sysctl[662]: Couldn't write '1' to 'fs/protected_regular', ignoring: No such file or directory
Mar 18 15:33:35 user_x systemd-sysctl[662]: Couldn't write '1' to 'fs/protected_fifos', ignoring: No such file or directory
Mar 18 15:33:35 user_x systemd[1]: Reloading D-Bus System Message Bus.
-- Subject: A reload job for unit dbus.service has begun execution
-- Subject: A reload job for unit dbus.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A reload job for unit dbus.service has begun execution.
--
-- The job identifier is 502.
Mar 18 15:33:35 user_x systemd[673]: dbus.service: Failed to apply ambient capabilities (before UID change): Invalid argument
Mar 18 15:33:35 user_x systemd[673]: dbus.service: Failed at step CAPABILITIES spawning /usr/bin/dbus-send: Invalid argument
-- Subject: Process /usr/bin/dbus-send could not be executed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/bin/dbus-send could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Mar 18 15:33:35 user_x systemd[1]: dbus.service: Control process exited, code=exited, status=218/CAPABILITIES
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- An ExecReload= process belonging to unit dbus.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 218.
Mar 18 15:33:35 user_x systemd[1]: Reload failed for D-Bus System Message Bus.
-- Subject: A reload job for unit dbus.service has finished
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A reload job for unit dbus.service has finished.
--
-- The job identifier is 502 and the job result is failed.
Mar 18 15:35:00 user_x sudo[563]: pam_unix(sudo:session): session closed for user root
Mar 18 15:36:58 user_x systemd[1]: Starting Cleanup of Temporary Directories...
-- Subject: A start job for unit systemd-tmpfiles-clean.service has begun execution
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit systemd-tmpfiles-clean.service has begun execution.
--
-- The job identifier is 503.
Mar 18 15:36:58 user_x systemd[682]: systemd-tmpfiles-clean.service: Failed to apply ambient capabilities (before UID change): Invalid argument
Mar 18 15:36:58 user_x systemd[682]: systemd-tmpfiles-clean.service: Failed at step CAPABILITIES spawning /usr/bin/systemd-tmpfiles: Invalid argument
-- Subject: Process /usr/bin/systemd-tmpfiles could not be executed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The process /usr/bin/systemd-tmpfiles could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Mar 18 15:36:58 user_x systemd[1]: systemd-tmpfiles-clean.service: Main process exited, code=exited, status=218/CAPABILITIES
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- An ExecStart= process belonging to unit systemd-tmpfiles-clean.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 218.
Mar 18 15:36:58 user_x systemd[1]: systemd-tmpfiles-clean.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The unit systemd-tmpfiles-clean.service has entered the 'failed' state with result 'exit-code'.
Mar 18 15:36:58 user_x systemd[1]: Failed to start Cleanup of Temporary Directories.
-- Subject: A start job for unit systemd-tmpfiles-clean.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- A start job for unit systemd-tmpfiles-clean.service has finished with a failure.
--
-- The job identifier is 503 and the job result is failed.
')

Status of DBUS.service
$this->bbcode_second_pass_code('', '
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
Active: active (running) since Wed 2020-03-18 15:22:08 EET; 17min ago
TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
Process: 673 ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig (code=exited, stat>
Main PID: 231 (dbus-daemon)
Memory: 1.6M
CGroup: /system.slice/dbus.service
└─231 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

Mar 18 15:33:21 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:21 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:22 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:22 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:22 user_x dbus-daemon[231]: [system] Reloaded configuration
Mar 18 15:33:35 user_x systemd[1]: Reloading D-Bus System Message Bus.
Mar 18 15:33:35 user_x systemd[673]: dbus.service: Failed to apply ambient capabilities (before UID change): Invalid argument
Mar 18 15:33:35 user_x systemd[673]: dbus.service: Failed at step CAPABILITIES spawning /usr/bin/dbus-send: Invalid argument
Mar 18 15:33:35 user_x systemd[1]: dbus.service: Control process exited, code=exited, status=218/CAPABILITIES
Mar 18 15:33:35 user_x systemd[1]: Reload failed for D-Bus System Message Bus.
')

After a reboot the system hangs somewhere in the boot process. Unfortunately I don't have serial console to see what is happening

[slydder]

Similar issue: https://github.com/systemd/systemd/issues/15062

[slydder]

Systemd 245.4 fixed the issue