Monitoring: missing disk IO statistic values since update 4.19.0-0.bpo.1

  • https://github.com/collectd/collectd/issues/2951 -> Could that be the problem?


    Is there someone who has the same issue?


    BR/FJ

    Yepp, same here.
    No more Disk I/O since second half of January 19. Neither for raid nor nvme drive.
    Only NaN Values arr being displayed and I today I got a monit alert: Does not exists collectd, restart, process is not running


    B.R.
    M



    Edit – just a quick note:
    To verify FJW's hint I tried downgrading to kernel 4.18 (backport) - the result are as expected: Disk I/O starts to work again but since VirtualBoxes and Plex won't start anymore this doesn't even count as a workaround.
    Seems like I'll have to wait for an updated collectd package.

  • Hi !


    Same here since 4.19 too... :(

    Lian Li PC-V354 (with Be Quiet! Silent Wings 3 fans)
    ASRock Rack x470D4U | AMD Ryzen 5 3600 | Crucial 16GB DDR4 2666MHz ECC | Intel x550T2 10Gb NIC

    1 x ADATA 8200 Pro 256MB NVMe for System
    6 x Western Digital 10To HDD in RAID 6 for Datas
    1 x Western Digital 2To HDD for Backups/Downloads

    Powered by OMV v5.6.26 & Linux kernel 5.10.x

  • Plugin diskstats 4.0.4-1 re-installation does not help.
    (graph attached)



    any hints on how to fix it?

    Roll back to kernel 4.18 or wait for a required upstream fix to collectd (collectd is not maintained by OMV).

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • Any update to this?


    5.8 is on Buster and collectd themselves put out 5.9 in June, but we're still on 5.7?

    OMV 4.x - ASUS P10S-X - Xeon E3-1220 v6 - 64GB ECC Crucial DDR4 2400MHz - Syba SI-PEX40064 SATA3 Card - 60GB Kingston SSD Boot Drive - 3x WD RED 4TB

    • Official Post

    Any update to this?


    5.8 is on Buster and collectd themselves put out 5.9 in June, but we're still on 5.7?

    OMV uses whatever package is in Debian's repos. Updating to a newer package may break something. Backup your system and try install the 5.8 package from buster if you need this.

    omv 8.0.6-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.2 | compose 8.1.2 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.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!

  • I managed to make it work here:


    Follow the steps here (https://collectd.org/wiki/index.php/First_steps) to compile a newer version of collectd, but compile in /root/tmp so it wont get erased. I used the collectd-5.8.1.tar.bz2 package here.


    Then rename your current and defective disk.so plugin: mv /usr/lib/collectd/disk.so /usr/lib/collectd/disk.so.old.


    At last copy the new compiled version of the plugin: cp /root/tmp/collectd-5.8.1/.libs/disk.so /usr/lib/collectd/



    Restart the collectd service: systemctl restart collectd.



    Hope it helps.

  • I upgraded these two packages from buster. No problems.


    collectd 5.8.1-1.3


    collectd-core 5.8.1-1.3

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • I upgraded these two packages from buster. No problems.


    collectd 5.8.1-1.3


    collectd-core 5.8.1-1.3

    Hye, how did you do that? With mgruber4 instructions?


    Thanks

    Linux openmediavault 4.15.0-0.bpo.2-amd64 #1 SMP Debian 4.15.11-1~bpo9+1 (2018-04-07) x86_64 GNU/Linux
    hp proliant N40L 8GB ram on 64GB flashAMD Turion(tm) II Neo N54L Dual-Core Processor
    More abut me: http://www.etiennebretteville.com

  • Hye, how did you do that? With mgruber4 instructions?
    Thanks

    I downloaded the packages from Debian buster and installed them with dpkg. Simple.


    https://packages.debian.org/buster/collectd


    https://packages.debian.org/buster/collectd-core

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

  • I upgraded these two packages from buster. No problems.


    collectd 5.8.1-1.3


    collectd-core 5.8.1-1.3

    have you ever resolved the problem? i have tried upgrade collectd to 5.8.1, but there still no data in the graph.


    I got the reason.
    I just use the new collectd config file, so disk.conf has been changed. After reinstall openmediavault and openmediavault-diskstats, all works.

  • Hello, same here.


    I'm using OMV on HP Microserver N54L (AMD Turion)


    May be flashmemory plugin cause the issue?

    • Official Post

    Is this the wrong forum or can i contact the author of the plugin or is he active in this forum?

    The author of that plugin is the author of OMV itself. votdev is active on the forum. I don't use the plugin myself so i can't help you.

    omv 8.0.6-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.2 | compose 8.1.2 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.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!

Participate now!

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