Fix common errors gave me the following message:Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums

 

So here I am. Here's the call trace from the log and I am attaching my diagnostics zip as well. I'm not sure what a call trace is or if this is something to be concerned about so any guidance would be greatly appreciated. 

 

 

Jan 26 00:38:17 Server kernel: Call Trace:

Jan 26 00:38:17 Server kernel: <IRQ>  [<ffffffff8136f79f>] dump_stack+0x61/0x7e

Jan 26 00:38:17 Server kernel: [<ffffffff8104a4ab>] warn_slowpath_common+0x8f/0xa8

Jan 26 00:38:17 Server kernel: [<ffffffff8155871e>] ? dev_watchdog+0x18c/0x1f2

Jan 26 00:38:17 Server kernel: [<ffffffff8104a507>] warn_slowpath_fmt+0x43/0x4b

Jan 26 00:38:17 Server kernel: [<ffffffff8155871e>] dev_watchdog+0x18c/0x1f2

Jan 26 00:38:17 Server kernel: [<ffffffff81558592>] ? qdisc_rcu_free+0x39/0x39

Jan 26 00:38:17 Server kernel: [<ffffffff81558592>] ? qdisc_rcu_free+0x39/0x39

Jan 26 00:38:17 Server kernel: [<ffffffff81089419>] call_timer_fn.isra.6+0x17/0x6b

Jan 26 00:38:17 Server kernel: [<ffffffff810895f2>] run_timer_softirq+0x185/0x1ac

Jan 26 00:38:17 Server kernel: [<ffffffff8104d6d3>] __do_softirq+0xc3/0x1b6

Jan 26 00:38:17 Server kernel: [<ffffffff8104d950>] irq_exit+0x3d/0x82

Jan 26 00:38:17 Server kernel: [<ffffffff8103569b>] smp_trace_apic_timer_interrupt+0x7b/0x88

Jan 26 00:38:17 Server kernel: [<ffffffff810356b1>] smp_apic_timer_interrupt+0x9/0xb

Jan 26 00:38:17 Server kernel: [<ffffffff8162a972>] apic_timer_interrupt+0x82/0x90

Jan 26 00:38:17 Server kernel: <EOI>  [<ffffffff81508581>] ? cpuidle_enter_state+0xf0/0x148

Jan 26 00:38:17 Server kernel: [<ffffffff8150853a>] ? cpuidle_enter_state+0xa9/0x148

Jan 26 00:38:17 Server kernel: [<ffffffff815085fb>] cpuidle_enter+0x12/0x14

Jan 26 00:38:17 Server kernel: [<ffffffff810765ca>] call_cpuidle+0x4e/0x50

Jan 26 00:38:17 Server kernel: [<ffffffff81076752>] cpu_startup_entry+0x186/0x1fd

Jan 26 00:38:17 Server kernel: [<ffffffff81033d5f>] start_secondary+0xf4/0xf7

Jan 26 00:38:17 Server kernel: ---[ end trace 80bb3b11722e7698 ]---

 

server-diagnostics-20170131-2015.zip

Looks like the realtek network driver crashed for some reason and then managed to recover and restart it self. Why isn't really obvious, but make sure that the cabling is nice and secure.  Wouldn't hurt to also run a memtest from the boot menu for a pass just to rule out any memory issues.

 

Also, you Kingston SSD seems to be having a heart attack every once in a while.  Make sure that the cabling is nice and secure to it and any power splitters, etc.

I'll pop it open and check the power I added another drive recently and had to use an extension for the power on the Kingston which is probably the issue there. I'll run memtest after I check out my cabling. Thanks so much!