• 6.9.2 RC2 "Read SMART" spins up the same 2 disks throughout the day


    cholzer
    • Closed

    The same 2 disks (sdb is the parity disk) seem to get spun up to read SMART (?) throughout the day.

    Time is AM, everyone was asleep during that time, no one accessed the NAS.
    There are no VM's and no dockers in Unraid, I use it as a "simple" NAS.

    Fusion-MPT 12GSAS SAS3008 PCI-Express in IT Mode

    The following plugins are installed:

    • CA User Scripts
    • Community Applications
    • Dynamix Cache Dirs
    • Dynamix Schedules
    • Dynamix SSD Trim
    • openVMTools_compiled
    • Recycle Bin
    • Tips and Tweaks
    • Unassigned Devices
    • Unassigned Devices Plus (Addon)
    Jan 12 03:02:13 NAS emhttpd: read SMART /dev/sde
    Jan 12 03:02:32 NAS emhttpd: read SMART /dev/sdd
    Jan 12 04:01:19 NAS emhttpd: spinning down /dev/sdd
    Jan 12 04:01:21 NAS emhttpd: spinning down /dev/sde
    Jan 12 04:07:29 NAS emhttpd: read SMART /dev/sde
    Jan 12 04:27:05 NAS emhttpd: read SMART /dev/sdd
    Jan 12 05:31:27 NAS emhttpd: spinning down /dev/sdd
    Jan 12 05:31:27 NAS emhttpd: spinning down /dev/sde

     




    User Feedback

    Recommended Comments



    I started off with the same. Read events would spin the disks and after 15min, they would spin down. After the troubleshooting shit I did, mentioned above in topic... even the 15min spindown no longer works. I decided to just give it up and wait for a version bump and hopefully a fix.

    Link to comment

    Same problem , every Hour Smart Spin Up, it was the Mover Config. I changed from every Hour to Daily and the Smart Spin Up stopps.

    • Like 1
    Link to comment

    I just found this thread dealing with the same thing. I noticed that all 8 of my disks were spun up all the time. If I manually spun them down, they'd all spin back up a few seconds later. Checking the log I'd see something like this:

     

    Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdh
    Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdg
    Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdd
    Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sde
    Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdb
    Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdf
    Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdc
    Mar 22 14:28:21 Jasmine emhttpd: spinning down /dev/sdi
    Mar 22 14:28:30 Jasmine emhttpd: read SMART /dev/sdb
    Mar 22 14:28:34 Jasmine emhttpd: read SMART /dev/sdf
    Mar 22 14:28:35 Jasmine emhttpd: read SMART /dev/sdg
    Mar 22 14:28:39 Jasmine emhttpd: read SMART /dev/sde
    Mar 22 14:28:39 Jasmine emhttpd: read SMART /dev/sdc
    Mar 22 14:28:55 Jasmine emhttpd: read SMART /dev/sdh
    Mar 22 14:28:55 Jasmine emhttpd: read SMART /dev/sdd
    Mar 22 14:28:55 Jasmine emhttpd: read SMART /dev/sdi

     

    I don't think it's related to Mover. Mover was on an hourly schedule but this happens consistently after I spin down the drives. I switched mover to a daily schedule and the same thing happens.

     

    I don't have any active streams or file handles to some of these drives, some of them are completely empty yet they're still spinning up.

     

    Some of these drives are plugged right into the motherboard's SATA ports, others are plugged into a cheapo Marvell 88SE9215 card. 

     

    It definitely used to spin drives down, so something has changed likely on my end that I've done but I can't see anything that would cause drives to be kept "awake". My spin down idle time is 30mins and even an hour after the SMART reads the drives are still spinning and nothing new is in the syslog. I suspect the SMART reads are a red herring and that's just happening when the drive spins up but what is causing them to spin up I simply don't know.

     

    EDIT: As soon as I posted this, I think I figured out the issue on my end was Turbowrite. It seems determined to spin up all my drives no matter how many are actually active so I've disabled it for now and it seems to have calmed down. I'll monitor on my end.

     

    jasmine-diagnostics-20210322-1538.zip

    Edited by Kushan
    Link to comment

    Same problem with one of five disks. 

     

    May 3 00:30:06 NAS emhttpd: read SMART /dev/sdb
    May 3 01:00:01 NAS emhttpd: spinning down /dev/sdb
    May 3 01:15:05 NAS emhttpd: read SMART /dev/sdb
    May 3 01:30:01 NAS emhttpd: spinning down /dev/sdb
    May 3 02:00:06 NAS emhttpd: read SMART /dev/sdb
    May 3 02:15:02 NAS emhttpd: spinning down /dev/sdb
    May 3 02:45:06 NAS emhttpd: read SMART /dev/sdb
    May 3 03:00:01 NAS emhttpd: spinning down /dev/sdb
    May 3 03:30:06 NAS emhttpd: read SMART /dev/sdb
    May 3 03:45:01 NAS emhttpd: spinning down /dev/sdb
    May 3 04:15:06 NAS emhttpd: read SMART /dev/sdb
    May 3 04:45:01 NAS emhttpd: spinning down /dev/sdb
    May 3 05:00:06 NAS emhttpd: read SMART /dev/sdb
    May 3 05:15:01 NAS emhttpd: spinning down /dev/sdb
    May 3 05:45:06 NAS emhttpd: read SMART /dev/sdb
    May 3 06:00:02 NAS emhttpd: spinning down /dev/sdb
    May 3 07:07:06 NAS emhttpd: read SMART /dev/sdb

     

    This is not normal. Its not the mover, the mover was disabled and turbowrite not active. 

    Link to comment
    On 3/11/2021 at 5:23 PM, Calidor said:

    Same problem , every Hour Smart Spin Up, it was the Mover Config. I changed from every Hour to Daily and the Smart Spin Up stopps.

    I was having the same issue.  Fifteen disks all spinning up immediately after spinning them down.  I would see the following in the logs:
    Jul 1 08:09:27 Tower emhttpd: spinning down /dev/sda

    Jul 1 08:09:49 Tower emhttpd: spinning down /dev/sdd

    Jul 1 08:09:51 Tower emhttpd: read SMART /dev/sdd

    Jul 1 09:09:28 Tower emhttpd: spinning down /dev/sda

    Jul 1 09:09:52 Tower emhttpd: spinning down /dev/sdd

    Jul 1 09:09:54 Tower emhttpd: read SMART /dev/sdd

    Jul 1 10:09:29 Tower emhttpd: spinning down /dev/sda

    Jul 1 10:09:55 Tower emhttpd: spinning down /dev/sdd

    Jul 1 10:09:57 Tower emhttpd: read SMART /dev/sdd

     

    I would also notice about 20-40Kb/s read rate on each drive.

     

    As soon as I disabled Turbo write, the issue stopped.  Read rate is now 0B/s, and drives stay spun down.

    Link to comment

    Jul 11 20:12:24 M17 emhttpd: read SMART /dev/sde
    Jul 11 20:27:00 M17 emhttpd: spinning down /dev/sde
    Jul 11 20:27:49 M17 emhttpd: read SMART /dev/sde
    Jul 11 20:42:25 M17 emhttpd: spinning down /dev/sde
    Jul 11 20:43:14 M17 emhttpd: read SMART /dev/sde
    Jul 11 20:57:50 M17 emhttpd: spinning down /dev/sde
    Jul 11 20:58:39 M17 emhttpd: read SMART /dev/sde
    Jul 11 21:13:15 M17 emhttpd: spinning down /dev/sde
    Jul 11 21:14:05 M17 emhttpd: read SMART /dev/sde
    Jul 11 21:28:41 M17 emhttpd: spinning down /dev/sde
    Jul 11 21:29:31 M17 emhttpd: read SMART /dev/sde
    Jul 11 21:44:07 M17 emhttpd: spinning down /dev/sde
    Jul 11 21:44:57 M17 emhttpd: read SMART /dev/sde
    Jul 11 21:59:33 M17 emhttpd: spinning down /dev/sde
    Jul 11 22:00:23 M17 emhttpd: read SMART /dev/sde
    Jul 11 22:14:59 M17 emhttpd: spinning down /dev/sde
    Jul 11 22:15:48 M17 emhttpd: read SMART /dev/sde
    Jul 11 22:30:24 M17 emhttpd: spinning down /dev/sde
    Jul 11 22:31:13 M17 emhttpd: read SMART /dev/sde
    Jul 11 22:45:49 M17 emhttpd: spinning down /dev/sde
    Jul 11 22:46:38 M17 emhttpd: read SMART /dev/sde
    Jul 11 23:01:14 M17 emhttpd: spinning down /dev/sde
    Jul 11 23:02:03 M17 emhttpd: read SMART /dev/sde
    Jul 11 23:16:39 M17 emhttpd: spinning down /dev/sde
    Jul 11 23:17:28 M17 emhttpd: read SMART /dev/sde
    Jul 11 23:32:04 M17 emhttpd: spinning down /dev/sde

     

    same problem here. the disk is format in GPT instead of MBR, this is the only difference compare to other sleeping disks

    Link to comment
    1 hour ago, moguiyu said:

    seems it is a bug, but no body cares now.

    Have you tried downgrade to 6.9.1?

    Link to comment

    Having the same issue on 4 of my drives.  It is def not the card or the cables because I tried replacing both and still the same issue.  Also just replaced the MB and processor and issue still persists.  It has to be software related and the unraid team really needs to look at this.

     

    Jul 20 06:34:56 SkyRAID emhttpd: spinning down /dev/sdl

    Jul 20 06:35:47 SkyRAID emhttpd: spinning down /dev/sdj

    Jul 20 06:35:47 SkyRAID emhttpd: spinning down /dev/sdf

    Jul 20 06:35:47 SkyRAID emhttpd: spinning down /dev/sdi

    Jul 20 07:00:17 SkyRAID emhttpd: read SMART /dev/sdj

    Jul 20 07:00:17 SkyRAID emhttpd: read SMART /dev/sdf

    Jul 20 07:00:17 SkyRAID emhttpd: read SMART /dev/sdi

    Jul 20 07:00:31 SkyRAID emhttpd: read SMART /dev/sdl

    Jul 20 07:31:39 SkyRAID emhttpd: spinning down /dev/sdj

    Jul 20 07:31:49 SkyRAID emhttpd: spinning down /dev/sdf

    Jul 20 07:31:49 SkyRAID emhttpd: spinning down /dev/sdl

    Jul 20 07:31:49 SkyRAID emhttpd: spinning down /dev/sdi

    Jul 20 08:00:12 SkyRAID emhttpd: read SMART /dev/sdj

    Jul 20 08:00:12 SkyRAID emhttpd: read SMART /dev/sdf

    Jul 20 08:00:12 SkyRAID emhttpd: read SMART /dev/sdi

    Jul 20 08:00:26 SkyRAID emhttpd: read SMART /dev/sdl

    Link to comment

    Guys, you should really open a new report in the correct subforum because mine is closed. 
    Hardly anyone from the dev team will read closed reports. :)

    Link to comment
    On 7/20/2021 at 3:20 PM, cholzer said:

    Guys, you should really open a new report in the correct subforum because mine is closed. 
    Hardly anyone from the dev team will read closed reports. :)

     

    I am facing the same issue...

     

    Has this already been done? Can't find any other forum post about this issue...

    Link to comment

    I don't think its the plex container.  I have a BTRFS pool that I use for camera recordings and Plex has not relationship with it and it experiences the spin up and spin down.  Weirdly, the pool is raid0 and it will spin up 1-3 drive while there are 5 of them in the pool.  So, it can't even be a read operation because it would need to spin up all of the drives for a read operation.

     

    image.png.6782c77f89662aba024b3539ecce9078.png

     

    image.png.5ecdc934cb2b0809787df57069bcc875.png

     

    image.png.37fa058139c4c25c642bb5e045c603b6.png

     

     

    Link to comment

    Well for me I disabled Plex for 4.5 hrs and no spin ups at all in that time. I re-enabled Plex and within 35 mins disks 1 and 2 plus my parity disk spun up. Disk 3 which had only a few videos on it spun up later on and disk 4 which had no videos remained spun-down.

     

    My point is that for me it appears to be Plex. Some have suggested in various threads the SMART reads are spinning up the disks which doesn't appear to be the case. I'm a novice with UNRAID mind you.

     

    I've now just set my disks to spin down after 5 hours so if Plex or anything else keeps the disks spun-up then so be it.

    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.