Jump to content
  • [6.7.0-rc5] Dashboard CPU erroneously stuck at 100%


    jbartlett
    • Closed Annoyance

    I noticed this back on RC3 but since RC5 came out, I updated and waited to see if it happened again. Back on RC3, it happened to CPU 0 which was assigned to UNRAID. Now it's showing up with CPU 14 which is the last core assigned to a Win10 VM. Task manager in Win10 shows no activity. Remoting into the server, htop does not show 100% utilization. I see it updating at the same rate as the other CPUs.

     

    cpu1.png.2845e5cfe63257cdff6f80b45548650d.pngcpu3.png.0e755f2050efaff4db486bc4b4e60021.pngcpu2.png.7fdae589d75381960e314dfa6d358225.png

     

    nas-diagnostics-20190302-0815.zip



    User Feedback

    Recommended Comments



    It's likely a Marvell controller like mine. I quit using it with this 6.7 branch due to the flakiness.

    Share this comment


    Link to comment
    Share on other sites

    Have a similar problem with my WD black 500Gb. When i try to add it to the cache it gets stuck under the format process and pin one core at 100% until reboot. Seems WD black doesn't  play well with Unraid at this time.

    Share this comment


    Link to comment
    Share on other sites
    18 minutes ago, Pazoozo said:

    Have a similar problem with my WD black 500Gb. When i try to add it to the cache it gets stuck under the format process and pin one core at 100% until reboot. Seems WD black doesn't  play well with Unraid at this time.

    This thread is about a very old release candidate. Is that the version you have?

    Share this comment


    Link to comment
    Share on other sites

    I dont know, the graphs in web interface NEVER were correct for me, it always shjows SOMETHING, but its never nearly that what e.g. htop shows. Still in version 6.8. Since it was first introduced...

    Share this comment


    Link to comment
    Share on other sites
    2 hours ago, nuhll said:

    I dont know, the graphs in web interface NEVER were correct for me, it always shjows SOMETHING, but its never nearly that what e.g. htop shows. Still in version 6.8. Since it was first introduced...

    Because calculations are different.  htop doesn't show waiting for IO processes in its bar chart, but the dashboard does.

    Share this comment


    Link to comment
    Share on other sites

    What does that mean? If htop shows 1% and 5% and unraid always shows above 30 or 90% this cant be real?! For what its waiting when there is "nothing to do"

     

     

    io wait should be when CPU is waiting for e.g. harddrive? But when its usage is under 1mb/s, there cant be a iotwait 90%, or do i think wrong?

    Edited by nuhll

    Share this comment


    Link to comment
    Share on other sites
    17 minutes ago, nuhll said:

    For what its waiting when there is "nothing to do"

    I/O

    Share this comment


    Link to comment
    Share on other sites

    Yeah, ive edited as u posted, i know what it is (more or less). But i dont trust the dashboard, what ever it shows, it does not seem to reflect the CPU Usage. Why you want to display "waiting for IO" in a chart for CPU usage Oo?

    Edited by nuhll

    Share this comment


    Link to comment
    Share on other sites
    15 minutes ago, nuhll said:

    Why you want to display "waiting for IO" in a chart for CPU usage Oo?

    Because in this state the CPU can't do anything else.

    Share this comment


    Link to comment
    Share on other sites
    1 hour ago, nuhll said:

    Why you want to display "waiting for IO" in a chart for CPU usage Oo?

    It means the CPU is busy waiting for IO. This is the Linux preferred way to show CPU utilization.

    There is nothing wrong in the GUI

    Share this comment


    Link to comment
    Share on other sites
    17 minutes ago, nuhll said:

    So that means htop reports are wrong?

    No.   Just a different way of looking at it

    Share this comment


    Link to comment
    Share on other sites
    Just now, Squid said:

    No.   Just a different way of looking at it

    what about display it like htop and as addition display the iowait as % next to overall load?

    Share this comment


    Link to comment
    Share on other sites

    There is no reason to change the GUI.

    If you want to see IO wait state, use htop.

    Share this comment


    Link to comment
    Share on other sites

    In my case, the root cause was a WD Black NVMe 256GB that stopped responding due to the unit overheating. It wasn't an obvious cause for me because the drive was not utilized in any fashion and it was easier to leave it in there than take it out (until this happened).

    Share this comment


    Link to comment
    Share on other sites



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.