Network goes down a couple of times a day

  • Mac mini 6,2 (Late 2012 Server)

    8GB RAM

    1TB Internal HDD

    5TB External USB 3.0

    1TB External (Time Machine Backup) USB 3.0


    This is my first post on the forum requesting for help so pardon the ignorance if I missed something very obvious.


    Just recently took the plunge and installed OMV on my old Mac mini 2012 that's been running without any issues, albeit slow and repurposed as NAS media device.


    For the most part when it's working, it's fast and I have a few docker instances running as well,


    A couple of times a day the network goes down and I'm unable to access it. Unable to ping for about 10 minutes and then it starts to work.


    When I view the Sys logs this is what I see right before the link goes down


    [0000007e:0000007e:(0000:0000:01ff):0000:(0000:0000:0000:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.456693] tg3 0000:01:00.0 enp1s0f0: Link is down

    Sep 15 12:46:32 miniosx systemd-networkd[355]: enp1s0f0: Lost carrier

    Sep 15 12:46:32 miniosx avahi-daemon[929]: Withdrawing address record for 192.168.1.85 on enp1s0f0.

    Sep 15 12:46:32 miniosx avahi-daemon[929]: Leaving mDNS multicast group on interface enp1s0f0.IPv4 with address 192.168.1.85.

    Sep 15 12:46:32 miniosx avahi-daemon[929]: Interface enp1s0f0.IPv4 no longer relevant for mDNS.

    Sep 15 12:46:36 miniosx kernel: [70588.049891] tg3 0000:01:00.0 enp1s0f0: Link is up at 1000 Mbps, full duplex

    Sep 15 12:46:36 miniosx kernel: [70588.049921] tg3 0000:01:00.0 enp1s0f0: Flow control is off for TX and off for RX

    Sep 15 12:46:36 miniosx kernel: [70588.049924] tg3 0000:01:00.0 enp1s0f0: EEE is disabled

    Sep 15 12:46:36 miniosx systemd-networkd[355]: enp1s0f0: Gained carrier

    Sep 15 12:46:36 miniosx avahi-daemon[929]: Joining mDNS multicast group on interface enp1s0f0.IPv4 with address 192.168.1.85.

    Sep 15 12:46:36 miniosx avahi-daemon[929]: New relevant interface enp1s0f0.IPv4 for mDNS.

    Sep 15 12:46:36 miniosx systemd-networkd[355]: enp1s0f0: Configured

    Sep 15 12:46:36 miniosx avahi-daemon[929]: Registering new address record for 192.168.1.85 on enp1s0f0.IPv4.


    And more after......

    miniosx kernel: [70581.309993] tg3 0000:01:00.0 enp1s0f0: transmit timed out, resetting

    kernel: [70584.425720] tg3 0000:01:00.0 enp1s0f0: 0x00000000: 0x168614e4, 0x00100406, 0x02000001, 0x00800040 (lots of Kernel errors)

    Sep 15 12:46:32 miniosx kernel: [70584.428295] tg3 0000:01:00.0 enp1s0f0: 0x00007500: 0x00000000, 0x00000000, 0x00000080, 0x00000000

    Sep 15 12:46:32 miniosx kernel: [70584.428307] tg3 0000:01:00.0 enp1s0f0: 0: Host status block [00000001:00000038:(0000:01f9:0000):(0000:0010)]

    Sep 15 12:46:32 miniosx kernel: [70584.428319] tg3 0000:01:00.0 enp1s0f0: 0: NAPI info [00000038:00000038:(01fd:0010:01ff):0000:(00c9:0000:0000:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.428331] tg3 0000:01:00.0 enp1s0f0: 1: Host status block [00000001:00000024:(0000:0000:0000):(0296:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.428343] tg3 0000:01:00.0 enp1s0f0: 1: NAPI info [00000024:00000024:(0000:0000:01ff):0296:(0096:0096:0000:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.428354] tg3 0000:01:00.0 enp1s0f0: 2: Host status block [00000001:000000b0:(027a:0000:0000):(0000:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.428364] tg3 0000:01:00.0 enp1s0f0: 2: NAPI info [000000b0:000000b0:(0000:0000:01ff):027a:(007a:007a:0000:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.428376] tg3 0000:01:00.0 enp1s0f0: 3: Host status block [00000001:00000023:(0000:0000:0000):(0000:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.428387] tg3 0000:01:00.0 enp1s0f0: 3: NAPI info [00000023:00000023:(0000:0000:01ff):00f1:(00f1:00f1:0000:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.428396] tg3 0000:01:00.0 enp1s0f0: 4: Host status block [00000001:0000007e:(0000:0000:0000):(0000:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.428408] tg3 0000:01:00.0 enp1s0f0: 4: NAPI info [0000007e:0000007e:(0000:0000:01ff):0000:(0000:0000:0000:0000)]

    Sep 15 12:46:32 miniosx kernel: [70584.456693] tg3 0000:01:00.0 enp1s0f0: Link is down

    Sep 15 12:46:32 miniosx systemd-networkd[355]: enp1s0f0: Lost carrier

    Sep 15 12:46:32 miniosx avahi-daemon[929]: Withdrawing address record for 192.168.1.85 on enp1s0f0.

    Sep 15 12:46:32 miniosx avahi-daemon[929]: Leaving mDNS multicast group on interface enp1s0f0.IPv4 with address 192.168.1.85.

    Sep 15 12:46:32 miniosx avahi-daemon[929]: Interface enp1s0f0.IPv4 no longer relevant for mDNS.

    Sep 15 12:46:36 miniosx kernel: [70588.049891] tg3 0000:01:00.0 enp1s0f0: Link is up at 1000 Mbps, full duplex

    Sep 15 12:46:36 miniosx kernel: [70588.049921] tg3 0000:01:00.0 enp1s0f0: Flow control is off for TX and off for RX

    Sep 15 12:46:36 miniosx kernel: [70588.049924] tg3 0000:01:00.0 enp1s0f0: EEE is disabled

    Sep 15 12:46:36 miniosx systemd-networkd[355]: enp1s0f0: Gained carrier

    Sep 15 12:46:36 miniosx avahi-daemon[929]: Joining mDNS multicast group on interface enp1s0f0.IPv4 with address 192.168.1.85.

    Sep 15 12:46:36 miniosx avahi-daemon[929]: New relevant interface enp1s0f0.IPv4 for mDNS.

    Sep 15 12:46:36 miniosx systemd-networkd[355]: enp1s0f0: Configured

    Sep 15 12:46:36 miniosx avahi-daemon[929]: Registering new address record for 192.168.1.85 on enp1s0f0.IPv4.


    10 ~ 15 minutes later the network is reachable again...


    I don't understand what these errors mean. Tried googling some of them but came up short.

    Is it a network driver issue or Kernel issue that requires an update?


    Any input would be much appreciated.

  • Hi,

    I see you are running 5.6.15-1 (Usul), where did you get that?. I run 5.6.14-1 without any issues.

    Linux Mint (Edge) EndeavourOS Arch Linux

    OMV7 NAS, bond0 LACP, Fractal Design Define R5 Case, Kodi "Omega", FreeBSD pfSense Plus firewall/router

    • Offizieller Beitrag

    The regular OMV updates.... Didn't think twice about updating. Is there anyway to downgrade without having to reinstall.

    As a general rule (unless there is a reason for it) it is preferable to have the system updated. I believe that the solution to your problem should not be to degrade. Have a little patience and wait for a wise man around here to answer you.

    I run the same version as you without problems.

    From my ignorance, I suggest to check the network cable and the router ... and wait for an answer better than mine.

  • Hi,

    I see you are running 5.6.15-1 (Usul), where did you get that?. I run 5.6.14-1 without any issues.

    And your point is???


    cobraiti

    The fact that your on the latest version of OMV doesn't mean nothing to your problem.


    Either you have faulty connections or your PC is doing something to switch off resources.

  • The regular OMV updates.... Didn't think twice about updating. Is there anyway to downgrade without having to reinstall.

    Well, I just checked OMV5 for update, nothing. Still on 5.6.14-1/ Hmmmm.

    Linux Mint (Edge) EndeavourOS Arch Linux

    OMV7 NAS, bond0 LACP, Fractal Design Define R5 Case, Kodi "Omega", FreeBSD pfSense Plus firewall/router

  • Soma & chente thanks.


    I'll start with replacing the cables first. It's possible the issue is hardware related. Wasn't sure if it was the OS.


    I read the release notes to the updates before updating, nothing related to network drivers so went ahead with it.

  • Soma "And your point is???"

    The point is: Is the 5.6.15-1 stable release, was it installed through OMV Update Management?. As of 30 seconds ago I still am not receiving this OMV update on my NAS. So, where did he get it, OMV site (openmediavault.org) that actually is showing 5.6.15-1_all.deb file and installed manually. That might make a difference, hence the question.

    Linux Mint (Edge) EndeavourOS Arch Linux

    OMV7 NAS, bond0 LACP, Fractal Design Define R5 Case, Kodi "Omega", FreeBSD pfSense Plus firewall/router

  • As of 30 seconds ago I still am not receiving this OMV update on my NAS.

    Sorry but just because you don't get the updates, doesn't mean other people also won't get them.

    You should sort out what is wrong on your setup and don't question why other's are working or from where do they get it.


    And a reply that your running 5..6.14-1 and everything is OK doesn't had nothing to a solution for the OP.

    Specially, that the OP was already considering that He shouldn't made the update when, I can garantie you that he received a notice on the OMV updates page (has you also should).


    Sorry (again) for beeing blunt...

    • Offizieller Beitrag

    As of 30 seconds ago I still am not receiving this OMV update on my NAS.

    Do you have omv-extras installed? If yes, what happens if you go to omv-extras >> updates >> omv-update?


    Any errors shown in the ouput?

  • Man, I do not know what is your problem. All I said that I do not see 5.5.15-1 update through OMV. So stop attacking people for asking questions. I see that your command of English language is somewhat limited so I will contribute your responses to that, for now.

    Linux Mint (Edge) EndeavourOS Arch Linux

    OMV7 NAS, bond0 LACP, Fractal Design Define R5 Case, Kodi "Omega", FreeBSD pfSense Plus firewall/router

  • Do you have omv-extras installed? If yes, what happens if you go to omv-extras >> updates >> omv-update?


    Any errors shown in the ouput?

    Yes, I have omv-extras installed and everything is working fine including Docker and Portainer. I do not get any errors when checking for new updated through OMV5, nor I get any notifications that new updates are available, hence my question regarding OMV 5.6.15-1. I know that it is available (.deb file) on OMV site. But not through updating OMV.

    Linux Mint (Edge) EndeavourOS Arch Linux

    OMV7 NAS, bond0 LACP, Fractal Design Define R5 Case, Kodi "Omega", FreeBSD pfSense Plus firewall/router

    • Offizieller Beitrag

    I do not get any errors when checking for new updated through OMV5

    ok. Does this include when you do it like described above?


    omv-extras >> updates >> omv-update


    or when you do omv-upgrade from CLI? Might be best if you post the ouput here using the </> code box

  • ok. Does this include when you do it like described above?


    omv-extras >> updates >> omv-update


    or when you do omv-upgrade from CLI? Might be best if you post the ouput here using the </> code box

    Yes, from OMV. I did not try from the console, yet. Give me couple of minutes and I will let you know.

    Here is output from omv-upgrade:

    Linux NAS 5.10.0-0.bpo.8-amd64 #1 SMP Debian 5.10.46-4~bpo10+1 (2021-08-07) x86_64


    The programs included with the Debian GNU/Linux system are free software;

    the exact distribution terms for each program are described in the

    individual files in /usr/share/doc/*/copyright.


    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

    permitted by applicable law.

    Last login: Sun Sep 12 08:52:26 2021

    {root@NAS}:/root:>omv-upgrade

    Err:1 http://deb.debian.org/debian buster InRelease

    Could not resolve 'deb.debian.org'

    Err:2 http://deb.debian.org/debian buster-updates InRelease

    Could not resolve 'deb.debian.org'

    Err:3 https://download.docker.com/linux/debian buster InRelease

    Could not resolve 'download.docker.com'

    Err:4 http://linux.teamviewer.com/deb stable InRelease

    Could not resolve 'linux.teamviewer.com'

    Err:5 https://openmediavault-plugin-…github.io/packages/debian usul InRelease

    Could not resolve 'openmediavault-plugin-developers.github.io'

    Err:6 https://openmediavault-plugin-…github.io/packages/debian usul-extras InRelease

    Could not resolve 'openmediavault-plugin-developers.github.io'

    Err:7 http://httpredir.debian.org/debian buster-backports InRelease

    Could not resolve 'httpredir.debian.org'

    Get:8 file:/var/cache/openmediavault/archives InRelease

    Ign:8 file:/var/cache/openmediavault/archives InRelease

    Err:9 http://security.debian.org/debian-security buster/updates InRelease

    Could not resolve 'security.debian.org'

    Get:10 file:/var/cache/openmediavault/archives Release

    Ign:10 file:/var/cache/openmediavault/archives Release

    Get:11 file:/var/cache/openmediavault/archives Packages

    Ign:11 file:/var/cache/openmediavault/archives Packages

    Get:12 file:/var/cache/openmediavault/archives Translation-en

    Ign:12 file:/var/cache/openmediavault/archives Translation-en

    Err:13 http://packages.openmediavault.org/public usul InRelease

    Could not resolve 'packages.openmediavault.org'

    Get:11 file:/var/cache/openmediavault/archives Packages

    Ign:11 file:/var/cache/openmediavault/archives Packages

    Get:12 file:/var/cache/openmediavault/archives Translation-en

    Ign:12 file:/var/cache/openmediavault/archives Translation-en

    Get:11 file:/var/cache/openmediavault/archives Packages

    Ign:11 file:/var/cache/openmediavault/archives Packages

    Get:12 file:/var/cache/openmediavault/archives Translation-en

    Ign:12 file:/var/cache/openmediavault/archives Translation-en

    Get:11 file:/var/cache/openmediavault/archives Packages

    Ign:11 file:/var/cache/openmediavault/archives Packages

    Err:14 https://openmediavault.github.io/packages usul InRelease

    Could not resolve 'openmediavault.github.io'

    Get:12 file:/var/cache/openmediavault/archives Translation-en

    Ign:12 file:/var/cache/openmediavault/archives Translation-en

    Get:11 file:/var/cache/openmediavault/archives Packages

    Ign:11 file:/var/cache/openmediavault/archives Packages

    Get:12 file:/var/cache/openmediavault/archives Translation-en

    Ign:12 file:/var/cache/openmediavault/archives Translation-en

    Get:11 file:/var/cache/openmediavault/archives Packages

    Ign:11 file:/var/cache/openmediavault/archives Packages

    Get:12 file:/var/cache/openmediavault/archives Translation-en

    Ign:12 file:/var/cache/openmediavault/archives Translation-en

    Get:11 file:/var/cache/openmediavault/archives Packages

    Get:12 file:/var/cache/openmediavault/archives Translation-en

    Ign:12 file:/var/cache/openmediavault/archives Translation-en

    Reading package lists... Done

    N: Ignoring file 'omvextras.list_org' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension

    W: Failed to fetch http://deb.debian.org/debian/dists/buster/InRelease Could not resolve 'deb.debian.org'

    W: Failed to fetch http://deb.debian.org/debian/dists/buster-updates/InRelease Could not resolve 'deb.debian.org'

    W: Failed to fetch https://download.docker.com/li…an/dists/buster/InRelease Could not resolve 'download.docker.com'

    W: Failed to fetch http://linux.teamviewer.com/deb/dists/stable/InRelease Could not resolve 'linux.teamviewer.com'

    W: Failed to fetch https://openmediavault-plugin-…bian/dists/usul/InRelease Could not resolve 'openmediavault-plugin-developers.github.io'

    W: Failed to fetch https://openmediavault-plugin-…sts/usul-extras/InRelease Could not resolve 'openmediavault-plugin-developers.github.io'

    W: Failed to fetch http://httpredir.debian.org/de…uster-backports/InRelease Could not resolve 'httpredir.debian.org'

    W: Failed to fetch http://security.debian.org/deb…/buster/updates/InRelease Could not resolve 'security.debian.org'

    W: Failed to fetch http://packages.openmediavault…blic/dists/usul/InRelease Could not resolve 'packages.openmediavault.org'

    W: Failed to fetch https://openmediavault.github.…ages/dists/usul/InRelease Could not resolve 'openmediavault.github.io'

    W: Some index files failed to download. They have been ignored, or old ones used instead.

    Reading package lists... Done

    Building dependency tree

    Reading state information... Done

    Calculating upgrade... Done

    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

    N: Ignoring file 'omvextras.list_org' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension

    Linux Mint (Edge) EndeavourOS Arch Linux

    OMV7 NAS, bond0 LACP, Fractal Design Define R5 Case, Kodi "Omega", FreeBSD pfSense Plus firewall/router

    • Offizieller Beitrag

    Could not resolve 'deb.debian.org'

    You have a DNS issue. Are you using a static IP?


    If yes, make sure to add a DNS server in the settings of OMV System >> Network >> Interfaces >> select the interface and press Edit. Should be your router IP and additionally a public DNS server like 1.0.0.1. (see picture).


    It you are not using static IP or if this does not solve it, report back.

    • Offizieller Beitrag

    If it does not fix the issue, post the output of each of these commands (please use the </> code box)


    sudo cat /etc/resolv.conf

    sudo ls -al /etc/resolv.conf

    sudo systemctl status systemd-resolved.service

    • Offizieller Beitrag

    N: Ignoring file 'omvextras.list_org' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension

    Did you change the file name?

    Do you have another file called omvextras.list in /etc/apt/sources.list.d/?

  • - Changed in OMV from static to DHCP --> problem fixed.


    THANKS.

    Linux Mint (Edge) EndeavourOS Arch Linux

    OMV7 NAS, bond0 LACP, Fractal Design Define R5 Case, Kodi "Omega", FreeBSD pfSense Plus firewall/router

  • Well I've replaced the ethernet cable (Cat6) and it's been working well until yesterday when trying to FTP a file to the server, it dropped connection again. 10 minutes later it was up again. Very weird.


    By the way should I keep a static ip for OMV or not?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!