• SSD Standby/„Spin Down“ not working in 6.9/6.9.1


    TGP
    • Minor

    I have the problem that my Cache Pools stays active (green) permanently. It is not possible to send them in standby with the spin down function. This worked perfectly in 6.8.3, even with the timer.

    My Idle power consumption is higher since I have some more SATA and NVME SSDs all without standby. Is there a way to fix this?




    User Feedback

    Recommended Comments

    "Spin-down" of SSDs was removed from Unraid 6.9. See here.

     

    Quote

    - avoid sending spinup/spindown to non-rotational devices

     

    Link to comment

    Interesting, so there is no energy saving for SSDs anymore? Why is there even a Spin down Button for the cache pool?

    I have to figure out what else is broken, since my server needs about 10W more now (from 22 to 32 idle), which is more than just the SSDs. 

    Link to comment
    20 minutes ago, TGP said:

    Why is there even a Spin down Button for the cache pool?

     

    Because pools can contain spinning disks.

     

    Link to comment

    I have to reopen this for 6.9.1.

    Since there is trouble with S3 Status not being entered, because SSDs remain active. Is there any workaround to bring back the standby function for SSDs? It doesnt make sense to me that it was removed in the first place.

     

    @limetech

    Edited by TGP
    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.