[File Activity Plugin - How can I figure out what keeps spinning up my disks?]

9 hours ago, dlandon said:

Update and try again.

Perfect, it works great now; thanks for the quick fixes!🙂

[File Activity Plugin - How can I figure out what keeps spinning up my disks?]

4 hours ago, dlandon said:

It's an unassigned slot in the array.  I've made an update that will ignore a non-existent disk.

Well that's a quick turnaround!  Thanks!  I can confirm that it now skips over the missing disk2 and works fine unless I try to enable cache drives, in which case I'm getting the same error for `/mnt/cache2` now.  I do have two cache disks, but they're in a pool so there isn't a second mount point (assuming I haven't set this up weird (see screenshot below)).  I guess I should have looked more thoroughly at disks.ini and I might have seen that coming too.

[File Activity Plugin - How can I figure out what keeps spinning up my disks?]

My File Activity plugin on 6.9-beta25 has just recently stopped working, though I'm not sure it's *entirely* File Activity's fault.  When I try to start File Activity, it fails with the following error:

inotifywait[9438]: Couldn't watch /mnt/disk2: No such file or directory

Which is fairly unsurprising because I don't *have* a disk2 so I'm not expecting a /mnt/disk2.  However /usr/local/emhttpd/state/disks.ini does contain this entry:

["disk2"]
idx="2"
name="disk2"
device=""
id=""
size="0"
status="DISK_NP"
rotational=""
format="-"
temp="*"
numReads="0"
numWrites="0"
numErrors="0"
type="Data"
color="grey-off"
spindownDelay="-1"
spinupGroup=""
smType=""
deviceSb=""
idSb=""
sizeSb="0"
luksState="0"
comment=""
floor="0"
exportable="no"
fsType="auto"
fsStatus="-"
fsColor="grey-off"
fsSize="0"
fsFree="0"

 

It's not totally clear to me yet where this entry came from (or how to make it go away), but if this is expected Unraid behavior, File Activity should maybe ignore (or gracefully fail to watch) disks in this state.

Would love any pointers anyone has on how to get rid of this weird phantom disk, or why it's here in the first place