June 13, 20179 yr These popped up in the log, anything to be concerned about....never seen this on any previous version No ill effects noticed everything seems to be working https://pastebin.com/xgZEjuwq Edited June 13, 20179 yr by mikefallen fix link
June 14, 20179 yr Author 2 hours ago, Squid said: You should post the full diagnostics attached tower-diagnostics-20170613-2158.zip
June 14, 20179 yr You guys should install the NerdPack plugin (and then set it to install mcelog). Then reboot. When FCP finds another mce error, it will log more details. MCE errors are hardware errors. And should not be ignored.
June 14, 20179 yr https://unix.stackexchange.com/questions/117449/random-restarts-caused-by-a-machine-check-exception
June 14, 20179 yr they are suggesting faulty MB/CPU or RAM...my MB is ASROCK J4205-ITX (CPU integrated) did test also with 2nd brand new MB same type and the same problem, memtest86+ passed multiple times. It has to be an Linux/Kernel issue or 2nd tip: Even more fortunately, in Debian and Ubuntu this can be done as easily as: sudo apt-get install intel-microcode How to do that in unRAID? Edited June 14, 20179 yr by killeriq
June 14, 20179 yr Just now, killeriq said: they are suggesting faulty MB/CPU or RAM...my MB is ASROCK J4205-ITX (CPU integrated) did test also with 2nd brand new MB same type and the same problem, memtest86+ passed multiple times. It has to be an Linux/Kernel issue Very well could be a kernel issue, but just because memtest86+ passes does not imply your memory is good. memtest only tests the data path between CPU/RAM. There are other data paths implemented by the memory controller, for example PCI/RAM (DMA access). If you suspect bad RAM the easiest way to test is to yank out a stick. If it still fails, put it back and yank out the other stick. Repeat until you're satisfied issue isn't with RAM. Anyway we're about to release -rc3 which uses kernel 4.11.5. You can examine the change logs to see if there's anything MCE related: https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.11.4 https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.11.5
June 14, 20179 yr 11 minutes ago, killeriq said: How to do that in unRAID? Generally newer Intel processors don't have microcode updates. Is your CPU listed here? https://downloadcenter.intel.com/download/26798/Linux-Processor-Microcode-Data-File
June 15, 20179 yr Author Model: Custom M/B: Supermicro - H8DM8-2 CPU: 2 x Six-Core AMD Opteron™ 2431 @ 2400 HVM: Enabled IOMMU: Disabled Cache: 768 kB, 3072 kB, 6144 kB Memory: 32 GB (max. installable capacity 32 GB)* I'm leaning towards kernel issue as well, because i have never seen these errors on any other version of unraid....just seems too coincidental
June 15, 20179 yr installed rc3 today and seems there is no red error after reboot maybe a final kernel solution? Will let u know after few hours of running EDIT: alert came up after 5min, will post full log later Edited June 15, 20179 yr by killeriq
June 19, 20179 yr 23 minutes ago, killeriq said: rc4 the same Have you checked for a motherboard bios update?
June 19, 20179 yr 4 minutes ago, limetech said: Have you checked for a motherboard bios update? yeah i have 1.30 , nothing new since http://www.asrock.com/mb/Intel/J4205-ITX/index.us.asp?cat=Download&os=BIOS
Archived
This topic is now archived and is closed to further replies.