Jump to content

berben

Members
  • Posts

    10
  • Joined

  • Last visited

Posts posted by berben

  1. 8 minutes ago, itimpi said:

     

     

    Make sure you are not overclocking the RAM (a XMP profile IS an overclock).   You can also try with less RAM sticks installed as sometimes it is the memory controller that cannot handle the number of installed RAM sticks without issues.   Sometimes the CPU has a max RAM speed it can handle as well so check the manual for that.

     

    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.

  2. 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.

  3. On 3/12/2023 at 10:40 PM, mgutt said:

    Test different USB Ports and Ethernet ports if your board has multiple of them. For example the C246M-WU4 reaches only C9 if a specific ethernet and usb port is used:

    https://forums.unraid.net/topic/119197-gigabyte-c246m-wu4-komme-nicht-über-c2-state-hinaus/page/4/#comment-1232565

     

    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.

  4. 5 hours ago, mgutt said:

    This is pretty usual. VMs produce load. Load stops the CPU from going to sleep. But you could try to give the vm only the very first CPU core #0 and then check again. Another variant could be to isolate the last cpu core and use this exclusively for HA. Then reduce the maximum frequency for this single core:

     

    Lets say your last core is #7 as you are having an 8-core CPU. Then do this to limit this core to 2 Ghz:

     

    echo "2000000" > /sys/devices/system/cpu/cpu7/cpufreq/scaling_max_freq

     

    Obtain all frequencies of all cores:

     

    cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq

     

    Note: This is reset after each reboot. So you have to add it to a script or the /boot/config/go File to make it permanent.

     

    Obtain minimum and maximum of your CPU:

     

    cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_*_freq

     

     

    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.

  5. 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.

     

     

    powertop_device_stats.png

    aspm_status.png

    powertop_idle_stats.png

    powertop_tunables.png

×
×
  • Create New...