fount this in my syslog,  and can't figure out why its there.  I'm not using a disk5.  I looked everywhere and couldn't find any reference to disk5. 

 "Jan  2 15:31:23 Server inotifywait[10968]: Couldn't watch /mnt/disk5: No such file or directory'

Any suggestions would be appreciated, or should I not worry about it?

 

 

Happy Holidays!!

server-syslog-20200102-2339.zip

server-diagnostics-20200102-1636.zip

Edited January 3, 20206 yr by Walter S

BTW, always post diagnostics.  Much easier for us to look things up.

 

It's probably coming from dynamix file integrity where it's looking for a disk 5, but since you don't have one, it's failing (Probably wasn't written to support gaps in the installed drives)

Thanks Squid, I put the Diag file above,  Is the dynamix file integrity app worth using in your opinion?  I do leave gaps in my array (for future expansion) Should I avoid doing this if it causes problems?

I personally don't see the point as you can always use include / excludes to confine shares to certain disks.  But, in and by itself gaps won't cause any problems.  But, if you do rearrange, you will have to rebuild parity

I understand, Thanks. 

with out causing any ill felling with the author, do you use "dynamix file integrity"? 

No.  IMO "BitRot" is already handled by the massive amounts of error checking that any given hard drive already does.

Thanks for the info Squid.  I try to keep my server simple.