berben

Ok, I think I can safely say that one of the two RAM sticks is at fault here. I tried swapping RAM slots and no matter what one of the sticks is causing errors. No XMP, no overclock. I'll send it to RMA and run the PC with only one stick for now. Thanks once again for the tips.

I took out one of the sticks and there seems to be no errors this time. I suspect the one stick that I took out to be faulty because the system was running fine for a couple of months and nothing has changed in the setup during this period. I'm not overclocking explicitely but I think XMP profile was selected. After this second test I'll put back the second stick and disable the XMP profile.

Looks like you were right. Memtest started to throw errorrs after a couple of seconds. Now I'll try to figure our if this is RAM indeed (hopefully not CPU) and RMA it. Thanks a lot for the tips!

Thanks for the explanation. That would be weird because the machine is almost brand new but of course anything could happen. I'm creating USB with the newest memtest and I'll leave it running for a couple of hours. SSD drive is not new though, it's a couple of years old drive.

Do you mean RAM test? The one I run from boot menu? Do you think this might be RAM related?

Attaching the diagnostics zip. nas-diagnostics-20231012-2141.zip

Hi, I encountered an issue with docker apps. They just randomly crash and are not responding. It happened a couple of times but reboot fixes it for a while (a couple of days). Today it happened again but this time I had a little time to do some log browsing. I've found a couple of weird errors showing up in logs. Firstly, system log shows something like this (new entry every couple of seconds): Oct 12 18:03:45 NAS kernel: pcieport 0000:00:1c.3: AER: Corrected error received: 0000:02:00.0 I looked up in devices manager and it points to this device: [8086:7abb] 00:1c.3 PCI bridge: Intel Corporation Device 7abb (rev 11) Also, /var/log/docker.log is spamed with: containerd: creating temp mount location: mkdir /var/lib/docker/containerd/daemon/tmpmounts: input/output error time="2023-10-12T07:05:09+02:00" level=warning msg="containerd config version `1` has been deprecated and will be removed in conta inerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header" My cache disk is SATA SSD and I don't have any external devices connected directly to PCI slots. Everything is fine again after reboot, except the "AER" error still being logged. This PC was running fine for about 6 months, it started to be problematic a couple of days ago. Any help would be appreciated.

It didn't help at all. I tried both USB 2.0 and 3.0 ports. This MB has only one ethernet port. Do you have any experience with this Sonoff USB stick? I think I saw this device on one of your screenshots.

Thank you for tips. Unfortunately it didn't help at all, I tried both approaches - CPU won't reach any C state. I tried replacing Home Assistant VM with docker container. I set up Home Assistant, Mosquito and Zigbee2MQTT containers and the story is almost the same. The is no CPU overhead that VM had but only C2 is reachable and there is no difference in power usage (maybe ~1W). I think Sonoff Zigbee USB stick is the culprit here. I can set up multiple different containers but only Zigbee2MQTT (it uses Sonoff stick directly) blocks CPU from entering better power states.

Greetings, first of all thanks for all the tips, I already managed to lower power consumption of my rig a bit. I have a couple of questions though, maybe someone will be able to help me. I built a new PC to host unraid on, these are the specs: MB: Asus PRIME H610M-R D4 CPU: i3-12100 HDD: 2x Seagate Ironwolf 4TB SSD: Samsung 850 EVO 500GB (SATA) PSU: Corsair RM550x (2018 revision sadly) When running unRAID and 2 containers (Photoprism and nextcloud) I measured about 20W power usage. CPU is reaching C8 I believe. Is this good result? I thought I could run a little lower. I have disks set up to spin down but they never do that, I don't know why. Main issue is when I start VM with home assistant and when I attach Sonoff Zigbee 3.0 USB stick. Power usage is now 30W and CPU never reaches any C state. I tried to apply all the tweaks but nothing seems to be helping. I'm attaching a couple of screenshots.