Hi all,

 

I setup my server and installed Unraid at the weekend and so far I am loving it.  But I am getting a random problem, with the it hanging so I cannot access the gui, or even ping the IP.  I cannot access any of the dockers either.

 

I have attached the diagnostics.

 

I have a quad port intel network card installed, with all 4 ports connected.

 

Not sure if that is causing an issue.  Any help would be appreciated.

 

Thanks

gamingnas-diagnostics-20200331-1653.zip

Setup Syslog Server so syslog will be saved somewhere you can get it after rebooting:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

 

23 minutes ago, trurl said:

Setup Syslog Server so syslog will be saved somewhere you can get it after rebooting:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=781601

 

Thanks, usually after a bit of waiting it does right itself and doesn't need a reboot.

 

I have taken these from the system logs, after it settled down.

 

Mar 31 05:47:05 GamingNAS kernel: docker0: port 4(veth7fc3892) entered blocking state
Mar 31 05:47:05 GamingNAS kernel: docker0: port 4(veth7fc3892) entered forwarding state
Mar 31 05:47:05 GamingNAS kernel: docker0: port 4(veth7fc3892) entered disabled state
Mar 31 05:47:08 GamingNAS kernel: eth0: renamed from veth18ad00d
Mar 31 05:47:08 GamingNAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7fc3892: link becomes ready
Mar 31 05:47:08 GamingNAS kernel: docker0: port 4(veth7fc3892) entered blocking state
Mar 31 05:47:08 GamingNAS kernel: docker0: port 4(veth7fc3892) entered forwarding state
Mar 31 05:47:10 GamingNAS avahi-daemon[2090]: Joining mDNS multicast group on interface veth7fc3892.IPv6 with address fe80::f86d:81ff:fe84:8378.
Mar 31 05:47:10 GamingNAS avahi-daemon[2090]: New relevant interface veth7fc3892.IPv6 for mDNS.
Mar 31 05:47:10 GamingNAS avahi-daemon[2090]: Registering new address record for fe80::f86d:81ff:fe84:8378 on veth7fc3892.*.
Mar 31 06:50:34 GamingNAS kernel: veth18ad00d: renamed from eth0
Mar 31 06:50:34 GamingNAS kernel: docker0: port 4(veth7fc3892) entered disabled state
Mar 31 06:50:34 GamingNAS avahi-daemon[2090]: Interface veth7fc3892.IPv6 no longer relevant for mDNS.
Mar 31 06:50:34 GamingNAS avahi-daemon[2090]: Leaving mDNS multicast group on interface veth7fc3892.IPv6 with address fe80::f86d:81ff:fe84:8378.
Mar 31 06:50:34 GamingNAS kernel: docker0: port 4(veth7fc3892) entered disabled state
Mar 31 06:50:34 GamingNAS kernel: device veth7fc3892 left promiscuous mode
Mar 31 06:50:34 GamingNAS kernel: docker0: port 4(veth7fc3892) entered disabled state
Mar 31 06:50:34 GamingNAS avahi-daemon[2090]: Withdrawing address record for fe80::f86d:81ff:fe84:8378 on veth7fc3892.
Mar 31 06:51:02 GamingNAS kernel: docker0: port 4(veth6f56dd3) entered blocking state
Mar 31 06:51:02 GamingNAS kernel: docker0: port 4(veth6f56dd3) entered disabled state
Mar 31 06:51:02 GamingNAS kernel: device veth6f56dd3 entered promiscuous mode
Mar 31 06:51:02 GamingNAS kernel: IPv6: ADDRCONF(NETDEV_UP): veth6f56dd3: link is not ready
Mar 31 06:51:02 GamingNAS kernel: docker0: port 4(veth6f56dd3) entered blocking state
Mar 31 06:51:02 GamingNAS kernel: docker0: port 4(veth6f56dd3) entered forwarding state
Mar 31 06:51:02 GamingNAS kernel: docker0: port 4(veth6f56dd3) entered disabled state
Mar 31 06:51:03 GamingNAS kernel: eth0: renamed from veth942c193
Mar 31 06:51:03 GamingNAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth6f56dd3: link becomes ready
Mar 31 06:51:03 GamingNAS kernel: docker0: port 4(veth6f56dd3) entered blocking state
Mar 31 06:51:03 GamingNAS kernel: docker0: port 4(veth6f56dd3) entered forwarding state
Mar 31 06:51:05 GamingNAS avahi-daemon[2090]: Joining mDNS multicast group on interface veth6f56dd3.IPv6 with address fe80::f437:57ff:fe38:f64d.
Mar 31 06:51:05 GamingNAS avahi-daemon[2090]: New relevant interface veth6f56dd3.IPv6 for mDNS.
Mar 31 06:51:05 GamingNAS avahi-daemon[2090]: Registering new address record for fe80::f437:57ff:fe38:f64d on veth6f56dd3.*.
Mar 31 08:50:32 GamingNAS kernel: igb 0000:04:00.1 eth2: igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Mar 31 08:50:32 GamingNAS kernel: bond0: link status definitely up for interface eth2, 1000 Mbps full duplex
Mar 31 08:50:40 GamingNAS kernel: igb 0000:04:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Mar 31 08:50:40 GamingNAS kernel: bond0: link status definitely up for interface eth0, 1000 Mbps full duplex

 

Thanks

Hi, I have tried getting a syslog but it did not work.  The hanging is happening randomly.  It happened about 20 mins ago, here are my logs.

 

Apr 8 15:56:28 GamingNAS kernel: br0: port 2(vnet0) entered disabled state
Apr 8 15:56:28 GamingNAS kernel: device vnet0 left promiscuous mode
Apr 8 15:56:28 GamingNAS kernel: br0: port 2(vnet0) entered disabled state
Apr 8 16:01:17 GamingNAS kernel: br0: port 2(vnet0) entered blocking state
Apr 8 16:01:17 GamingNAS kernel: br0: port 2(vnet0) entered disabled state
Apr 8 16:01:17 GamingNAS kernel: device vnet0 entered promiscuous mode
Apr 8 16:01:17 GamingNAS kernel: br0: port 2(vnet0) entered blocking state
Apr 8 16:01:17 GamingNAS kernel: br0: port 2(vnet0) entered forwarding state

 

Any help would appreciated.

 

Thanks

Not necessarily your problem, but motherboards do tend to like matching sets of RAM.  All 4 of your sticks are different from each other.  If you must mix & match, then your best results will come from sticks that all have the same CL timings.

15 hours ago, Squid said:

Not necessarily your problem, but motherboards do tend to like matching sets of RAM.  All 4 of your sticks are different from each other.  If you must mix & match, then your best results will come from sticks that all have the same CL timings.

Hi mate, thanks for the reply. Yeah I know, sadly it was all I had at the time. Will be looking to replace the RAM next payday

 

I have a 4 port pcie intel nic and the onboard nic that I am using.  Is there any benefit to having the extra card, or would I be better off using just the onboard port?