[Solved] NTFS drive issue causing Syslog spam

[Marc_G2]

UPDATE.

I ended up formatting the SSD to XFS, and the problem went a way.  The drive was originally formatted to NTFS by Windows when I created the VM.  Perhaps that caused the issue.  

 

ORIGINAL POST_________________________

I've attached my system log.  I believe there's an issue with my UD mounted SSD that's causing my system log to get filled up with this message below.  Most recently, I created a new Windows 10 VM while passing though the SSD.  I'm guessing that's related.  I also recently enabled ACS override to pass though a USB card.   Help would be greatly appreciated.

 

Nov 16 10:01:33 NAS-NG ntfs-3g[6394]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000  size: 4096   usa_ofs: 0  usa_count: 0: Invalid argument
Nov 16 10:01:33 NAS-NG ntfs-3g[6394]: Index buffer (VCN 0x0) of directory inode 86039 has a size (24) differing from the directory specified size (4096).
Nov 16 10:01:33 NAS-NG ntfs-3g[6394]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000  size: 4096   usa_ofs: 0  usa_count: 0: Invalid argument
Nov 16 10:01:33 NAS-NG ntfs-3g[6394]: Index buffer (VCN 0x0) of directory inode 86096 has a size (24) differing from the directory specified size (4096).
Nov 16 10:01:33 NAS-NG ntfs-3g[6394]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000  size: 4096   usa_ofs: 0  usa_count: 0: Invalid argument
Nov 16 10:01:33 NAS-NG ntfs-3g[6394]: Index buffer (VCN 0x0) of directory inode 83330 has a size (24) differing from the directory specified size (4096).
Nov 16 10:01:33 NAS-NG ntfs-3g[6394]: ntfs_mst_post_read_fixup_warn: magic: 0x00000000  size: 4096   usa_ofs: 0  usa_count: 0: Invalid argument
Nov 16 10:01:33 NAS-NG ntfs-3g[6394]: Index buffer (VCN 0x0) of directory inode 83338 has a size (24) differing from the directory specified size (4096).

 

nas-ng-syslog-20191116-1502.zip

nas-ng-diagnostics-20191116-1526.zip

Edited November 17, 2019 by Marc_G2

[Marc_G2]

Some Googling showed that the error could be result of corrupt file system.  I ran Windows Chkdsk and it found no errors.  Against my better judgement, I decided to delete the empty partition shown in the screenshot and now it can't boot properly.   I guess I will do another fresh install of windows.