cubox i4-pro fails to boot fully at systemd update to 236

This forum is for supported devices using an ARMv7 Freescale SoC.

cubox i4-pro fails to boot fully at systemd update to 236

Postby mcloaked » Thu Dec 21, 2017 7:05 pm

This evening I did a pacman update on my cubox i4-pro - it has booted reliably for a very long time without issue. However this evening although the red light is displayed I can no longer ssh into the box (it's headless) after the updates that include systemd 236.0

Anybody have any ideas as to how to proceed to work around this - without the ability to ssh in the only option I have is to remove the ssd card and make changes on the card from another arch machine. However I don't know what to try to get it to boot and have the ssh server working?

On an odroid-c2 after the same updates it does boot but I see that the systemd-sysctl service has major problems:

Code: Select all
[root@odroid-c2 ~]# systemctl status systemd-sysctl
* systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2017-12-21 13:33:56 UTC; 5h 16min ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 203 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
 Main PID: 203 (code=exited, status=1/FAILURE)

Dec 21 13:33:56 odroid-c2 systemd-sysctl[203]: Couldn't write '1' to 'net/ipv4/conf/all/rp_filter': Input/output er
Dec 21 13:33:56 odroid-c2 systemd-sysctl[203]: Couldn't write '0' to 'net/ipv4/conf/all/accept_source_route': Input
Dec 21 13:33:56 odroid-c2 systemd-sysctl[203]: Couldn't write '1' to 'net/ipv4/conf/all/promote_secondaries': Input
Dec 21 13:33:56 odroid-c2 systemd-sysctl[203]: Couldn't write 'fq_codel' to 'net/core/default_qdisc': Input/output
Dec 21 13:33:56 odroid-c2 systemd-sysctl[203]: Couldn't write '1' to 'fs/protected_hardlinks': Input/output error
Dec 21 13:33:56 odroid-c2 systemd-sysctl[203]: Couldn't write '1' to 'fs/protected_symlinks': Input/output error
Dec 21 13:33:56 odroid-c2 systemd-sysctl[203]: Couldn't write '100000' to 'fs/inotify/max_user_watches': Input/outp
Dec 21 13:33:56 odroid-c2 systemd[1]: systemd-sysctl.service: Main process exited, code=exited, status=1/FAILURE
Dec 21 13:33:56 odroid-c2 systemd[1]: systemd-sysctl.service: Failed with result 'exit-code'.
Dec 21 13:33:56 odroid-c2 systemd[1]: Failed to start Apply Kernel Variables.
...skipping...
* systemd-sysctl.service - Apply Kernel Variables
   Loaded: loaded (/usr/lib/systemd/system/systemd-sysctl.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2017-12-21 13:33:56 UTC; 5h 16min ago
     Docs: man:systemd-sysctl.service(8)
           man:sysctl.d(5)
  Process: 203 ExecStart=/usr/lib/systemd/systemd-sysctl (code=exited, status=1/FAILURE)
 Main PID: 203 (code=exited, status=1/FAILURE)


So maybe this is at the heart of the problems on the cubox too?

Thanks

Edit: After pulling the power and letting the system cool for a period it did reboot but now the systemd-sysctl fails just as in my post at viewtopic.php?f=65&t=12365 but at least I have the cubox i4 pro booting with sshd running now.
mcloaked
 
Posts: 49
Joined: Thu Oct 16, 2014 4:16 pm

Re: cubox i4-pro fails to boot fully at systemd update to 23

Postby Bartoli » Sun Jan 07, 2018 10:51 pm

I can confirm that I have a similar problem on my cubox i4-pro.
Bartoli
 
Posts: 2
Joined: Mon Nov 23, 2015 10:17 pm


Return to Freescale

Who is online

Users browsing this forum: No registered users and 2 guests