Hi everyone, trying to still work out some kinks in my newly installed server.  It's not been busy doing much of anything, has one VM and one container running on it, and sits mostly idle.  There's not even any files on Disk 2 or disk 3, and the ones on Disk 1 are just isos.

 

Disk 2 used to contain my system share, but I've moved that off and it now shows nothing there. I even re-created the share directories on each of the disks, then used touch to create a file there, then had mover move them back to the SATA cache pool, which then as expected deleted the share directories off the disks since they were empty.  I've tried disabling my docker and VM services completely, and still the disks spin up.

 

Interested in any thoughts for what to try next, or if anyone can tell what is causing those three disks (but strangely, never Disk 3) to spin up from my diagnostics.  Thanks in advance.

 

 

moissanite-diagnostics-20230718-1223.zip

Could be the plugin ZFS Master. 

 

28 minutes ago, Niklas said:

Could be the plugin ZFS Master. 

 

Hm,  good possibility, though why would it only be starting one of the empty drive but not the other?

 

I'll dig in on that lead amd see if I cam find anything.

It seems it was ZFS master.  I'll make a post in that plugin's thread to maybe only scan drives that are active, since ZFS can now be in the main array.  The maximum timeout is 5m which I set it to, but no need to keep spinning up disks that wouldn't have any dataset changes if they haven't been spun up since the last check.