Hello, last night my server was showing as unresponsive so I needed to do a hard shutdown and run the parity check. I noticed this in the logs partway through. I had some previous hardware issues with this machine in the past and replaced the motherboard a few times as a result, but it seems like the processor failing is the root-cause here?

Unraid Version: 6.12.2

Relevant log info, this repeats every second:

Jan 26 14:17:29 unNAS mcelog: CPU 0 on socket 0 has large number of corrected cache errors in Level-3 Instruction
Jan 26 14:17:29 unNAS mcelog: System operating correctly, but might lead to uncorrected cache errors soon
Jan 26 14:17:29 unNAS mcelog: Running trigger `cache-error-trigger' (reporter: yellow)
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 0 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 0 failed
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 1 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 2 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 3 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 4 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 5 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 6 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 7 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 8 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 9 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 10 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Offlining CPU 11 due to cache error threshold
Jan 26 14:17:29 unNAS mcelog: Trigger `cache-error-trigger' exited with status 1

Diagnostics attached.

unnas-diagnostics-20240126-1414.zip

Edited January 26, 20242 yr by ja444

13 hours ago, ja444 said:

but it seems like the processor failing is the root-cause here?

It does look like it.