• 6.10.0 RC8 "Cache" nvme temperature wrong


    lucidnx
    • Closed Minor

    Hello! Today I'v got alert that one of my Pool nvme ssd's went up to 84°C. after short research I have found that it is wrong..

     

    update: after reboot it went back to normal readings.

    Screenshot_20220514-195159_Firefox.jpg

    Screenshot_20220514-195209_Firefox.jpg

    hv01-diagnostics-20220514-1953.zip




    User Feedback

    Recommended Comments

    16 minutes ago, lucidnx said:

    Here it stayed at 84 degrees until reboot.

    Because of have the GUI updating at the default 1800secs, that's 30 minutes, change that to a more reasonable 60 or 120secs.

     

    Settings -> Disk Settings -> Poll Attributes.

    • Thanks 1
    Link to comment

    Oh really... I thought it is a lot faster... Can 60s polling rate cause issue or why is there such a nonsense value?

    Link to comment
    2 minutes ago, lucidnx said:

    I mean, why is default value that high?

    Yes, I agree, default should be much lower.

    Link to comment

    Reading smart info from a disk may interfere with its normal operation.

    The default value of 30 min. is to ensure minimum impact is expected, changing the interval to a lower value is up to user choice and care should be taken that normal disk operations are not impacted.

     

    Link to comment
    1 minute ago, bonienl said:

    Reading smart info from a disk may interfere with its normal operation.

    It might, though I never found it, still I would prefer to risk that that having disks overheating due to for example a failed fan and being notified half an hour later, when it already might be too late, disks in a close space like in a 5in3 cage or similar can overheat very quick if a fan stops or gets blocked.

    Link to comment

    Well, from enterprise solutions, it's reading temps almost realtime and those machines works 24/7 for years.. I have never seen issue with that..

    Link to comment

    Default poll interval dates back a number of years.  It was chosen to minimize video "glitching" in lower-performance servers - Atom processors, 4G or less of RAM, older hard drives with small caches.

     

    These days I think something like 30 seconds would be better.  Then if someone posts that they are seeing video glitches every 30 sec we can suggest raising the value.

    • Like 1
    • Thanks 2
    Link to comment

    @limetech Just wondering, would it make sense if you could please update the default setting to 30 seconds in your next Unraid release and then if users wanted a higher value then they can increase the value. In my case i wasn't aware of the default polling interval being so high and i would guess that many others dont know about this either. I have just gone ahead and changed this to 30 sec now.

    Link to comment
    17 hours ago, Titan84 said:

    @limetech Just wondering, would it make sense if you could please update the default setting to 30 seconds in your next Unraid release and then if users wanted a higher value then they can increase the value. In my case i wasn't aware of the default polling interval being so high and i would guess that many others dont know about this either. I have just gone ahead and changed this to 30 sec now.

    ok

    • Thanks 1
    Link to comment

    I have two Samsung 980 500GB with the same firmware in both 1B4QFXO7 but only one of them is constantly giving the warnings. The 2nd one no warnings at all.

     

    Link to comment


    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.