• [6.9.2] emhttpd: read SMART keeps disks spin up


    moguiyu
    • Urgent

    Dear all,

    I've been trying to figure out why 2 of my disks keep awake: (No docker/VM running, Tunable (md_write_method): is auto)

    1. Fall back to 6.9.1: noticed that the WebUI shows the disk already spin down, but in reality the disks are still spinning.
    2. Upgrade to 6.9.2/6.10.0-rc1, shows the spin up/down correctly, but disks keep reading SMART to awake disks, see pic 2.
    3. https://forums.unraid.net/topic/106508-advanced-disk-spindown/, I also tried this solution. it didi not help.

    my findings:

    1. 2 spin up disks are HGST 4tb, format in GPT, see pic 4.
    2. 2 spin down disks are Toshiba 1TB, format in MBR, see pic 3.

    this is all my findings, really struggled by this issue for a long time, not sure if Unraid is good solution any more.

    could anyone gives some suggestions how to troubleshoot? any other NAS solution to recommend?

     

    pic 1: 2 Hitachi disks keeps UP all the time.

    1572733799_Unraid0.thumb.png.806d2729ccb43c71f90854ec6b8b6512.png

     

    Pic 2: Disks keep reading SMART

    1735538516_Unraiddisk1.thumb.png.09d172828fb24610415fee9368502c51.png1172194611_Unraid3.thumb.png.6944f1b3147d50000b8ed5148fda46a6.png1627187315_Unraid4.thumb.png.095e124320edbb53a7d3fc0e062464ac.png




    User Feedback

    Recommended Comments

    31 minutes ago, SimonF said:

    Is something writing to disk 3 as it will spin up parity. suggest post diags.

    thank you for suggestions, I'm not very pro here. do you mean information like this?

     

    Sep 28 00:09:12 M17 emhttpd: spinning down /dev/sde
    Sep 28 00:09:50 M17 emhttpd: read SMART /dev/sde
    Sep 28 00:24:38 M17 emhttpd: spinning down /dev/sde
    Sep 28 00:25:16 M17 emhttpd: read SMART /dev/sde
    Sep 28 00:40:04 M17 emhttpd: spinning down /dev/sde
    Sep 28 00:40:42 M17 emhttpd: read SMART /dev/sde
    Sep 28 00:55:30 M17 emhttpd: spinning down /dev/sde
    Sep 28 00:56:08 M17 emhttpd: read SMART /dev/sde
    Sep 28 01:10:56 M17 emhttpd: spinning down /dev/sde
    Sep 28 01:11:34 M17 emhttpd: read SMART /dev/sde
    Sep 28 01:26:22 M17 emhttpd: spinning down /dev/sde
    Sep 28 01:27:00 M17 emhttpd: read SMART /dev/sde
    Sep 28 01:41:48 M17 emhttpd: spinning down /dev/sde
    Sep 28 01:42:26 M17 emhttpd: read SMART /dev/sde
    Sep 28 01:57:14 M17 emhttpd: spinning down /dev/sde
    Sep 28 01:57:52 M17 emhttpd: read SMART /dev/sde
    Sep 28 02:20:03 M17 emhttpd: spinning down /dev/sde
    Sep 28 02:23:28 M17 emhttpd: read SMART /dev/sde
    Sep 28 02:38:16 M17 emhttpd: spinning down /dev/sde
    Sep 28 02:38:53 M17 emhttpd: read SMART /dev/sde
    Sep 28 02:53:41 M17 emhttpd: spinning down /dev/sde
    Sep 28 02:54:19 M17 emhttpd: read SMART /dev/sde
    Sep 28 03:09:07 M17 emhttpd: spinning down /dev/sde
    Sep 28 03:09:45 M17 emhttpd: read SMART /dev/sde
    Sep 28 03:24:33 M17 emhttpd: spinning down /dev/sde
    Sep 28 03:25:11 M17 emhttpd: read SMART /dev/sde
    Sep 28 03:39:59 M17 emhttpd: spinning down /dev/sde
    Sep 28 03:40:37 M17 emhttpd: read SMART /dev/sde
    Sep 28 03:55:25 M17 emhttpd: spinning down /dev/sde
    Sep 28 03:56:03 M17 emhttpd: read SMART /dev/sde
    Sep 28 04:10:51 M17 emhttpd: spinning down /dev/sde
    Sep 28 04:11:29 M17 emhttpd: read SMART /dev/sde
    Sep 28 04:26:17 M17 emhttpd: spinning down /dev/sde
    Sep 28 04:26:55 M17 emhttpd: read SMART /dev/sde
    Sep 28 04:41:43 M17 emhttpd: spinning down /dev/sde
    Sep 28 04:42:21 M17 emhttpd: read SMART /dev/sde
    Sep 28 04:57:09 M17 emhttpd: spinning down /dev/sde
    Sep 28 04:57:47 M17 emhttpd: read SMART /dev/sde
    Sep 28 05:12:35 M17 emhttpd: spinning down /dev/sde
    Sep 28 05:13:13 M17 emhttpd: read SMART /dev/sde
    Sep 28 05:28:01 M17 emhttpd: spinning down /dev/sde
    Sep 28 05:28:39 M17 emhttpd: read SMART /dev/sde
    Sep 28 05:43:27 M17 emhttpd: spinning down /dev/sde
    Sep 28 05:44:05 M17 emhttpd: read SMART /dev/sde
    Sep 28 05:58:53 M17 emhttpd: spinning down /dev/sde
    Sep 28 05:59:31 M17 emhttpd: read SMART /dev/sde
    Sep 28 06:14:19 M17 emhttpd: spinning down /dev/sde
    Sep 28 06:14:57 M17 emhttpd: read SMART /dev/sde
    Sep 28 06:29:45 M17 emhttpd: spinning down /dev/sde
    Sep 28 06:30:23 M17 emhttpd: read SMART /dev/sde
    Sep 28 06:45:11 M17 emhttpd: spinning down /dev/sde
    Sep 28 06:45:49 M17 emhttpd: read SMART /dev/sde
    Sep 28 07:00:37 M17 emhttpd: spinning down /dev/sde
    Sep 28 07:01:15 M17 emhttpd: read SMART /dev/sde
    Sep 28 07:16:03 M17 emhttpd: spinning down /dev/sde
    Sep 28 07:16:41 M17 emhttpd: read SMART /dev/sde
    Sep 28 07:31:29 M17 emhttpd: spinning down /dev/sde
    Sep 28 07:32:07 M17 emhttpd: read SMART /dev/sde
    Sep 28 07:46:55 M17 emhttpd: spinning down /dev/sde
    Sep 28 07:47:33 M17 emhttpd: read SMART /dev/sde
    Sep 28 08:02:21 M17 emhttpd: spinning down /dev/sde
    Sep 28 08:02:59 M17 emhttpd: read SMART /dev/sde
    Sep 28 08:17:47 M17 emhttpd: spinning down /dev/sde
    Sep 28 08:18:25 M17 emhttpd: read SMART /dev/sde
    Sep 28 08:33:13 M17 emhttpd: spinning down /dev/sde
    Sep 28 08:33:51 M17 emhttpd: read SMART /dev/sde
    Sep 28 08:48:39 M17 emhttpd: spinning down /dev/sde
    Sep 28 08:49:17 M17 emhttpd: read SMART /dev/sde
    Sep 28 09:04:05 M17 emhttpd: spinning down /dev/sde
    Sep 28 09:04:43 M17 emhttpd: read SMART /dev/sde
    Sep 28 09:19:31 M17 emhttpd: spinning down /dev/sde
    Sep 28 09:20:09 M17 emhttpd: read SMART /dev/sde
    Sep 28 09:34:57 M17 emhttpd: spinning down /dev/sde
    Sep 28 09:35:35 M17 emhttpd: read SMART /dev/sde
    Sep 28 09:50:23 M17 emhttpd: spinning down /dev/sde
    Sep 28 09:51:01 M17 emhttpd: read SMART /dev/sde
    Sep 28 10:05:49 M17 emhttpd: spinning down /dev/sde
    Sep 28 10:06:27 M17 emhttpd: read SMART /dev/sde
    Sep 28 10:21:15 M17 emhttpd: spinning down /dev/sde
    Sep 28 10:21:53 M17 emhttpd: read SMART /dev/sde
    Sep 28 10:36:41 M17 emhttpd: spinning down /dev/sde
    Sep 28 10:37:19 M17 emhttpd: read SMART /dev/sde
    Sep 28 10:52:07 M17 emhttpd: spinning down /dev/sde
    Sep 28 10:52:45 M17 emhttpd: read SMART /dev/sde
    Sep 28 11:07:33 M17 emhttpd: spinning down /dev/sde
    Sep 28 11:08:11 M17 emhttpd: read SMART /dev/sde
    Sep 28 11:22:59 M17 emhttpd: spinning down /dev/sde
    Sep 28 11:23:37 M17 emhttpd: read SMART /dev/sde
    Sep 28 11:38:25 M17 emhttpd: spinning down /dev/sde
    Sep 28 11:39:03 M17 emhttpd: read SMART /dev/sde
    Sep 28 11:53:51 M17 emhttpd: spinning down /dev/sde
    Sep 28 11:54:29 M17 emhttpd: read SMART /dev/sde
    Sep 28 12:09:17 M17 emhttpd: spinning down /dev/sde
    Sep 28 12:09:55 M17 emhttpd: read SMART /dev/sde
    Sep 28 12:38:37 M17 emhttpd: spinning down /dev/sde
    Sep 28 12:40:31 M17 emhttpd: read SMART /dev/sde
    Sep 28 12:55:19 M17 emhttpd: spinning down /dev/sde
    Sep 28 12:55:56 M17 emhttpd: read SMART /dev/sde
    Sep 28 13:10:44 M17 emhttpd: spinning down /dev/sde
    Sep 28 13:11:19 M17 emhttpd: read SMART /dev/sde
    Sep 28 13:26:08 M17 emhttpd: spinning down /dev/sde
    Sep 28 13:26:44 M17 emhttpd: read SMART /dev/sde
    Sep 28 13:41:32 M17 emhttpd: spinning down /dev/sde
    Sep 28 13:42:09 M17 emhttpd: read SMART /dev/sde
    Sep 28 13:56:57 M17 emhttpd: spinning down /dev/sde
    Sep 28 13:57:35 M17 emhttpd: read SMART /dev/sde
    Sep 28 14:12:23 M17 emhttpd: spinning down /dev/sde
    Sep 28 14:13:01 M17 emhttpd: read SMART /dev/sde
    Sep 28 14:27:49 M17 emhttpd: spinning down /dev/sde
    Sep 28 14:28:27 M17 emhttpd: read SMART /dev/sde
    Sep 28 14:43:15 M17 emhttpd: spinning down /dev/sde
    Sep 28 14:43:53 M17 emhttpd: read SMART /dev/sde
    Sep 28 14:58:41 M17 emhttpd: spinning down /dev/sde
    Sep 28 14:59:19 M17 emhttpd: read SMART /dev/sde
    Sep 28 15:14:07 M17 emhttpd: spinning down /dev/sde
    Sep 28 15:14:45 M17 emhttpd: read SMART /dev/sde
    Sep 28 15:29:33 M17 emhttpd: spinning down /dev/sde
    Sep 28 15:30:11 M17 emhttpd: read SMART /dev/sde
    Sep 28 15:44:59 M17 emhttpd: spinning down /dev/sde
    Sep 28 15:45:37 M17 emhttpd: read SMART /dev/sde
    Sep 28 16:00:25 M17 emhttpd: spinning down /dev/sde
    Sep 28 16:01:03 M17 emhttpd: read SMART /dev/sde
    Sep 28 16:15:51 M17 emhttpd: spinning down /dev/sde
    Sep 28 16:16:29 M17 emhttpd: read SMART /dev/sde
    Sep 28 16:31:17 M17 emhttpd: spinning down /dev/sde
    Sep 28 16:31:55 M17 emhttpd: read SMART /dev/sde
    Sep 28 16:46:43 M17 emhttpd: spinning down /dev/sde
    Sep 28 16:47:21 M17 emhttpd: read SMART /dev/sde
    Sep 28 17:02:09 M17 emhttpd: spinning down /dev/sde
    Sep 28 17:02:47 M17 emhttpd: read SMART /dev/sde
    Sep 28 17:17:35 M17 emhttpd: spinning down /dev/sde
    Sep 28 17:18:13 M17 emhttpd: read SMART /dev/sde
    Sep 28 17:33:02 M17 emhttpd: spinning down /dev/sde
    Sep 28 17:33:39 M17 emhttpd: read SMART /dev/sde
    Sep 28 17:48:28 M17 emhttpd: spinning down /dev/sde
    Sep 28 17:49:05 M17 emhttpd: read SMART /dev/sde
    Sep 28 18:03:53 M17 emhttpd: spinning down /dev/sde
    Sep 28 18:04:31 M17 emhttpd: read SMART /dev/sde
    Sep 28 18:19:19 M17 emhttpd: spinning down /dev/sde
    Sep 28 18:19:57 M17 emhttpd: read SMART /dev/sde
    Sep 28 18:34:45 M17 emhttpd: spinning down /dev/sde
    Sep 28 18:35:23 M17 emhttpd: read SMART /dev/sde
    Sep 28 18:50:11 M17 emhttpd: spinning down /dev/sde
    Sep 28 18:50:49 M17 emhttpd: read SMART /dev/sde
    Sep 28 19:05:37 M17 emhttpd: spinning down /dev/sde
    Sep 28 19:06:15 M17 emhttpd: read SMART /dev/sde
    Sep 28 19:21:03 M17 emhttpd: spinning down /dev/sde
    Sep 28 19:21:41 M17 emhttpd: read SMART /dev/sde
    Sep 28 19:36:29 M17 emhttpd: spinning down /dev/sde
    Sep 28 19:37:07 M17 emhttpd: read SMART /dev/sde
    Sep 28 19:51:55 M17 emhttpd: spinning down /dev/sde
    Sep 28 19:52:33 M17 emhttpd: read SMART /dev/sde
    Sep 28 20:07:21 M17 emhttpd: spinning down /dev/sde
    Sep 28 20:07:59 M17 emhttpd: read SMART /dev/sde
    Sep 28 20:22:47 M17 emhttpd: spinning down /dev/sde
    Sep 28 20:23:25 M17 emhttpd: read SMART /dev/sde

    Link to comment

    I meet the same problem.

    But mine looks like different between HBA and MB sata port

     

     

    Edited by SeanOne
    Link to comment
    On 9/29/2021 at 12:04 PM, SeanOne said:

    I meet the same problem.

    But mine looks like different between HBA and MB sata port

     

     

    guess it is a bug, also exists in next version to be released. 

    Link to comment
    6 hours ago, moguiyu said:

    guess it is a bug, also exists in next version to be released. 

    Have you tried booting in safemode to see if drives spin down? i.e. no plugins or dockers?

    Link to comment
    22 hours ago, SimonF said:

    Have you tried booting in safemode to see if drives spin down? i.e. no plugins or dockers?

    Thank you for your suggestion. 

    I tried to boot in safe mode, and the behavior is exactly the same, 2 disks are keeping spinning, attached are diagnose result. 

    m17-diagnostics-20211003-1358.zip

    Link to comment

    This is what I have found too. In fact I believe I've narrowed it down to Plex. Unraid logs do not appear to show when a docker initiates a read on a disk so it always appears that following a spin down the SMART Read wakes the drive up. My understanding is that SMART reads are not attempted on idle drives so they do not spin up. But when they do spin up then a SMART read is initiated immediately.

    I've shut down Plex and now all of my drives are staying idle. 1 hour so far whereas before they would either not all spin down or spin back up after 10-15 minutes.

     

    With Plex running (Disk spin down time set to 1 hour):

    image.png.53b1d5ab29fbb8f0e107ef823bbb8ab9.png

     

    With Plex shut down (Disk spin down time set to 15 minutes for testing):

    image.png.500b59f12ff948579a81fe92818c21c4.png

    Link to comment

    I've turned off "Scan my library periodically" in Plex...let's see if that makes a difference.  I (like everyone else) am running Tdarr on my libraries at the moment so it may be a month or two before my disks spin down to test this for reals.  

    Link to comment
    On 10/15/2021 at 3:25 PM, Andiroo2 said:

    I've turned off "Scan my library periodically" in Plex...let's see if that makes a difference.  I (like everyone else) am running Tdarr on my libraries at the moment so it may be a month or two before my disks spin down to test this for reals.  

    I have turn off the scan long time ago. does not help. I even turn off all VM docker. still spin up. there must be bug.

    Link to comment

    Anyone found a solution to this?

    My server is a week old and all my disks also spin up with Read Smart, even the disks where there is no data or anything in use. But not as often as yours, can be 30min or up to 4 hours after spin down.

    Link to comment
    On 2/1/2022 at 10:50 PM, Dreeas said:

    Anyone found a solution to this?

    My server is a week old and all my disks also spin up with Read Smart, even the disks where there is no data or anything in use. But not as often as yours, can be 30min or up to 4 hours after spin down.

    nope, Im already check rack for hiding the disk noise... unfortunately.

    Link to comment

    This Problem ocured after exchanging drives.

     

    I had 4 Seagate 2.5" 5TB drives and replaced them with 2 TOSHIBA 18TB HDDs.

    With those Seagates, everything was fine.

     

    My Toshiba Parity drive remains shut down and the disk log does show a "read SMART" some days ago only.

    My Data Drive does spin up between 30min to 4hours after spin down for "READ SMART"

     

    Should not be a Firmware Issure since both drives differ only by 3 digits on their serial.

    Tried with Docker / VM on and off. No change.

     

     

    Link to comment
    16 minutes ago, GeeTee said:

    Any update on this? Same issue here.

    Have you investigated any causes for disk access. Read smart is called when unraid detects drives being spun up?

     

    Where is your docker or libvirt image if using them. Post diagnostics.

    Link to comment
    On 11/5/2022 at 11:59 AM, GeeTee said:

    Any update on this? Same issue here.

    Tried everything but still fail. Now waiting for Sinologist discount and switch to synology 

    Link to comment
    On 11/5/2022 at 12:17 PM, SimonF said:

    Have you investigated any causes for disk access. Read smart is called when unraid detects drives being spun up?

     

    Where is your docker or libvirt image if using them. Post diagnostics.

    I have all docker vm turned off. But it still spin up. And checked no file is active.

    Link to comment

    I have this same issue, put lots of effort into making sure that my spinning drives are only used for backups and media/video use and my disk logs are full of "read SMART" spin ups and spin downs 15 minutes later. No other access on the drives for hours.

     

    I have just turned off Plex to test that and will report back but looking at this thread, I'm not confident it will work.

    Link to comment
    1 hour ago, mgiggs said:

    I have this same issue, put lots of effort into making sure that my spinning drives are only used for backups and media/video use and my disk logs are full of "read SMART" spin ups and spin downs 15 minutes later. No other access on the drives for hours.

     

    I have just turned off Plex to test that and will report back but looking at this thread, I'm not confident it will work.

    Can confirm that turning off Plex does not resolve the issue.

     

    My diagnostics attached if anyone wants to look closely.

    unraid-diagnostics-20221109-0927.zip

    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.