Machine Check Events detected on your server

[IMDS]

Hi all,

 

I got a "Machine Check Events detected on your server" error in "Fix Common Problems" plugin, and it says that I should "install mcelog via the NerdPack plugin", but that plugin seems to be depreciated, and the "NerdTools" that came in it's place doesn't have "mcelog".

 

So I've downloaded diagnostics and in syslog.txt I found a few errors:

 

Quote

Apr  6 07:13:28 SVE kernel: ACPI BIOS Error (bug): Failure creating named object [\ADBG], AE_ALREADY_EXISTS (20220331/dswload2-326)
Apr  6 07:13:28 SVE kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)

 

Apr  6 07:13:28 SVE kernel: mce: [Hardware Error]: Machine check events logged

 

Apr  6 07:13:42 SVE  ntpd[1141]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

 

Any advice on how should I approach solving this problem?

 

I saw on the forum that "mce" errors can be ignored, but I just want to make sure.

 

These are my NAS specs:

CPU: Intel® Core™ i3-10105

MOBO: Gigabyte Technology Co., Ltd. B560M AORUS PRO

BIOS: F8

RAM: 32GB (2x16GB) 3600MHz

HDD: 3x 8TB WD Red

SDD: 2x 1TB MX500

NVMe: 1TB ADATA XPG SX8200 Pro

 

Thanks!

 

[itimpi]

6 minutes ago, IMDS said:

I saw on the forum that "mce" errors can be ignored, but I just want to make sure.

This tends to be true if they only occur during system startup.    More likely to be of concern if they start occurring later during normal running.

[IMDS]

Just now, itimpi said:

This tends to be true if they only occur during system startup.    More likely to be of concern if they start occurring later during normal running.

 

I did actually had to reboot my server due to a UPS started shutdown during a power outage and I guess that's when I got the error now that I think about it..

 

Okay, so if I ignore it now in "fix common problems", will it show up if it happens again?

Or should I leave it as is?

[IMDS]

I got the error again in normal operation 

 

Any idea on what it might be? Or how I can troubleshoot it?

I've attached the syslog file from diagnostics.

syslog.txt