Not Detecting Some Files - TrueNAS

[architect]

I’m not sure if this is a TrueNAS setup questiopn or Syncthing question but will ask it on both forums.

I have an entire drive (Zora) that I am syncing between Windows and TrueNAS with ~2.7TB worth of files:

After upgrading from TrueNAS Core to Scale, I have added each folder back, mostly with success.

However, this base folder (Zora) was not properly detected. I only notice this after I realize it started syncing all the files and I caught it after about 30gb of files:

I have SMB setup for this dataset and I can see all the files/folders from windows.

In fact, all the sub folders are syncing pretty fine.

So if that was an issue, subfolders like Music have shown issues.

I’m feeling this is a TrueNAS issue but really lost…

EDIT:

I have tried to add a / to the base folder path and still ignores all the files I can see via Window Share, but somehow detecting another set of files:

[martinleben]

In the first screenshot you see Shared With “TrueNAS(1)”. This in an indication that the other end has not accepted the sharing.

In the second screenshot you can see that Shared With is empty.

So on TrueNas you need to accept the share request.

[architect]

Sorry, I want to clarify that the exact copy of the data exists on both both sides (2.7TB). I did not connect the folders together because I realize that TrueNAS doesn’t see anything locally and brining over files. I stopped it at 30GB. I deleted and readded the folder and it still sees whatever it just synced over instead of the data that already exists. I can understand it’s a pathing issue, but the sub folders are synced up no problem.

[martinleben]

For my clariry, let me rephrase what I believe you have done so far.

• Using som other tool, you made sure that both sides (TrueNAS and XEON) have the same art of files (2.72TiB).
• You created a folder on XEON which you gave Folder ID “Zora” and you set Folder Path to “Z:”.
• You created a folder on TrueNAS which you gave Folder ID “Zora” and you set Folder Path to “~”.

Correct so far?

When you create a folder in Syncthing and set it’s Folder Path to an existing directory, Syncthing needs to scan it. This takes a long time given that you have quite much data.

@architect

However, this base folder (Zora) was not properly detected. I only notice this after I realize it started syncing all the files and I caught it after about 30gb of files:

(… and a screenshot from TrueNAS were “Shared With” was empty.)

Since Shared With is empty, TrueNAS folder “Zora” is NOT synching with anything. So the 30 gigs you see is just how far it had gotten in the initial scanning.

@architect

I did not connect the folders together because I realize that TrueNAS doesn’t see anything locally and brining over files.

What makes you believe it does not “see anything locally”?

[architect]

Thanks for responding.

If you see my first screenshot of Zora XEON, there are 2.7TB of data. The other screenshots of Zora TrueNAS shows only ~30gb of data after scan.

This should not have anything to do with sharing. Zora TrueNAS not shared with anything should still show that it’s 2.7TB of files locally. Both drives are identical and Up to Date prior to the TrueNAS upgrade. Again, the local subfolders all seem to have scanned and synced up without issue.

At this point, I am just going to nuke the entire Synching install and start from scratch. Everything was fine before the upgrade from Core to Scale so I think something happened on the way…

[martinleben]

I agree that starting from scratch is best if you feel unsure. I’d like to give some pieces of advice / tips / knowledge:

1. On XEON the Zora share uses Folder Path “Z:”. In this situation the filesystem watcher does not work. See Filesystem watcher error when watching disk root directory on Windows · Issue #5578 · syncthing/syncthing · GitHub .
2. On TrueNAS, start with some directories containing small sets of test data, so that you can get to know the system without jeopardising valuable files.

Good luck!

[architect]

Nuking Syncthing and reloading all the folders worked. Now the long wait for my 2.7TB folder to scan.

Not sure about the Z: path being an issue. It looks like it was fixed in v1.1.4 in 2019. I don’t seem to have any issues with watching for changes for any root folders.