Increased energy consumption after update?

1st Official Post

    Increased energy consumption after update?


    Dear forum,


    I am in the process of installing a new NAS based on OMV 7. I have noticed that after the installation the energy consumption is as low as expected (about 5-7 watts)


    However, when I install the updates suggested by OMV, the energy consumption increases to about 10 watts.


    How can this be - since I don't use any other services or plugins and the BIOS settings are exactly the same?



    I have checked with PowerTop that the system can still reach C10 states - no change here either.


    I would be pleased if you could give me a tip on how I can continue to maintain the low energy consumption with updated packages.


    Here more details:

    Hardware:
    Board Odroid H4+ (N97 CPU) with 16GB Ram

    OS installed on eMMC 32 Gb

    1 NVME WD Blue SN580 1 TB
    1 Samsung SSD 840 PRO Series 512 GB

    1 NIC used (1 GB, Hardware could handle 2.5)

    System running headless, ie. disconnected HDMI & keyboard after installation


    Fresh installation, only enabled read/write cache on drives, installed openmediavault-flashmemory 7.0.1 via OMV-Extras


    With fresh installation:
    OMV_Report_FreshInstall.txt


    OMV reports 77 updates for my installation:


    After updates of packages via OMV Updates:


    OMV_Report_DriverUpdates.txt


    Checked energy states via PowerTop, still getting C10 states


    For comparison I have installed Ubuntu desktop on the system, which has also 4-5 Watts power consumption. As I'd like to run the system as basis for backups, paperless NGX, Immich and similar I try to keep energy consumption as low as possible.


    I have not tried, which of the 77 updates actually doubles energy consumption - so I hope someone might be able to help me with this.

  • votdev

    Approved the thread.

    Hi votdev,


    Thanks for your answer. Meanwhile I did some more analysis and installed listed packages one by one.


    The increase starts when I install the package linux-image-6.12.12+bpo-amd64


    One question: What do you mean with 'Things done by Odroid OS image (out of control of OMV)' - the BIOS?

    omv 7.7.7-1 (Sandworm) | 64 bit | Linux 6.12.22+bpo-amd64

    plugins :: omvextrasorg 7.0.2 | flashmemory 7.0.1 | immich | syncthing | autoshutdown

    • Official Post
    Quote from Figarion

    The increase starts when I install the package linux-image-6.12.12+bpo-amd64

    Disable backports in omv-extras

    from the command line:


    sudo apt-get install linux-image-amd64=6.1.133-1


    reboot


    remove the 6.12 kernel with the openmediavault-kernel plugin.


    Quote from Figarion

    What do you mean with 'Things done by Odroid OS image (out of control of OMV)' - the BIOS?

    He likely saw odroid and thought it was an arm device (most of their boards are).

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Thanks 1

    Hi ryecoaaron


    This was exactly the right hint - thanks a lot!


    I followed all your instructions and switched back to the older kernel - but consumption remained on elevated levels.

    But then I started over again: Installed OMV from scratch, but this time disabled backports in omv-extras before running updates (which updated to kernel 6.1.0-33-amd64.)

    Now energy consumption is back to 5 Watts (what is great)

    omv 7.7.7-1 (Sandworm) | 64 bit | Linux 6.12.22+bpo-amd64

    plugins :: omvextrasorg 7.0.2 | flashmemory 7.0.1 | immich | syncthing | autoshutdown

    I had the same problem and was a bit incredulous when I saw the increased consumption. Luckily I found your adive to disable backports and then to run the update. Should you always disable backports after a new installation? Do I have any disadvantages? In the GUi I cannot see if I have disabled or enabled backports ultimately.

    omv 7.7.5-1 sandworm | 64 bit |6.1.0-33-amd64

    plugins :: omvextrasorg 7.0.2 | flashmemory 7.0.1 | more to be added soon

    I am using new hardware and so I was surprised at the increased consumption after the update. I assumed that new kernels would be energy efficient.

    omv 7.7.5-1 sandworm | 64 bit |6.1.0-33-amd64

    plugins :: omvextrasorg 7.0.2 | flashmemory 7.0.1 | more to be added soon

    • Official Post
    Quote from fantozzi

    How do I know that actually I disabled backports in case one day I should forgotten it?

    Either click the disable backports button again or look at the output of apt clean (or apt-get update) or look to see if the backports repo file exists in /etc/apt/sources.list.d/

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Just a short note on deactivating the backport: To be fair, there is also a disadvantage to this procedure: With the older kernel version, the spindown of the HDD (refurbished Seagate IronWolf 12TB (ST12000VN0007)) unfortunately does not work correctly for me (even if the values have been configured to 5 minutes spindown, for example).
    This worked with linux-image-6.12.12+bpo-amd64 kernel from backports.

    omv 7.7.7-1 (Sandworm) | 64 bit | Linux 6.12.22+bpo-amd64

    plugins :: omvextrasorg 7.0.2 | flashmemory 7.0.1 | immich | syncthing | autoshutdown

    • Official Post
    Quote from Figarion

    With the older kernel version, the spindown of the HDD (refurbished Seagate IronWolf 12TB (ST12000VN0007)) unfortunately does not work correctly for me (even if the values have been configured to 5 minutes spindown, for example).

    Did you try the proxmox 6.2 or 6.5 or 6.8 or 6.11 kernel that you can install with the kernel plugin?

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Hi

    Yes, I tried proxmox 6.14.0-2-pve kernel which enabled spindown of the HDD.


    I'm still in the process of installing the NAS for my needs - so no final configuration yet. I found out, that you need to be careful with autoshutdown plugin: By default, HDD usage is monitored, which prevents the HDD to spin down.

    omv 7.7.7-1 (Sandworm) | 64 bit | Linux 6.12.22+bpo-amd64

    plugins :: omvextrasorg 7.0.2 | flashmemory 7.0.1 | immich | syncthing | autoshutdown

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login