June 3, 201610 yr Jun 3 16:32:25 YES-MEDIASERVER kernel: CPU: Physical Processor ID: 0 Jun 3 16:32:25 YES-MEDIASERVER kernel: CPU: Processor Core ID: 0 Jun 3 16:32:25 YES-MEDIASERVER kernel: mce: CPU supports 22 MCE banks Jun 3 16:32:25 YES-MEDIASERVER kernel: mce: [Hardware Error]: Machine check events logged Jun 3 16:32:25 YES-MEDIASERVER kernel: mce: [Hardware Error]: Machine check events logged Jun 3 16:32:25 YES-MEDIASERVER kernel: CPU0: Thermal monitoring enabled (TM1) Jun 3 16:32:25 YES-MEDIASERVER kernel: process: using mwait in idle threads This week my unRAID server at the office started posting machine check events errors into the syslog. I didn't think to much of it until I started having complete system lockups. Nothing was accessible, VM locks up, mapped drives on other machines drop, and ssh couldn't resolve the server; daily complete system lockups. As I had recently been making config changes (num_stripes, rombar, isolcpu, adding a cheapy usb fan for the user), I reverted everything back to the original settings from before this week. Unfortunately I still get the 2 errors in the same place on the system log upon bootup. This appears to be a genuine hardware fault, but after doing some searching here and on google, I tried to view the mcelog, but unRAID doesn't appear to be packaged with this. Being completely new to nix, even after following installation directions at mcelog.org, I was unable to install the app to view the details of the fault. How do I download & install mcelog? In an effort to try and see exactly what is logged into the syslog at the time of crashing, I currently have a tail on the syslog and also a watch sensors running via putty. However, the cpu temps are pretty consistently running in the 40s, so I don't think its temp related. It seems to happen completely at random, sometimes just while idling. Seemingly unconnected, but suddenly out of the blue while writing this post I decided to reboot my VM and the gpu came up with an error code 43. I was able to resolve that issue by downgrading the drivers to 362, but still the timing seems suspect. At this point, aside from a generous soul instructing me on how to install the mcelog or simply waiting for the crash to occur again and hoping for a decent log entry, I'm not sure where to go next from here. Anyone have any other suggestions I might try? yes-mediaserver-diagnostics-20160603-1546.zip
June 3, 201610 yr The number one thing to check (and the easiest!) is the memory. Run Memtest all night. If not memory, then these things are HARD to figure out! Sorry.
June 4, 201610 yr Author The number one thing to check (and the easiest!) is the memory. Run Memtest all night. If not memory, then these things are HARD to figure out! Sorry. Kk, thank you RobJ, I'll try that out when I get into the office on Monday and let you know what I turn up with.
September 3, 20178 yr Hello Total N00b here how exactly do i get my mcelog? I have nerd tools and mce log installed, just not sure how to get it saved or retrieve it for saving to my VM or resident Mac?
Archived
This topic is now archived and is closed to further replies.