Interface eth0 error on raspberry pi 4

JackEsparrago9 · 21. April 2020

Hi

I have done a clean install and Im triying to add eth0 method dhcp and dns 8.8.8.8 in Interfaces and i got this error.

And when i click i show details.

Code

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run systemd-networkd 2>&1' with exit code '1': /usr/lib/python3/dist-packages/salt/utils/path.py:265: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  if not isinstance(exes, collections.Iterable):
raspberrypi:
----------
          ID: configure_etc_network_interfaces
    Function: file.managed
        Name: /etc/network/interfaces
      Result: True
     Comment: File /etc/network/interfaces is in the correct state
     Started: 00:38:39.922352
    Duration: 59.958 ms
     Changes:
----------
          ID: remove_systemd_networkd_config_files
    Function: module.run
      Result: True
     Comment: file.find: []
     Started: 00:38:39.983770
    Duration: 2.121 ms
     Changes:
              ----------
              file.find:
----------
          ID: remove_netplan_config_files
    Function: module.run
      Result: True
     Comment: file.find: ['/etc/netplan/10-openmediavault-default.yaml', '/etc/netplan/20-openmediavault-eth0.yaml']
     Started: 00:38:39.986175
    Duration: 2.202 ms
     Changes:
              ----------
              file.find:
                  - /etc/netplan/10-openmediavault-default.yaml
                  - /etc/netplan/20-openmediavault-eth0.yaml
----------
          ID: configure_netplan_default
    Function: file.managed
        Name: /etc/netplan/10-openmediavault-default.yaml
      Result: True
     Comment: File /etc/netplan/10-openmediavault-default.yaml updated
     Started: 00:38:39.988662
    Duration: 13.548 ms
     Changes:
              ----------
              diff:
                  New file
              mode:
                  0644
----------
          ID: configure_netplan_ethernet_eth0
    Function: file.managed
        Name: /etc/netplan/20-openmediavault-eth0.yaml
      Result: True
     Comment: File /etc/netplan/20-openmediavault-eth0.yaml updated
     Started: 00:38:40.002608
    Duration: 57.192 ms
     Changes:
              ----------
              diff:
                  New file
              mode:
                  0644
----------
          ID: apply_netplan_config
    Function: cmd.run
        Name: netplan apply
      Result: False
     Comment: Command "netplan apply" run
     Started: 00:38:40.061592
    Duration: 289.165 ms
     Changes:
              ----------
              pid:
                  7866
              retcode:
                  1
              stderr:
                  Traceback (most recent call last):
                    File "/usr/sbin/netplan", line 23, in <module>
                      netplan.main()
                    File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
                      self.run_command()
                    File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command
                      self.func()
                    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 43, in run
                      self.run_command()
                    File "/usr/share/netplan/netplan/cli/utils.py", line 130, in run_command
                      self.func()
                    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 93, in command_apply
                      stderr=subprocess.DEVNULL)
                    File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
                      raise CalledProcessError(retcode, cmd)
                  subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 'net_setup_link', '/sys/class/net/lo']' returned non-zero exit status 1.
              stdout:

Summary for raspberrypi
------------
Succeeded: 5 (changed=5)
Failed:    1
------------
Total states run:     6
Total run time: 424.186 ms in /usr/share/php/openmediavault/system/process.inc:182
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(60): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusAk...', '/tmp/bgoutputcn...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Alles anzeigen

Im on raspberry pi 4. In a recent install i didn't get this error.

Could I get some help?

Thank you.

ryecoaaron · 21. April 2020

Try this:

sudo rm /etc/systemd/network/99-default.link

sudo netplan apply

sudo omv-salt deploy run systemd-networkd

GerardHenninger · 22. April 2020

Just registered an account to say "Thank you".

Had the same problem as the Jack and your solution worked (after a reboot).

JackEsparrago9 · 23. April 2020

Thanks for answering

lassewr · 24. April 2020

That did not work for me. In the end I just requested a new ip lease from the console (thank you https://www.computerhope.com/issues/ch001078.htm)

Sudo dhclient -v

Then I continued to my router and set that, as the static IP address (checked again, already did that earlier)

Now I got access to my Pi once more... IP and local hostname.
I can now successfully change settings in Network. Hostname and local domain... and just to be extra sure. I went to interfaces and added DNS and IPv4 and IPv6 settings as read in the console. Might be overkill, but it finally seems to work.

buttervault · 26. April 2020

thanks. had to register just for this. Tried to clean install thrice before googling this and finding your solution.

benjamin37 · 26. April 2020

Thank you very much ryecoaaron !

I had the same issue while trying to add the ethernet (eth0) interface (as stated in official documentation https://github.com/OpenMediaVa…ing_OMV5_on_an%20R-PI.pdf) with OMV 5 on my RPi 4B.

Trying these commands have fixed the issue.

I guess it is not the "normal" behavior as I cannot see any warning on official documentation and it seems to be working like a charm in this video.

Thank you anyway

Ljukic · 27. April 2020

I have the same problem on mi Pi 3B+, I've tried the three commands reported but after a system reboot I can't access anymore to OMV via SSH.

From my router panel I see Pi 3B+, but it's setted as "non active". How can I resolve this issue?

Thanks!!!

earnil · 27. April 2020

I can confirm this issue on Pi 3B running Raspbian.

Following @lassewr's instructions fixed this for me:

Ljukic · 28. April 2020

Thanks for the reply! I tried but seems no work for me... The output from console is:

Code

pi@raspberrypi:~ $ sudo dhclient -v
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/b8:27:eb:45:17:f6
Sending on   LPF/wlan0/b8:27:eb:45:17:f6
Listening on LPF/eth0/b8:27:eb:10:42:a3
Sending on   LPF/eth0/b8:27:eb:10:42:a3
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
send_packet: Network is down
dhclient.c:2445: Failed to send 300 byte long packet over wlan0 interface.
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
receive_packet failed on wlan0: Network is down
DHCPOFFER of 192.168.1.6 from 192.168.1.1
DHCPREQUEST for 192.168.1.6 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.6 from 192.168.1.1
RTNETLINK answers: File exists
Too few arguments.
bound to 192.168.1.6 -- renewal in 9741 seconds.

Alles anzeigen

It's everything ok? What I have to do after that?

Thanks!

kstenqvist · 29. April 2020

Just created an account to say thank you. I had the same issue and this solved the problem.

rdos14 · 23. Juni 2020

Thanks, that works right on the money.

pudding · 28. Oktober 2020

Sorry, but that does not work for me.

First line gives me

Second outcome:

Any ideas?

ryecoaaron · 28. Oktober 2020

Did you reboot? Is the network adapter still named enp2s0 in the output of ip a? If it isn't, you need to update the omv network setup. omv-firstaid might help.

metRo_ · 26. Dezember 2020

What this sudo rm /etc/systemd/network/99-default.link does?

QubaVR · 10. Februar 2021

Thank you so much! I have run into the very problem on my Pi4 OMV just yesterday and this method helped me fix it!

sutharsha · 1. Dezember 2021

Registered to say Thank you.

This sorted it out after 3 hours of head-banging.

CT678 · 17. Januar 2023

thx! worked great to restore eth0!
in my case, Debian / Armbian buster (20.02.5), it was:
sudo rm /lib/systemd/network/99-default.link
looked it up with:
networkctl status eth0

Interface eth0 error on raspberry pi 4

Jetzt mitmachen!

Ähnliche Themen

Raspberry Pi 4 (OMV5) installation - Why is my NAS getting two IP addresses?

Transmission Openvpn Run Errors

Pihole on Docker - DNS resolution is currently unavailable error

Can't get any Docker containers to run on Nano Pi Neo2 (Arm64v8) on Armbian Buster