My Unraid server is Shutting down randomly, first i think it was the SSD, checked and reformated the whole SSD without errors, 

Then i run a Memtest, with no errors at all. 

SMART is okk too. 

 

The server runs for serveral houres and then it goes offline. 

the logs are a bit wired, this is an example, the logs are full with this: 
 

Apr 29 13:28:32 Server kernel: vethd123a7d: renamed from eth0
Apr 29 13:28:32 Server kernel: docker0: port 32(vethe08ef94) entered disabled state
Apr 29 13:28:32 Server kernel: docker0: port 32(vethe08ef94) entered disabled state
Apr 29 13:28:32 Server kernel: device vethe08ef94 left promiscuous mode
Apr 29 13:28:32 Server kernel: docker0: port 32(vethe08ef94) entered disabled state
Apr 29 13:29:05 Server kernel: docker0: port 32(vethfb022db) entered blocking state
Apr 29 13:29:05 Server kernel: docker0: port 32(vethfb022db) entered disabled state
Apr 29 13:29:05 Server kernel: device vethfb022db entered promiscuous mode
Apr 29 13:29:05 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vethfb022db: link is not ready
Apr 29 13:29:06 Server kernel: eth0: renamed from veth5eba356
Apr 29 13:29:06 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfb022db: link becomes ready
Apr 29 13:29:06 Server kernel: docker0: port 32(vethfb022db) entered blocking state
Apr 29 13:29:06 Server kernel: docker0: port 32(vethfb022db) entered forwarding state
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered blocking state
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state
Apr 29 13:29:32 Server kernel: device veth3c88d1b entered promiscuous mode
Apr 29 13:29:32 Server kernel: IPv6: ADDRCONF(NETDEV_UP): veth3c88d1b: link is not ready
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered blocking state
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered forwarding state
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state
Apr 29 13:29:32 Server kernel: eth0: renamed from veth3e71acd
Apr 29 13:29:32 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth3c88d1b: link becomes ready
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered blocking state
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered forwarding state
Apr 29 13:29:32 Server kernel: veth3e71acd: renamed from eth0
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state
Apr 29 13:29:32 Server kernel: device veth3c88d1b left promiscuous mode
Apr 29 13:29:32 Server kernel: docker0: port 34(veth3c88d1b) entered disabled state
Apr 29 13:29:40 Server kernel: veth5eba356: renamed from eth0
Apr 29 13:29:40 Server kernel: docker0: port 32(vethfb022db) entered disabled state
Apr 29 13:29:40 Server kernel: docker0: port 32(vethfb022db) entered disabled state
Apr 29 13:29:40 Server kernel: device vethfb022db left promiscuous mode
Apr 29 13:29:40 Server kernel: docker0: port 32(vethfb022db) entered disabled state
Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered blocking state
Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered disabled state
Apr 29 13:30:32 Server kernel: device vethda94d6d entered promiscuous mode
Apr 29 13:30:32 Server kernel: IPv6: ADDRCONF(NETDEV_UP): vethda94d6d: link is not ready
Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered blocking state
Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered forwarding state
Apr 29 13:30:32 Server kernel: docker0: port 32(vethda94d6d) entered disabled state
Apr 29 13:30:33 Server kernel: eth0: renamed from vethbfaccc9
Apr 29 13:30:33 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethda94d6d: link becomes ready
Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered blocking state
Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered forwarding state
Apr 29 13:30:33 Server kernel: vethbfaccc9: renamed from eth0
Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered disabled state
Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered disabled state
Apr 29 13:30:33 Server kernel: device vethda94d6d left promiscuous mode
Apr 29 13:30:33 Server kernel: docker0: port 32(vethda94d6d) entered disabled state
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered blocking state
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state
Apr 29 13:31:33 Server kernel: device veth7c1c504 entered promiscuous mode
Apr 29 13:31:33 Server kernel: IPv6: ADDRCONF(NETDEV_UP): veth7c1c504: link is not ready
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered blocking state
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered forwarding state
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state
Apr 29 13:31:33 Server kernel: eth0: renamed from veth6728934
Apr 29 13:31:33 Server kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7c1c504: link becomes ready
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered blocking state
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered forwarding state
Apr 29 13:31:33 Server kernel: veth6728934: renamed from eth0
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state
Apr 29 13:31:33 Server kernel: device veth7c1c504 left promiscuous mode
Apr 29 13:31:33 Server kernel: docker0: port 32(veth7c1c504) entered disabled state

Diag: 

server-diagnostics-20200429-1337.zip

If you haven't yet see here.

bios is up to date but i will check the setting

but why was my system running for month´s and is now stucking daily since 3 days ? 

 

EDIT: Ram speeds are good, no over clock at all. CPU is stock too

Edited April 29, 20206 yr by Wuast94

The log snippet you posted is perfectly normal, if the FAQ suggestions are being followed try this, it might catch something.

5 minutes ago, Wuast94 said:

bios is up to date but i will check the setting

but why was my system running for month´s and is now stucking daily since 3 days ? 

 

EDIT: Ram speeds are good, no over clock at all. CPU is stock too

It's not unusual for things to happen out of the blue.

For example, if you watercool, the gunk buildup (big hoohah with a popular AIO recently) will need some time to happen and eventually the pump can only put in so much continuous high load. Could be even as unlikely as bad TIM that dries up or RAM stick that just fails. Or even an overheated NIC that becomes unstable.

 

Of course, if you recently make changes to the system (even software e.g. new docker / docker settings / VM etc.) then they do stand out as potential causes so you should provide details whatever that changed in tha last 3 days.

10 minutes ago, johnnie.black said:

The log snippet you posted is perfectly normal, if the FAQ suggestions are being followed try this, it might catch something.

i have two tails open, one on my pc and one that is piping it into a txt file on cache drive to see if there is anything usefull on crash

 

2 minutes ago, testdasi said:

Of course, if you recently make changes to the system (even software e.g. new docker / docker settings / VM etc.) then they do stand out as potential causes so you should provide details whatever that changed in tha last 3 days.

i dont change anything the last month at the system, i also dont installed any plugins or anything else 

Im having the same issue, if you boot in to safe mode NO PLUGINS, you'll notice the server doesnt crash/reboot. Now i don't know why. I'm the in same boat as you. But I have discovered this much. If you can figure out what plugin is causing the reboot or system crash please let me know. I'm having the same issue.