• [6.9.0] HDD's no spin down after update


    xruchai
    • Solved Minor

    After updating to 6.9 Final the HDD's (sata) no longer go into standby (after 30 min), no spin down.

     

    I also set the delay to 15 minutes but the HDD's just don't go into standby.

    I have not changed any system settings before, only when I tried to solve the problem (uninstalled plugins etc.).

     

    Before the update, on 6.8.3, the spin down worked fine.

     

    I hope that you can help.

     

    • Like 2


    User Feedback

    Recommended Comments



    same here. 6.9.2.

    Disks spin down and a few seconds later wake up because of reading smart values. 

    had the rc before, there was no problem with spinning down

    Link to comment
    Share on other sites

    Researching for a fix I stumbled on this post.

     

    I am seeing the same behavior on 6.9.2.

    Link to comment
    Share on other sites

    Maybe some of you like to test my script:

    https://forums.unraid.net/topic/106508-force-spindown-script/

     

    It solved multiple issues for me:

    - some disks randomly spin up without any I/O change, which means Unraid does not know that they are spinning and by that they stay infinitely in IDLE_A state and never spin down.

    - some disks randomly return the STANDBY state although they are spinning. This is really crazy.

    - some disks randomly like to spindown twice to save even more power. I think the second spindown triggers the sata port standby state.

     

    Feedback is welcome!

    Link to comment
    Share on other sites

    "I have the same problem. Installed plugins

    Emby

    Heimdall

    Krusader

    Glances

    Papperless-ng

    Redis

     

    i have no VM´s.

    Link to comment
    Share on other sites

    I notice it is not 'all' of my hard drives - just 2 or sometimes 3, and it is always the same ones.

     

    Mainly it is the Toshiba 4.0TB MD04ACA400 that seems to spin up routinely.

     

    Link to comment
    Share on other sites

    @ChatNoir

    You posted a screenshot that your WD180EDFZ spins down. Now I'm on 6.9.2, too, but nothing works except of the original Ultrastar DC HC550 18TB which I'm using as my parity disk.

     

    18:38

    914883082_2021-06-2018_38_08.png.4d81634d4167f5345e84ff27a36cd5b6.png

     

    23:06

    205533099_2021-06-2023_06_03.png.b3b39e91a352ddb3f3de6c9ed1bc1ed5.png

     

    As you can see there was no activity on most of the disks, so why isn't unraid executing the spin down command?!

     

    Logs (yes, that's all):

    Jun 20 18:27:00 thoth root: Fix Common Problems Version 2021.05.03
    Jun 20 18:27:08 thoth root: Fix Common Problems: Warning: Syslog mirrored to flash ** Ignored
    Jun 20 19:07:04 thoth emhttpd: spinning down /dev/sdg

     

    If I click the spindown icon it creates a new entry in the logs. And it creates it as well if I execute the following command:

    /usr/local/sbin/emcmd cmdSpindown=disk2

     

    So the command itself works flawlessly, but it isn't executed by Unraid.

     

    @limetech What are the conditions before this command gets executed? Does Unraid check the power state, before going further? Because this disks have the powerstate "IDLE_B" all the time. Maybe you like to send me the source code, so I can investigate it?

    Link to comment
    Share on other sites
    59 minutes ago, mgutt said:

    @ChatNoir

    You posted a screenshot that your WD180EDFZ spins down. Now I'm on 6.9.2, too, but nothing works except of the original Ultrastar DC HC550 18TB which I'm using as my parity disk.

    I can confirm that all my HDDs do spin down and stay down properly (WD180EDFZ included).

    Here is an extract of the drives temperature from Grafana, it is an indirect but reliable visualization the the drives status. The spindown periods and spinup impulses are clearly visible. (7 days period for better visibility)

     

    A two day spinned down period is visible for one of my drive (between 23:30 on the 15th to 1:30 the 18th).

     

    image.thumb.png.88fd32181fce50402926ffaac577cb8f.png

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

    I can confirm that all my HDDs do spin down and stay down properly

    Are you using an HBA controller? I'm using onboard SATA ports.

     

    PS Re-booted in Safe Mode. Same behaviour. 😭

    Link to comment
    Share on other sites
    8 hours ago, mgutt said:

    Are you using an HBA controller? I'm using onboard SATA ports.

     

    Some of the drives are on my Dell H200 and others on the SATA ports of my X10SRA-F. Not sure which but I see no difference in behavior.

    Link to comment
    Share on other sites

    Hello,

     

    unfortunately I have the same problem that the HDDs with V6.9.2 do not perform spindown.

     

    This error can be observed especially when the function [[inputs.smart]] is activated in Telegraf. There is also read activity every few seconds on all HDDs and SSDs.

     

    grafik.png.1dcdf05cbb10dccce168074346ad379e.png

     

    It does not matter whether these are connected to the onboard SATA ports or to an HBA. If this function is deactivated, the HDDs go into spindown again.

     

    Greetings

    Edited by Gorosch
    Link to comment
    Share on other sites
    17 hours ago, Gorosch said:

    This error can be observed especially when the function [[inputs.smart]] is activated in Telegraf. There is also read activity every few seconds on all HDDs and SSDs.

     

    It does not matter whether these are connected to the onboard SATA ports or to an HBA. If this function is deactivated, the HDDs go into spindown again.

     

    Greetings

     

    Is this a standard feature of Unraid? How can I deactivate it? I don't have any other containers running and the disks still start up every few seconds.

    Link to comment
    Share on other sites

    Telegraf is a Docker that is required for Grafana. With this function Telegraf checks the S.M.A.R.T. HDD values.

    Link to comment
    Share on other sites

    Unraid 6.9.2

     

    Hey, i also have the problem that my disks are not spinning down. Even if i spin them down manual, they will spin up 5 sek later.
    Tryed turning off all vm and docker. Also looked with the Plugin File Activity but there is nothing reading or writing.

    I also do not have telegraf running.

    In the logs of the drive i see the SMART scan right after the spindown.
    Jul 16 14:26:27  emhttpd: read SMART /dev/sdc
    Jul 18 23:39:28  emhttpd: spinning down /dev/sdc
    Jul 18 23:39:31  emhttpd: read SMART /dev/sdc
    Jul 18 23:39:51  emhttpd: spinning down /dev/sdc
    Jul 18 23:39:54  emhttpd: read SMART /dev/sdc
    Jul 18 23:43:37  emhttpd: spinning down /dev/sdc
    Jul 18 23:43:45  emhttpd: read SMART /dev/sdc
    Jul 18 23:50:11  emhttpd: spinning down /dev/sdc
    Jul 18 23:50:28  emhttpd: read SMART /dev/sdc

     

    Maybe someone found a fix for that. Thanks :)

    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.