Disks Spinning Up (For no reason).

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. 

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.



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

Disk's settings:

Unraid Disk Settings: