• Disks Spinning Up (For no reason).


    XtremeOwnage
    • Annoyance

    This likely is not related to 6.12, however, I have an issue where my disks are being spun up around every hour for no reason.

    Hardware: Dell R730XD. HBA 330 mini.

     

    May 18 14:42:49 Tower emhttpd: read SMART /dev/sdk
    May 18 14:57:38 Tower emhttpd: spinning down /dev/sdk
    May 18 16:07:46 Tower emhttpd: read SMART /dev/sdk
    May 18 16:22:36 Tower emhttpd: spinning down /dev/sdk
    May 18 17:32:46 Tower emhttpd: read SMART /dev/sdk
    May 18 17:47:36 Tower emhttpd: spinning down /dev/sdk
    May 18 18:57:41 Tower emhttpd: read SMART /dev/sdk
    May 18 19:12:31 Tower emhttpd: spinning down /dev/sdk
    May 18 20:22:36 Tower emhttpd: read SMART /dev/sdk
    May 18 20:37:26 Tower emhttpd: spinning down /dev/sdk
    May 18 21:47:32 Tower emhttpd: read SMART /dev/sdk
    May 18 22:02:22 Tower emhttpd: spinning down /dev/sdk
    May 18 23:12:26 Tower emhttpd: read SMART /dev/sdk
    May 18 23:27:15 Tower emhttpd: spinning down /dev/sdk
    May 19 00:37:20 Tower emhttpd: read SMART /dev/sdk
    May 19 00:52:10 Tower emhttpd: spinning down /dev/sdk
    May 19 02:02:12 Tower emhttpd: read SMART /dev/sdk
    May 19 02:17:02 Tower emhttpd: spinning down /dev/sdk
    May 19 03:27:05 Tower emhttpd: read SMART /dev/sdk
    May 19 03:41:55 Tower emhttpd: spinning down /dev/sdk
    May 19 04:52:01 Tower emhttpd: read SMART /dev/sdk
    May 19 05:06:50 Tower emhttpd: spinning down /dev/sdk
    May 19 06:16:55 Tower emhttpd: read SMART /dev/sdk
    May 19 06:31:44 Tower emhttpd: spinning down /dev/sdk
    May 19 07:41:48 Tower emhttpd: read SMART /dev/sdk
    May 19 07:56:37 Tower emhttpd: spinning down /dev/sdk



    I use /dev/sdk in this example, for the simple reason- it has no file system. It is literally just an empty drive which happens to be inserted into unraid. 

     

    1. This drive has NO data.
    2. This drive has NO filesystem.
    3. It has no mounts.
    4. There are no docker containers with access to this device. Everything is isolated to /mnt/user or /mnt/cache shares.
    5. There are no VMs running.

     

    But, it spins up pretty consistently, every 50 minutes after it last spun down.

    I have....

    1. Updated the firmware / bios for my HBA, BIOS, etc. No Change.

    2. Removed most of the plugins I thought could be contributing to this. So, Folder Caching, etc.

    3. Trim schedule is only once a week. Mover schedule wouldn't apply to this disk.

    There is, nothing in syslog to assist, other than viewing the timing of the other drives randomly spinning up as well.

     

    May 19 04:50:08 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="1287" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
    May 19 04:52:01 Tower emhttpd: read SMART /dev/sdk
    May 19 05:04:10 Tower emhttpd: read SMART /dev/sdm
    May 19 05:04:21 Tower emhttpd: read SMART /dev/sdn
    May 19 05:06:50 Tower emhttpd: spinning down /dev/sdk
    May 19 05:18:59 Tower emhttpd: spinning down /dev/sdm
    May 19 05:19:12 Tower emhttpd: spinning down /dev/sdn
    May 19 05:40:29 Tower emhttpd: read SMART /dev/sde
    May 19 05:55:19 Tower emhttpd: spinning down /dev/sde
    May 19 06:00:01 Tower root: mover: started
    May 19 06:00:01 Tower root: mover: finished
    May 19 06:16:55 Tower emhttpd: read SMART /dev/sdk
    May 19 06:29:02 Tower emhttpd: read SMART /dev/sdm
    May 19 06:29:14 Tower emhttpd: read SMART /dev/sdn
    May 19 06:31:44 Tower emhttpd: spinning down /dev/sdk
    May 19 06:43:52 Tower emhttpd: spinning down /dev/sdm
    May 19 06:44:06 Tower emhttpd: spinning down /dev/sdn
    May 19 07:20:11 Tower emhttpd: spinning down /dev/sde
    May 19 07:41:48 Tower emhttpd: read SMART /dev/sdk
    May 19 07:53:57 Tower emhttpd: read SMART /dev/sdm
    May 19 07:54:09 Tower emhttpd: read SMART /dev/sdn
    May 19 07:56:37 Tower emhttpd: spinning down /dev/sdk
    May 19 08:00:01 Tower root: mover: started
    May 19 08:00:01 Tower root: mover: finished
    May 19 08:08:47 Tower emhttpd: spinning down /dev/sdm
    May 19 08:08:59 Tower emhttpd: spinning down /dev/sdn
    May 19 08:30:17 Tower emhttpd: read SMART /dev/sde
    May 19 08:45:08 Tower emhttpd: spinning down /dev/sde

     

     

    For lsblk- note- no partitions. 

     

    image.thumb.png.d13ccaa7cf3a980ce668aba4a51d9a56.png

     

    I would have uploaded the diagnostics.zip, but, it appears to have crashed after running sed -i against the nextcloud's trashbin directory......



    BUT, I did run 

    root@Tower:~# lsof -r 1 /dev/sdk | tee sdkaccess

     

    for a few hours


    And, came up with this.

    image.png.d9e7021f83b40a4caff6a4494056519e.png

    So, the only process accessing that disk, is hdparm. 

    Disk's settings:

     

    image.thumb.png.415f746d96de423a197da1f53793faa3.png

     


    Unraid Disk Settings:

    image.thumb.png.2477d6dcdbf73d8fbf11fa81ec6eeea8.png




    User Feedback

    Recommended Comments

    I do have ZFS Master installed, but, just to give snapshot functionality to the dashboard. The zpools I do have, were created using unraid 6.12 rc5.

    This particular disk, per the original post, has NOTHING on it. Not even a file system. 

    Despite having 12-18 disks in my chassis, all having issues spinning up every hour, I am opening the ticket specifically for this drive, because it is not in use AT ALL.

    Link to comment

    After uninstalling the ZFS Master plugin last night- 

    I am checking the logs for the unused, completely empty disk-

     

    May 19 12:29:48 Tower emhttpd: read SMART /dev/sdk
    May 19 12:44:49 Tower emhttpd: spinning down /dev/sdk
    May 19 14:07:49 Tower emhttpd: read SMART /dev/sdk
    May 19 14:22:39 Tower emhttpd: spinning down /dev/sdk
    May 19 15:32:43 Tower emhttpd: read SMART /dev/sdk
    May 19 15:47:33 Tower emhttpd: spinning down /dev/sdk
    May 19 16:57:40 Tower emhttpd: read SMART /dev/sdk
    May 19 17:12:28 Tower emhttpd: spinning down /dev/sdk
    May 19 18:22:33 Tower emhttpd: read SMART /dev/sdk
    May 19 18:37:22 Tower emhttpd: spinning down /dev/sdk
    May 19 19:47:29 Tower emhttpd: read SMART /dev/sdk
    May 19 20:02:17 Tower emhttpd: spinning down /dev/sdk
    May 19 21:12:23 Tower emhttpd: read SMART /dev/sdk
    May 19 21:27:12 Tower emhttpd: spinning down /dev/sdk
    May 19 22:37:19 Tower emhttpd: read SMART /dev/sdk
    May 19 22:52:08 Tower emhttpd: spinning down /dev/sdk
    May 20 00:02:16 Tower emhttpd: read SMART /dev/sdk
    May 20 00:17:04 Tower emhttpd: spinning down /dev/sdk
    May 20 01:27:11 Tower emhttpd: read SMART /dev/sdk
    May 20 01:41:59 Tower emhttpd: spinning down /dev/sdk
    May 20 02:52:02 Tower emhttpd: read SMART /dev/sdk
    May 20 03:06:52 Tower emhttpd: spinning down /dev/sdk
    May 20 04:16:55 Tower emhttpd: read SMART /dev/sdk
    May 20 04:31:44 Tower emhttpd: spinning down /dev/sdk
    May 20 05:41:49 Tower emhttpd: read SMART /dev/sdk
    May 20 05:56:38 Tower emhttpd: spinning down /dev/sdk
    May 20 07:06:43 Tower emhttpd: read SMART /dev/sdk
    May 20 07:21:33 Tower emhttpd: spinning down /dev/sdk
    May 20 08:31:36 Tower emhttpd: read SMART /dev/sdk
    May 20 08:46:25 Tower emhttpd: spinning down /dev/sdk
    May 20 09:56:28 Tower emhttpd: read SMART /dev/sdk
    May 20 10:11:18 Tower emhttpd: spinning down /dev/sdk
    May 20 11:21:23 Tower emhttpd: read SMART /dev/sdk
    May 20 11:36:13 Tower emhttpd: spinning down /dev/sdk
    May 20 12:46:18 Tower emhttpd: read SMART /dev/sdk
    May 20 13:01:08 Tower emhttpd: spinning down /dev/sdk



    Regarding the note about the LSI 9300 HBA, what is the suspected idea? 

    Link to comment

    I haven't problem on SAS3008 chips or microsemi hba. ( 6.11.5 )

     

    May be try disable storage OptROM or interrupt 19 capture at BIOS. At least I always disable those and haven't random spinup issue.

     

    To eliminate OS/plugin relate, I recommend use another USB to install fresh Unraid, just keep array stop and click spin down then check any disk will spinup self.

    Edited by Vr2Io
    Link to comment

    So- here is something interesting.

     

    image.thumb.png.abd4d88c7c1d3beb1020af752dc342af.png

     

     

    Nothing has changed. But, after noon on May 21st- all of the disks stopped randomly spinning up. (and, is now working as expected?)

    Going to continue to monitor this, to see if I can figure out exactly... what exactly happened..... 

    Link to comment

    Yea, I don't know how to explain this, but, it only randomly spins up disks for a day or two after booting.

     

    (Disk in the array, empty, unused)

    image.thumb.png.82fab51f8ded32bf8ed994c2258b40be.png

     

    Another disk in the array, also empty, unused.

    image.thumb.png.97c312a8ec3f48bcb2cdd8ee0f06c836.png

     

    Random, unmounted, unused disk. Not in any pool or array.

     

    image.thumb.png.c6c1aadb531c9bebf965366948f88596.png

     



    This matches what I noticed before. To note, these images were taken on 6/14 @ 11:47am. Disks have not spun up in two days. 

    Any ideas on that one?

    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.