• [6.11.5] Hddtemp causing spun down drive to leave array


    PSteward
    • Closed

    I have been using hddtemp in a docker to read drive temperatures and have noticed that when I spin down drives and then let the hddtemp try to read it's temperature it knocks a drive out of the array (it will show up in assigned devices).

    I have replicated it this a few times, and to stop it from occuring now I check if the drive is on standby (with smartmontools) before using hddtemp to read the temp. Drive is a 10TB Seagate, but note it won't happen with all Seagate drives, just appears to be this one (so far).

     

    Steps to cause issue:

    Spin down drive via unRAID interface

    Use 'hddtemp -n /dev/sdX' on drive

    -- Drive shows still spun down on interface and appears with new sdX assignment in Unassigned Devices  --

     

    Steps to fix/restore:

    Stop array (if possible, if not reboot)

    New config

    Start array

     

    homeserver-diagnostics-20230523-1318.zip




    User Feedback

    Recommended Comments

    FYI: I'm not using his container. Why would this be considered a hddtemp issue and not an unRAID issue? I assume reading drive information should not cause spun down drives to break your unRAID array.

     

    Link to comment

    If you read temps with the included tools it doesn't cause any issues, suggesting the problem is with the 3rd party app.

    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.