I don't want to just "acknowledge" an error in fix common problems like this without understanding it (somewhat)...

Here are the events as I recall,

yesterday afternoon I got an error, that I can no longer find, and I didn't have time to research properly, but a quick google was indicating that it could have been something with my ECC memory (detecting an error?) or L3 cache maybe, either way, I was going to have to post here, so I tried getting diagnostics to save, but my music was still streaming via Emby, so I didn't think about it any more until this afternoon...

..At this point the dashboard showed "log filesystem" at 100% so something was writing there, and I got an email sent from "Console and webGui login account" (which is either something built in, or something I set up a few years ago and don't remember) that read as follows..

error: error writing to /var/log/libvirt/libvirtd.log.1: No space left on device
error: error copying /var/log/libvirt/libvirtd.log to /var/log/libvirt/libvirtd.log.1: No space left on device

but after a reboot that is sitting at 3% which seems more reasonable.. I however don't know how to read the diagnostics...

The relevant bits (based on nothing other than the example shown after clicking on the error in "fix common problems" tool)...

Sep 15 19:14:50 Ezra kernel: mce: [Hardware Error]: Machine check events logged

Sep 15 19:14:50 Ezra kernel: [Hardware Error]: Corrected error, no action required.

Sep 15 19:14:50 Ezra kernel: [Hardware Error]: CPU:0 (19:21:2) MC18_STATUS[-|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0x9c2040000000011b

Sep 15 19:14:50 Ezra kernel: [Hardware Error]: Error Addr: 0x000000013f2c72c0

Sep 15 19:14:50 Ezra kernel: [Hardware Error]: IPID: 0x0000009600150f00, Syndrome: 0x455c00040a800d00

Sep 15 19:14:50 Ezra kernel: [Hardware Error]: Unified Memory Controller Ext. Error Code: 0

Sep 15 19:14:50 Ezra kernel: EDAC MC0: 1 CE Cannot decode normalized address on mc#0csrow#0channel#1 (csrow:0 channel:1 page:0x0 offset:0x0 grain:64 syndrome:0x4)

Sep 15 19:14:50 Ezra kernel: [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD

Sep 15 19:15:01 Ezra unassigned.devices: Remote Share '//192.168.111.99/media_backup' is not set to auto mount.

Sep 15 19:15:01 Ezra unassigned.devices: Remote Share '//192.168.111.99/Z' is not set to auto mount.

Sep 15 19:15:01 Ezra unassigned.devices: Remote Share '//TRUENAS/idiot' is not set to auto mount.

Sep 15 19:15:01 Ezra unassigned.devices: Remote Share '//TRUENAS/jane' is not set to auto mount.

Sep 15 19:16:19 Ezra nmbd[2708]: [2025/09/15 19:16:19.943080, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)

Sep 15 19:16:19 Ezra nmbd[2708]: process_local_master_announce: Server HOMEASSISTANT at IP 192.168.111.158 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.

Sep 15 19:19:20 Ezra nmbd[2708]: [2025/09/15 19:19:20.068259, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)

Sep 15 19:19:20 Ezra nmbd[2708]: process_local_master_announce: Server HOMEASSISTANT at IP 192.168.111.158 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.

Sep 15 19:23:01 Ezra root: Fix Common Problems Version 2025.08.07

Sep 15 19:23:06 Ezra root: Fix Common Problems: Error: Machine Check Events detected on your server

Sep 15 19:23:06 Ezra root: mcelog: ERROR: AMD Processor family 25: mcelog does not support this processor. Please use the edac_mce_amd module instead.

Sep 15 19:23:06 Ezra root: CPU is unsupported

I am sure there are many things that I can improve, and all help is welcomed, but specifically I need to know about this error so I can either move on or dig in 🤣

thanks in advance

-G

ezra-diagnostics-20250915-1933.zip

Looks like an ECC corrected error; you can ignore it if it was a one time thing, if it keeps happening, the affected DIMM should be replaced.

I was worried that becuase I kept seeing an L3 error it was a CPU problem..

I will try to get the time to take it down and swap some memory around this weekend.

What diagnostic approach would you take? I have 4 matching ram sticks, I figure 2 and 2 to test...

I just need to know what software/process to get something repeatable..

Thanks once again for your help.

5 hours ago, Garbonzo said:

I kept seeing an L3 error it was a CPU problem.

Could also be a CPU cache memory error.

I am attaching new diagnostics since its been running another week or so now, but I just don't know what to look for.

I have an older Ryzen I can put back in (I upgraded an old R7 1700 with an R9 5900x about 6 months back.
Prior to that I had used the same MB/Memory for 2+ yrs. So the processor sticks out as the most likely to me...

Any advice helpful and welcome.

-G

ezra-diagnostics-20250923-0935.zip

You can retest with one DIMM at a time; if you get the same errors with two different DIMMs, it basically rules out the RAM, or retest the old CPU. Start with whichever is easy.

13 hours ago, JorgeB said:

Start with whichever is easy

I have to pull the cooler to get to the ram in this build

...but I will report the results back when I can..

Thanks again,

-g