Odroid-HC2 woes

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Odroid-HC2 woes

      I recently got an odroid-HC2 and installed OMV on it on a new Samsung SD card. I am using the power supply it came with from odroid.co.uk.

      The system runs fine for 3ish days then it looses network connection. This can easily be fixed by removing and replacing the Ethernet cable but this is obviously not useful for a NAS device.

      Other errors I have read on this forum related to similar devices seem to be power supply or sd card based but relate to the whole system crashing. My issue seems specific to the network itself.

      The OMV logs give no indication of errors though one line seems to relate to a post I found via google about an issue with the USB driver.

      Anyone aware of a similar issue and what the fix might be or should I return the odroid?
    • prupert wrote:

      should I return the odroid?
      Only if you think 'The last thing I added to my setup always must be at fault' is good troubleshooting guidance.

      You've problems with a network connection. A connection involves more than one point of failure. It's this new thing (HC2), it's a cable and it's the thing the cable plugs into (3 points of failure -- why are you thinking only about the HC2?)
    • So, the reason I am thinking it is the HC2 is since replugging the cable fixes the connection, this implies somethings killed the connection and replugging it resets that - though yeah, could also be the cable so I shall try an alternative cable.

      Here is the syslog when the connection dies:

      Source Code

      1. Jun 26 20:30:01 omv CRON[21877]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)
      2. Jun 26 20:35:01 omv CRON[22042]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
      3. Jun 26 20:36:13 omv avahi-daemon[914]: Withdrawing address record for 192.168.1.22 on enx001e06328264.
      4. Jun 26 20:36:13 omv avahi-daemon[914]: Leaving mDNS multicast group on interface enx001e06328264.IPv4 with address 192.168.1.22.
      5. Jun 26 20:36:13 omv avahi-daemon[914]: Interface enx001e06328264.IPv4 no longer relevant for mDNS.
      6. Jun 26 20:36:15 omv ntpd[1497]: Deleting interface #11 enx001e06328264, 192.168.1.22#123, interface stats: received=117, sent=119, dropped=0, active_time=59759 secs
      7. Jun 26 20:36:15 omv ntpd[1497]: 88.150.240.202 local addr 192.168.1.22 -> <null>
      8. Jun 26 20:36:42 omv monit[1495]: Cannot translate '127.0.0.1' to IP address -- Address family for hostname not supported
      9. Jun 26 20:36:42 omv monit[1495]: 'nginx' failed protocol test [HTTP] at [127.0.0.1]:80 [TCP/IP] -- Cannot resolve [127.0.0.1]:80
      10. Jun 26 20:37:12 omv monit[1495]: Cannot translate '127.0.0.1' to IP address -- Address family for hostname not supported
      11. Jun 26 20:37:12 omv monit[1495]: 'nginx' failed protocol test [HTTP] at [127.0.0.1]:80 [TCP/IP] -- Cannot resolve [127.0.0.1]:80
      12. Jun 26 20:37:12 omv monit[1495]: 'nginx' trying to restart
      13. Jun 26 20:37:12 omv monit[1495]: 'nginx' stop: '/bin/systemctl stop nginx'
      14. Jun 26 20:37:13 omv systemd[1]: Stopping A high performance web server and a reverse proxy server...
      15. Jun 26 20:37:13 omv systemd[1]: Stopped A high performance web server and a reverse proxy server.
      16. Jun 26 20:37:13 omv monit[1495]: 'nginx' start: '/bin/systemctl start nginx'
      17. Jun 26 20:37:13 omv systemd[1]: Starting A high performance web server and a reverse proxy server...
      18. Jun 26 20:37:13 omv systemd[1]: Started A high performance web server and a reverse proxy server.
      19. Jun 26 20:37:43 omv monit[1495]: Cannot translate '127.0.0.1' to IP address -- Address family for hostname not supported
      20. Jun 26 20:37:43 omv monit[1495]: 'nginx' failed protocol test [HTTP] at [127.0.0.1]:80 [TCP/IP] -- Cannot resolve [127.0.0.1]:80
      21. Jun 26 20:37:43 omv monit[1495]: 'nginx' trying to restart
      22. Jun 26 20:37:43 omv monit[1495]: 'nginx' stop: '/bin/systemctl stop nginx'
      Display All


      For whatever reason the interface gets removed, which then causes nginx to go nuts as it can't host the OMV pages and then the rest of the log is full with nginx trying to recover. As you can see though, there is nothing unusual prior to avahi-daemon removing the address record (line 5) which is odd. Are there any other logs to look at other than syslog that might shed some light on this?

      I've got a USB-UART bridge so can putty in that way and can see the system is still up, so its network specific this issue.

      Ifconfig -a when the network appears broken gives:

      Source Code

      1. enx001e06328264: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      2. inet6 fe80::18f2:23a8:13f4:7e0 prefixlen 64 scopeid 0x20<link>
      3. ether 00:1e:06:32:82:64 txqueuelen 1000 (Ethernet)
      4. RX packets 1898701 bytes 1512931116 (1.4 GiB)
      5. RX errors 0 dropped 162 overruns 0 frame 0
      6. TX packets 1238354 bytes 2613134175 (2.4 GiB)
      7. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
      8. lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
      9. inet 127.0.0.1 netmask 255.0.0.0
      10. inet6 ::1 prefixlen 128 scopeid 0x10<host>
      11. loop txqueuelen 1 (Local Loopback)
      12. RX packets 73373 bytes 8291469 (7.9 MiB)
      13. RX errors 0 dropped 0 overruns 0 frame 0
      14. TX packets 73373 bytes 8291469 (7.9 MiB)
      15. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
      Display All
      Its then possible to fix the network connection (via UART) by bringing the interface down and then up. So, by running these two commands:
      ip link set dev enx001e06328264 down
      ip link set dev enx001e06328264 up

      The log now shows:

      Source Code

      1. Jun 26 23:28:17 omv NetworkManager[884]: <info> [1530052097.5260] device (enx001e06328264): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40]
      2. Jun 26 23:28:17 omv NetworkManager[884]: <info> [1530052097.5377] manager: NetworkManager state is now CONNECTED_LOCAL
      3. Jun 26 23:28:17 omv NetworkManager[884]: <info> [1530052097.5432] manager: NetworkManager state is now DISCONNECTED
      4. Jun 26 23:28:18 omv kernel: [304764.028268] IPv6: ADDRCONF(NETDEV_UP): enx001e06328264: link is not ready
      5. Jun 26 23:28:18 omv kernel: [304764.043939] r8152 6-1:1.0 enx001e06328264: carrier on
      6. Jun 26 23:28:18 omv kernel: [304764.044056] IPv6: ADDRCONF(NETDEV_CHANGE): enx001e06328264: link becomes ready
      7. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.0669] device (enx001e06328264): link connected
      8. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.0687] device (enx001e06328264): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
      9. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.0709] policy: auto-activating connection 'Wired connection 1'
      10. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.0750] device (enx001e06328264): Activation: starting connection 'Wired connection 1' (72b9f1d5-9d26-3ce6-98fa-3ca764ea4bc9)
      11. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.0759] device (enx001e06328264): state change: disconnected -> prepare (reason 'none') [30 40 0]
      12. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.0765] manager: NetworkManager state is now CONNECTING
      13. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.0783] device (enx001e06328264): state change: prepare -> config (reason 'none') [40 50 0]
      14. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.0796] device (enx001e06328264): state change: config -> ip-config (reason 'none') [50 70 0]
      15. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.0965] dhcp4 (enx001e06328264): dhclient started with pid 30262
      16. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1615] dhcp4 (enx001e06328264): address 192.168.1.22
      17. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1615] dhcp4 (enx001e06328264): plen 24 (255.255.255.0)
      18. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1616] dhcp4 (enx001e06328264): gateway 192.168.1.1
      19. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1616] dhcp4 (enx001e06328264): server identifier 192.168.1.1
      20. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1616] dhcp4 (enx001e06328264): lease time 86400
      21. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1617] dhcp4 (enx001e06328264): hostname 'omv'
      22. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1618] dhcp4 (enx001e06328264): nameserver '192.168.1.1'
      23. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1618] dhcp4 (enx001e06328264): state changed unknown -> bound
      24. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1664] device (enx001e06328264): state change: ip-config -> ip-check (reason 'none') [70 80 0]
      25. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1697] device (enx001e06328264): state change: ip-check -> secondaries (reason 'none') [80 90 0]
      26. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1712] device (enx001e06328264): state change: secondaries -> activated (reason 'none') [90 100 0]
      27. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1719] manager: NetworkManager state is now CONNECTED_LOCAL
      28. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1756] manager: NetworkManager state is now CONNECTED_GLOBAL
      29. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1761] policy: set 'Wired connection 1' (enx001e06328264) as default for IPv4 routing and DNS
      30. Jun 26 23:28:18 omv NetworkManager[884]: <info> [1530052098.1770] device (enx001e06328264): Activation: successful, device activated.
      Display All
      Ifconfig -a now shows an IP address:

      Source Code

      1. enx001e06328264: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      2. inet 192.168.1.22 netmask 255.255.255.0 broadcast 192.168.1.255
      3. inet6 fe80::18f2:23a8:13f4:7e0 prefixlen 64 scopeid 0x20<link>
      4. ether 00:1e:06:32:82:64 txqueuelen 1000 (Ethernet)
      5. RX packets 1899654 bytes 1513058146 (1.4 GiB)
      6. RX errors 0 dropped 162 overruns 0 frame 0
      7. TX packets 1238450 bytes 2613150616 (2.4 GiB)
      8. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
      9. lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
      10. inet 127.0.0.1 netmask 255.0.0.0
      11. inet6 ::1 prefixlen 128 scopeid 0x10<host>
      12. loop txqueuelen 1 (Local Loopback)
      13. RX packets 73446 bytes 8299726 (7.9 MiB)
      14. RX errors 0 dropped 0 overruns 0 frame 0
      15. TX packets 73446 bytes 8299726 (7.9 MiB)
      16. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
      Display All
      To be clear, I didn't disconnect the cable to fix this, I simply puttyed in via USB UART and brought the connection down and then up. By doing this, the OMV webpage comes back on line and the shared folders on the windows network reappears.

      So, in my mind, something is causing the interface to fall over, but I've no idea what....