alhatmy Posted August 29, 2019 Share Posted August 29, 2019 Hi all, I can see this error in "Fix Common Problems"; Machine Check Events detected on your server.. Quote "Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged" Just installed the mcelog, how to output the log? If it's from "System Log" will the above report will be included or i have to run something before exporting it. Quote Link to comment
Kevek79 Posted September 2, 2019 Share Posted September 2, 2019 Go to Tools --> Diagnostics Create a diagnostics file and attach to your next post. Quote Link to comment
alhatmy Posted September 2, 2019 Author Share Posted September 2, 2019 (edited) attached * removed Edited September 2, 2019 by alhatmy Quote Link to comment
Kevek79 Posted September 2, 2019 Share Posted September 2, 2019 (edited) I'm by no means an expert, but there are a couple of those entries in your syslog Aug 21 09:53:18 Tower kernel: mce: [Hardware Error]: Machine check events logged Aug 21 09:53:18 Tower kernel: EDAC sbridge MC1: HANDLING MCE MEMORY ERROR Aug 21 09:53:18 Tower kernel: EDAC sbridge MC1: CPU 10: Machine Check Event: 0 Bank 7: cc00008000010092 Aug 21 09:53:18 Tower kernel: EDAC sbridge MC1: TSC 119cdde8e0587a Aug 21 09:53:18 Tower kernel: EDAC sbridge MC1: ADDR 1a7f729580 Aug 21 09:53:18 Tower kernel: EDAC sbridge MC1: MISC 207c3e86 Aug 21 09:53:18 Tower kernel: EDAC sbridge MC1: PROCESSOR 0:306e4 TIME 1566366798 SOCKET 1 APIC 20 Aug 21 09:53:18 Tower kernel: EDAC MC1: 2 CE memory read error on CPU_SrcID#1_Ha#0_Chan#2_DIMM#1 (channel:2 slot:1 page:0x1a7f729 offset:0x580 grain:32 syndrome:0x0 - OVERFLOW area:DRAM err_code:0001:0092 socket:1 ha:0 channel_mask:4 rank:4) Error seams to be memory related, but you will need to wait and let the real gurus look into your logs to help you figuring out what is going on here. Edited September 2, 2019 by Kevek79 readability Quote Link to comment
Squid Posted September 2, 2019 Share Posted September 2, 2019 Bad ramSent from my NSA monitored device Quote Link to comment
alhatmy Posted September 2, 2019 Author Share Posted September 2, 2019 Thank you both... is there a way to detect the exact ram to replace? How i'll be able to identify ... Quote Link to comment
Kevek79 Posted September 2, 2019 Share Posted September 2, 2019 Channel and slot are recorded in the last line of the error message. So you can start by parsing the syslog for those errors and see if it is always the same module. But you should maybe also run memtest from the boot loader Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.