MCE errors detected during Fix Common Problems scan - posting logs


Recommended Posts

Good morning everyone,

 

Recently my FCP posted this error: "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"

 

I am attaching the log file per the message. I'm not sure if I'm posting the correct log, as I'm not sure how to extract the mcelog stated in FCP but I did go into "Tools" and grab the Diagnostics log download.

Some things of note:

 

- Recently upgraded the hardware from a z97 and i7-5775c to a B560 and i7-10700 , but maintained the same GTX 970 and drives

- During upgrade, missing two SATA ports and waiting on SATA PCIe controller to add them back that were present via Unassigned Devices

- Recently been trying to spin up VMs, which has resulted in a total lockup of the system to the point where the PLUGINS and VM page become completely unresponsive and will not load, and it also stops Docker. It shows that containers are running, but when you try to connect to Plex, for example, it will not connect and cannot find the host. Even restarting the container does not change it. Rebooting the entire system fixes everything.

I am more than happy to provide anything else required. I am also ikyn#4444 on discord and am in the unraid "guild" on Discord.

tower-diagnostics-20210620-1047.zip

Link to comment

Certain combinations of hardware will cause an mce when initializing the cores.  This is happening to you and is quite safe to ignore.

 

For the VMs (especially if they are using passthrough), you may need to reconfigure everything on them due to the differing hardware.

Link to comment
5 minutes ago, Squid said:

Certain combinations of hardware will cause an mce when initializing the cores.  This is happening to you and is quite safe to ignore.

 

For the VMs (especially if they are using passthrough), you may need to reconfigure everything on them due to the differing hardware.

 

Thank you.

 

So it is normal for a mis-configured VM to render Docker useless until reboot? I will see if I can re-create the error and then pull logs before reboot and post them it that will help.

Edited by ikyn
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.