Unschelued restart - Intermittent

Supersonical

Dabbler
Joined
Apr 12, 2016
Messages
17
Hi, my freenas box is restarting and i have no idea why.
I have tried looking through the logs but i have to admit that I´m a total noob and can´t se anything obviously causing the restarta.

Here is my logs files https://pastebin.com/raw/PLGCNWLr

Anyone who can please help solve my reboot problems?

Appreciate any help i can get?

My system is,
CPU: Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz (3405.98-MHz K8-class CPU)
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: Z87-DELUXE
Corsair XMS3 8GB (2x4GB) / 1600MHz / DDR3 / CL9 / CMX8GX3M2A1600C9
Corsair Vengeance 16GB (2x8GB) / 1600MHz / DDR3 / CL10 / CML16GX3M2A1600C10
 
D

dlavigne

Guest
Hard to tell without analyzing a full debug. That portion of the log only shows the reboot messages.
 

Supersonical

Dabbler
Joined
Apr 12, 2016
Messages
17
Hard to tell without analyzing a full debug. That portion of the log only shows the reboot messages.
How can i extract a full debug log?
 
D

dlavigne

Guest
System -> Advanced -> Save debug. Note it may contain sensitive info so these are typically included as a private attachment when reporting an issue at bugs.ixsystems.com.
 

Supersonical

Dabbler
Joined
Apr 12, 2016
Messages
17
System -> Advanced -> Save debug. Note it may contain sensitive info so these are typically included as a private attachment when reporting an issue at bugs.ixsystems.com.

Found this in msgbug.txt can this be it?

panic: Unrecoverable machine check exception
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff82178a60
vpanic() at vpanic+0x177/frame 0xffffffff82178ac0
panic() at panic+0x43/frame 0xffffffff82178b20
mca_intr() at mca_intr+0x9b/frame 0xffffffff82178b40
mchk_calltrap() at mchk_calltrap+0x8/frame 0xffffffff82178b40
--- trap 0x1c, rip = 0xffffffff80fa937a, rsp = 0xfffffe065e6a3750, rbp = 0xfffffe065e6a3780 ---
pmap_try_insert_pv_entry() at pmap_try_insert_pv_entry+0x3a/frame 0xfffffe065e6a3780
pmap_copy() at pmap_copy+0x569/frame 0xfffffe065e6a3810
vmspace_fork() at vmspace_fork+0x4da/frame 0xfffffe065e6a3870
fork1() at fork1+0x47a/frame 0xfffffe065e6a3920
sys_fork() at sys_fork+0x39/frame 0xfffffe065e6a3980
amd64_syscall() at amd64_syscall+0xa38/frame 0xfffffe065e6a3ab0
fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe065e6a3ab0
--- syscall (0, FreeBSD ELF64, nosys), rip = 0x8019b974a, rsp = 0x7fffffff7c98, rbp = 0x7fffffff7cf0 ---
KDB: enter: panic
 
D

dlavigne

Guest
A panic could definitely cause a reboot. The trick is figuring out what caused the panic.
 

Supersonical

Dabbler
Joined
Apr 12, 2016
Messages
17
A panic could definitely cause a reboot. The trick is figuring out what caused the panic.

My system is at least 8 years old and been running as my freenas box for at least 5 years (running non stop 24/7). And maybe it´s not that wise to use different ram sticks and on top of that differrent capacities. I´m going to track down some software to benchmark my HW, you don´t have any suggestions :)
 
Top