i woke up this morning to find my log being spammed with a few error messages, one i figured out (it was dynamix system info spamming a message, i believe it was just due to not restarting unraid after it updated, either way i don't use the plugin so i uninstalled it, that error stopped.) but the other one was quite puzzling and from googling it seems to be a hard drive related issue.

Feb 12 04:07:02 otfgserver kernel: docker0: port 1(veth172e216) entered forwarding state
Feb 12 04:07:02 otfgserver CA Backup/Restore: done!
Feb 12 04:07:03 otfgserver  avahi-daemon[12132]: Joining mDNS multicast group on interface veth172e216.IPv6 with address fe80::3cea:3aff:fea1:54b.
Feb 12 04:07:03 otfgserver  avahi-daemon[12132]: New relevant interface veth172e216.IPv6 for mDNS.
Feb 12 04:07:03 otfgserver  avahi-daemon[12132]: Registering new address record for fe80::3cea:3aff:fea1:54b on veth172e216.*.
Feb 12 04:07:04 otfgserver CA Backup/Restore: Starting PlexMediaServer... (try #1) 
Feb 12 04:07:06 otfgserver CA Backup/Restore: done!
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: ntfs_mst_post_read_fixup_warn: magic: 0x361ed4da  size: 4096   usa_ofs: 11910  usa_count: 19358: Invalid argument
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: Corrupt index block signature: vcn 83 inode 7288
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: ntfs_mst_post_read_fixup_warn: magic: 0x361ed4da  size: 4096   usa_ofs: 11910  usa_count: 19358: Invalid argument
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: Corrupt index block signature: vcn 83 inode 7288
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: ntfs_mst_post_read_fixup_warn: magic: 0x361ed4da  size: 4096   usa_ofs: 11910  usa_count: 19358: Invalid argument
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: Corrupt index block signature: vcn 83 inode 7288
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: ntfs_mst_post_read_fixup_warn: magic: 0x361ed4da  size: 4096   usa_ofs: 11910  usa_count: 19358: Invalid argument
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: Corrupt index block signature: vcn 83 inode 7288
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: ntfs_mst_post_read_fixup_warn: magic: 0x361ed4da  size: 4096   usa_ofs: 11910  usa_count: 19358: Invalid argument
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: Corrupt index block signature: vcn 83 inode 7288

this is when it first appears in the syslog. and repeats with the odd line being 

Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: ntfs_mst_post_read_fixup_warn: magic: 0x361ed4da  size: 4096   usa_ofs: 11910  usa_count: 19358: Invalid argument
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: Corrupt index block signature: vcn 83 inode 7288
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: Record 10651 has no FILE magic (0x0)
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000  size: 1024   usa_ofs: 0  usa_count: 0: Invalid argument
Feb 12 04:07:06 otfgserver  ntfs-3g[28431]: Record 10651 has no FILE magic (0x0)

i can upload my entire syslog file, but it is quite large (and verry long) due to these errors spamming a few times a second.

the only thing it could be is this weekend i was takling my security cameras and plugged a new (ADDED, not swapped) 8tb serveilance hdd in to use for the security camera footage and was playing around with new software, and had it mounted into an ubuntu vm to run the desktop version of shinobi, as well as i had the older docker version of shinobi (ive been using this for a couple years now, didnt change anything other than telling it to use the new drive instead of the old one) both these drives are mounted using the unassigned devices plugin and not in any way connected to the array. unraid tells me everything is fine with the system, and a fix common problem scan also turns up nothing.

otfgserver-diagnostics-20230212-1440.zip

That's from an NTFS connected disk, disconnect it and run chkdsk on it, if it's already been disconnected reboot the server.

i think i figured it it out...i did a dumb thing, when i formatted and put the new partition on my 8tb drive i just added for my security camera system i formatted it as ntfs, my old drive was xfs. i formatted it to xfs and the errors appear to have stopped....i will do a restart but unraid is currently in the middle of a parity check so i will wait till its done. the only other ntfs drive i have is a small ssd used for update backups and. but this error did start showing up like 24hrs after the new drive was put in....not quite shure how it being ntfs and a brand new disk caused the problem....but maby it was something when i did while mounting it in the vm, or copying files over to it