No network services after Arch install

[sambul13]

Hi guys,

I just fresh installed to run on my DockStar the latest ArchLinux ARM 4.3 on a 1st partition of a multipartitioned newly formatted USB Thumb following standard install procedure on this site, and after reboot I'm not getting network in Linux. Added IP and Mac in Uboot envs via Serial Console, but it didn't fix the issue. Didn't change anything in OS, expecting it to run OK out of the box. Any suggestions, what needs to be looked at or changed? Same Uboot starts up ArchLinux ARM 3.6 from another thumb with network enabled.

$this->bbcode_second_pass_code('', '
Linux version 4.3.3-1-ARCH (builduser@leming) (gcc version 5.3.0 (GCC) ) #1 PREEMPT Thu Dec 17 22:16:31 MST 2015

------------------------------------------------------------------------------------------
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
[ OK ] Started Permit User Sessions.
[FAILED] Failed to start Network Service.
See 'systemctl status systemd-networkd.service' for details.
[ OK ] Found device /dev/ttyS0.
[ OK ] Stopped Network Service.
Starting Network Service...
[ OK ] Stopped Login Service.
Starting Login Service...
[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Reached target Login Prompts.
[FAILED] Failed to start Network Service.
See 'systemctl status systemd-networkd.service' for details.
[ OK ] Started Login Service.
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See 'systemctl status systemd-networkd.service' for details.
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See 'systemctl status systemd-networkd.service' for details.
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See 'systemctl status systemd-networkd.service' for details.
[ OK ] Stopped Network Service.
[FAILED] Failed to start Network Service.
See 'systemctl status systemd-networkd.service' for details.
[ OK ] Reached target Network.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.
[ OK ] Stopped Network Name Resolution.
[FAILED] Failed to start Network Name Resolution.
See 'systemctl status systemd-resolved.service' for details.

----------------------------------------------------------------------------
[root@alarm mkinitcpio.d]# dmesg

[29.579634] MV-CESA:Could not register sha1 driver
[29.590677] MV-CESA:Could not register hmac-sha1 driver

')

EDIT:

Was able to start network manually from Serial Console with below commands, but no auto start at boot. Network related config files seem to be OK based on Network Configuration Wiki. Update OS with pacman -Syu, but still the same issue.

$this->bbcode_second_pass_code('', 'ip link set eth0 up
dhcpcd eth0')

[WarheadsSE]

MV-CESA is a crypto accelerator, and the "MAC" here is a Message Authentication Code, not a Media Access Control

Please do as the message says: See 'systemctl status systemd-networkd.service' for details.

[sambul13]

Thanks for the prompt reply.

In Serial output in /etc/systemd/network/eth0.network :

$this->bbcode_second_pass_code('', '[Match]
Name=eth0

[Network]
DHCP=yes')

$this->bbcode_second_pass_code('', '[root@alarm ~]# systemctl status systemd-networkd.service -l
* systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit) since Fri 2015-11-27 18:07:52 UTC; 2min 8s ago
Docs: man:systemd-networkd.service(8)
Process: 214 ExecStart=/usr/lib/systemd/systemd-networkd (code=exited, status=1/FAILURE)
Main PID: 214 (code=exited, status=1/FAILURE)

Nov 27 18:07:52 alarm systemd[1]: systemd-networkd.service: Unit entered failed state.
Nov 27 18:07:52 alarm systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Nov 27 18:07:52 alarm systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Nov 27 18:07:52 alarm systemd[1]: Stopped Network Service.
Nov 27 18:07:52 alarm systemd[1]: systemd-networkd.service: Start request repeated too quickly.
Nov 27 18:07:52 alarm systemd[1]: Failed to start Network Service.
Nov 27 18:07:52 alarm systemd[1]: systemd-networkd.service: Unit entered failed state.
Nov 27 18:07:52 alarm systemd[1]: systemd-networkd.service: Failed with result 'start-limit'.
[root@alarm ~]#
')

[WarheadsSE]

The service would not outright die because it would not die simply because of the .network file.

We're going to need to root out the real cause.

[sambul13]

May be the log below will help. See also similar earlier fixed issue systemd.timesyncd fails on boot. Current Arch release for PC doesn't have network problems now. So every DockStar upon installing current Arch ARM 4.3 will become toast requiring Serial connection, and many folks wouldn't have previous working Arch version at hand. With current default Uboot envs it doesn't boot to original Pogo OS on Flash either, if no USB drives are attached.

$this->bbcode_second_pass_code('', '[root@alarm ~]# journalctl -b
Jan 01 00:00:18 alarm systemd[1]: Starting Network Time Synchronization...dev...
Jan 01 00:00:18 alarm systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Jan 01 00:00:18 alarm systemd-timesyncd[164]: System clock time unset or jumped backwards, restoring from recorded timestamp: Fri 2015-11-27 18:07:49 UTC 01 00:00:08 alarm systemd[1]: Reached target Local File Systems (Pre).
Nov 27 18:07:49 alarm systemd[1]: Time has been changed
Nov 27 18:07:49 alarm systemd[1]: Started Update UTMP about System Boot/Shutdown.
Nov 27 18:07:49 alarm systemd-timesyncd[164]: Failed to allocate manager: Permission denied
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILUREsuch file or directory
Nov 27 18:07:49 alarm systemd[1]: Failed to start Network Time Synchronization.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Unit entered failed state.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Nov 27 18:07:49 alarm systemd[1]: Stopped Network Time Synchronization.
Nov 27 18:07:49 alarm systemd[1]: Starting Network Time Synchronization...
Nov 27 18:07:49 alarm systemd-timesyncd[170]: Failed to allocate manager: Permission denied
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 18:07:49 alarm systemd[1]: Failed to start Network Time Synchronization.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Unit entered failed state.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Nov 27 18:07:49 alarm systemd[1]: Stopped Network Time Synchronization.
Nov 27 18:07:49 alarm systemd[1]: Starting Network Time Synchronization...
Nov 27 18:07:49 alarm systemd-timesyncd[174]: Failed to allocate manager: Permission denied
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 18:07:49 alarm systemd[1]: Failed to start Network Time Synchronization.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Unit entered failed state.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Nov 27 18:07:49 alarm systemd[1]: Stopped Network Time Synchronization.
Nov 27 18:07:49 alarm kernel: saa7115 0-0025: gm7113c found @ 0x4a (stk1160)
Nov 27 18:07:49 alarm systemd[1]: Starting Network Time Synchronization...
Nov 27 18:07:49 alarm systemd-timesyncd[178]: Failed to allocate manager: Permission denied
, code=exited, status=1/FAILURE
Nov 27 18:07:49 alarm systemd[1]: Failed to start Network Time Synchronization.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Unit entered failed state.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Nov 27 18:07:49 alarm systemd[1]: Stopped Network Time Synchronization.
Nov 27 18:07:49 alarm systemd[1]: Starting Network Time Synchronization...
Nov 27 18:07:49 alarm systemd-timesyncd[182]: Failed to allocate manager: Permission denied
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 18:07:49 alarm systemd[1]: Failed to start Network Time Synchronization.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Unit entered failed state.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Service has no hold-off time, scheduling restart.
Nov 27 18:07:49 alarm systemd[1]: Stopped Network Time Synchronization.
ted too quickly.
Nov 27 18:07:49 alarm systemd[1]: Failed to start Network Time Synchronization.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Unit entered failed state.
Nov 27 18:07:49 alarm systemd[1]: systemd-timesyncd.service: Failed with result 'start-limit'.
Nov 27 18:07:49 alarm systemd[1]: Reached target System Time Synchronized.
Nov 27 18:07:49 alarm systemd[1]: Reached target System Initialization.
Nov 27 18:07:49 alarm systemd[1]: Started Daily rotation of log files.
Nov 27 18:07:49 alarm systemd[1]: Started Daily Cleanup of Temporary Directories.
Nov 27 18:07:49 alarm systemd[1]: Started Daily man-db cache update.
Nov 27 18:07:50 alarm systemd[1]: Started Daily verification of password and group files.
Nov 27 18:07:50 alarm systemd[1]: Reached target Timers.
Nov 27 18:07:50 alarm systemd[1]: Listening on D-Bus System Message Bus Socket.
Nov 27 18:07:50 alarm systemd[1]: Reached target Sockets.
Nov 27 18:07:50 alarm systemd[1]: Reached target Basic System.
Nov 27 18:07:50 alarm systemd[1]: Starting SSH Key Generation...
Nov 27 18:07:50 alarm systemd[1]: Starting Permit User Sessions...
Nov 27 18:07:50 alarm systemd[1]: Started Entropy Harvesting Daemon.
Nov 27 18:07:50 alarm systemd[1]: Starting Login Service...
Nov 27 18:07:50 alarm systemd[1]: Started D-Bus System Message Bus.
Nov 27 18:07:50 alarm systemd-logind[190]: Failed to enable subscription: The name org.freedesktop.systemd1 was not provided by any .service files
Nov 27 18:07:50 alarm systemd-logind[190]: Failed to fully start up daemon: No route to host
Nov 27 18:07:50 alarm systemd[1]: Starting Network Service...
Nov 27 18:07:50 alarm systemd[1]: Started SSH Key Generation.
Nov 27 18:07:50 alarm systemd[1]: Started Permit User Sessions.
Nov 27 18:07:50 alarm systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 18:07:50 alarm systemd[1]: Failed to start Login Service.
Nov 27 18:07:50 alarm systemd-networkd[195]: Could not connect to bus: Permission denied
Nov 27 18:07:50 alarm systemd[1]: systemd-logind.service: Unit entered failed state.
Nov 27 18:07:50 alarm systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
Nov 27 18:07:50 alarm systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 18:07:50 alarm systemd[1]: Failed to start Network Service.
Nov 27 18:07:50 alarm systemd[1]: systemd-networkd.service: Unit entered failed state.
Nov 27 18:07:50 alarm systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Nov 27 18:07:50 alarm systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Nov 27 18:07:50 alarm systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
Nov 27 18:07:51 alarm systemd[1]: Stopped Login Service.
Nov 27 18:07:51 alarm systemd[1]: Starting Login Service...
Nov 27 18:07:51 alarm systemd[1]: Stopped Network Service.
Nov 27 18:07:51 alarm systemd[1]: Starting Network Service...
Nov 27 18:07:51 alarm systemd[1]: Started Serial Getty on ttyS0.
Nov 27 18:07:51 alarm systemd-networkd[199]: Could not connect to bus: Permission denied
Nov 27 18:07:51 alarm systemd[1]: Started Getty on tty1.
Nov 27 18:07:51 alarm systemd[1]: Reached target Login Prompts.
Nov 27 18:07:51 alarm systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 18:07:51 alarm systemd[1]: Failed to start Network Service.
Nov 27 18:07:51 alarm systemd[1]: systemd-networkd.service: Unit entered failed state.
Nov 27 18:07:51 alarm systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Nov 27 18:07:51 alarm systemd-logind[198]: New seat seat0.
off time, scheduling restart.
Nov 27 18:07:51 alarm systemd[1]: Started Login Service.
Nov 27 18:07:51 alarm systemd[1]: Stopped Network Service.
Nov 27 18:07:51 alarm systemd[1]: Starting Network Service...
Nov 27 18:07:51 alarm systemd-networkd[210]: Could not connect to bus: Permission denied
Nov 27 18:07:51 alarm systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 18:07:51 alarm systemd[1]: Failed to start Network Service.
Nov 27 18:07:51 alarm systemd[1]: systemd-networkd.service: Unit entered failed state.
Nov 27 18:07:51 alarm systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Nov 27 18:07:51 alarm systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
Nov 27 18:07:51 alarm systemd[1]: Stopped Network Service.
Nov 27 18:07:51 alarm systemd[1]: Starting Network Service...
Nov 27 18:07:51 alarm systemd-networkd[212]: Could not connect to bus: Permission denied
Nov 27 18:07:51 alarm systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
Nov 27 18:07:51 alarm systemd[1]: Failed to start Network Service.
Nov 27 18:07:51 alarm systemd[1]: systemd-networkd.service: Unit entered failed
')

[sambul13]

I don't know if this issue is going to be fixed any time soon in ARM distro, since upstream Arch PC release doesn't have this problem. Keep updating OS with pacman to no avail. Anyway, can someone suggest a working Archlinux ARM 4.3 earlier release that starts network normally on DockStar, and where to download it? Current release bricks the device, network can only be activated via Serial Console.

Is there a Netconsole based method to start network after Arch boot, or possibly via Uboot envs? Or may be editing certain OS configs in a way that would work around systemd starting the network after boot? I was trying to trace the bug, but my skills are way too limited to deal with complex systemd & udev interactions.

[WarheadsSE]

systemd-timesyncd would not kill systemd-networkd

[sambul13]

It turns out, "/" dir owner was set to Alarm. So running the below code fixed the issue, but raised the question "why this key system permission was changed from default, thus leading to the device bricking upon ArchLinux ARM install?"

$this->bbcode_second_pass_code('', 'chown root /
chmod 755 /
')

To other device owners, I suggest to download and unpack Arch distro to a USB Thumb EXT3 partition in a VM, chroot to it, check permissions and run the above code if required, before booting your device from the thumb.

[WarheadsSE]

You missed the step of doing this as root, then. `sudo su - root` . Not `sudo blah`.

You gaffed.

[sambul13]

I usually unpack large tarballs to USB Thumbs in a Linux VM as sudo su, since its a lot more efficient compare to downloading and unpacking through DockStar. Never had a problem with this method. My PC Linux VM doesn't have Alarm user, so it was impossible for Alarm user to capture "/" ownership on the USB Thumb at unpacking.

Anyway, thanks for your comments.