Drive full after trying to re-sync

I have Syncthing running on about 6 clients, including 2 phones. My hard drive unexpectedly failed, and after installing another, I have had difficulty re-syncing, particularly with a MyCloudEX2Ultra. I had 6 TB free on it when I installed my new hard drive in my PC, now it is full, and I can’t even log into it with the GUI. I am able to SSH into it, but don’t know enough about where to look for the offending files, although I’ve tried.

Syncthing says it is unable to sync the 35 GB that it had been syncing and is out of sync the last time I was able to check. These files are/were shared with 4 clients.

It was working great. After I recovered my backups with Macrium, it didn’t update the last couple of weeks, and Syncthing promptly synced with the other clients to match my shortness on the new hard drive. I had the later data on a laptop which I had turned off, and recovered the remainder from that. That’s why it isn’t a good backup, because it will carry your erasures and mistakes to the other clients. But now I can’t get the NAS to work properly and it’s full of something.

Any ideas? Could it be Syncthing that filled up my NAS with 6 TB in the last couple of days? What else can I look for? tia, jts

It’s quite difficult to say without having at least some screenshots of the Web GUI and/or logfiles to see what exactly has been going on there.

Do you perhaps have versioning enabled? If yes, that could possibly fill up quite a bit of space if you’re dealing with giant files that have been sent there. Also, large conflict files could be a problem too. Just some ideas on my part here, without being able to verify anything 100%.

Here’s a screenshot today. I have the log also. What should I do with it? I have since paused all on the NAS.

Well, the two folders have been stopped with folder path missing errors, which is not good. This means that folder markers (which are normally hidden folders called .stfolder in the folder roots) are missing.

I’d suggest that you first check what is actually going on with the folders physically. Also, do not try to recreate .stfolder manually unless you know 100% what you’re doing, because this could potentially lead to mass deletions on the other devices.

Basically, are the folders with their content physically there? If yes, then you should try to investigate why Syncthing cannot detect them and/or what happened to their markers.

Well I sure don’t know 100% of what I am doing, maybe 10%. I did have versioning turned on so there was about 100 GB in the folder. I removed the folder from syncthing and ssh’d in and deleted the folder. It wouldn’t let me delete it in windows. My plan is to now re-share with the NAS client from my desktop and laptop and hope that’s the end of that.

It may have the folder path missing because I removed the folder from syncthing when it wiped out part of my data after the hard drive replacement, then shared it again. It warned me that it was an existing folder when I selected it. The path, however, was correct in the GUI.

I’m still unsure what filled up the NAS. I couldn’t get into the GUI with it full, so I pulled the plug on it, and when it got through booting thoroughly, it showed over 7 TB free, and all seems well for now. Pretty much.

Thanks for the help.

It’s just not working after working without a hitch for about a year or so. I removed my sync folder from the NAS and deleted the folder. I then re-shared it from two other clients, and it is stuck with the message about the folder path. It hasn’t even created the folder yet and it is stopped, and I don’t know how to get it going. Amy help is appreciated.

If Syncthing cannot even create the folders, then I can only think about maybe permission issues, where the program is simply not allowed to access the given paths. This is assuming that the paths themselves are actually correct and writable.

Yes, sir, it is in the same place it was before, and it was writeable then, unless something has changed that I am not aware of.
Should I copy the current files to this directory?

Not really. You may try to remove the folders from Syncthing and then re-add them, but if the situation is still the same then, I’d suggest to focus on finding out what exactly is blocking the program from accessing those paths first and foremost.

I’d also make sure to have a full backup of the data in question, just in case something goes wrong during the experiments.

How about if I uninstall and reinstall it? Will that reset it, or will it use the old settings?

As it is now, I can’t get it to sync anything on the Mycloudex2ultra. I don’t know how to check permissions other than the GUI, and syncthing isn’t shown.

thanks again, jts

This is handled differently depending on the operating system, e.g. typical desktop systems like Windows or GNU/Linux will keep the settings, but others like Android will not. I’ve no idea how yours operates, so you may just have to do a test yourself. In case the settings do remain, you may need to manually find the home folder and remove them from there.

OK, I can do that. It’s a linux base OS, maybe archlinux, but I can plunder around and find the home folder if it don’t get taken out. thanks again, jts

Well, that didn’t work. I deleted the syncthing home folder after the first reinstall, and I thought it was good to go, but it can’t write and even create the directory for the shared files. That may be the issue, but I don’t know how to handle it. It is frustrating, especially when it worked so well before the hard drive failure.

Do the file permissions and ownership fit to the user running syncthing?

Yes, I’ve changed it to logging in as admin with full privileges and other users. I’ve now upgraded the operating system. I’ve uninstalled and reinstalled syncthing, and it just can’t get back going, gets stuck with every file and folder out of sync. I don’t know why it can’t write to the NAS. I’m ready to give up.

Anybody know if syncthing run on an Asusstore or Synology?

Could you post the current logs? Hard to tell what is exactly going wrong without them.

I have it running fine on two Synologys usind the package provided by SynoCommunity. There you still need to take care of the right folder permissions though, same as the current situation.

I suggest you take a look at the actual folder path using a file manager or the command line. Then post screenshots of what current permissions are granted to whom. Next step is to find out which user Syncthing is running as, which depends on how you start it on the NAS.

Here is my latest log after I shut it down. I have an older log with more info if needed.

2021-10-01 09:51:27 My ID: 4BJ6GFI-TWYGCIE-WCPNUUO-BTROMEQ-YGT46YG-IM2M5LY-TQ5INRK-JPLZGAJ
2021-10-01 09:51:28 Single thread SHA256 performance is 18 MB/s using minio/sha256-simd (18 MB/s using crypto/sha256).
2021-10-01 09:51:28 Hashing performance is 16.46 MB/s
2021-10-01 09:51:28 Overall send rate is unlimited, receive rate is unlimited
2021-10-01 09:51:28 Ready to synchronize "TEST" (zv7pd-eocsy) (sendreceive)
2021-10-01 09:51:28 Failed initial scan of sendreceive folder "TEST" (zv7pd-eocsy)
2021-10-01 09:51:28 Error on folder "TEST" (zv7pd-eocsy): folder path missing
2021-10-01 09:51:28 TCP listener ([::]:22000) starting
2021-10-01 09:51:28 Relay listener (dynamic+https://relays.syncthing.net/endpoint) starting
2021-10-01 09:51:28 QUIC listener ([::]:22000) starting
2021-10-01 09:51:28 ...
2021-10-01 09:51:28 Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
2021-10-01 09:51:28 Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
2021-10-01 09:51:28 Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
2021-10-01 09:51:28 Using discovery mechanism: IPv4 local broadcast discovery on port 21027
2021-10-01 09:51:28 Using discovery mechanism: IPv6 local multicast discovery on address [ff12::8384]:21027
2021-10-01 09:51:28 GUI and API listening on 192.168.1.191:8384
2021-10-01 09:51:28 Access the GUI via the following URL: http://192.168.1.191:8384/
2021-10-01 09:51:28 My name is "MyCloudEX2Ultra"
2021-10-01 09:51:28 Device KVRQWJU-PJFAEJ3-CCJGVVG-B72XNXB-A2XL2LD-ILNIWQR-5R7KBXJ-U2ZY2QB is "DELL1" at [dynamic]
2021-10-01 09:51:28 Syncthing should not run as a privileged or system user. Please consider using a normal user account.
2021-10-01 09:51:28 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 09:51:28 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 09:51:28 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 09:51:28 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 09:51:37 Established secure connection to KVRQWJU-PJFAEJ3-CCJGVVG-B72XNXB-A2XL2LD-ILNIWQR-5R7KBXJ-U2ZY2QB at 192.168.1.191:22000-192.168.1.24:22000/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256
2021-10-01 09:51:37 Device KVRQWJU-PJFAEJ3-CCJGVVG-B72XNXB-A2XL2LD-ILNIWQR-5R7KBXJ-U2ZY2QB client is "syncthing v1.18.2" named "DELL1" at 192.168.1.191:22000-192.168.1.24:22000/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256
2021-10-01 09:51:38 Connected to already connected device KVRQWJU-PJFAEJ3-CCJGVVG-B72XNXB-A2XL2LD-ILNIWQR-5R7KBXJ-U2ZY2QB (existing: 192.168.1.191:22000-192.168.1.24:22000/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256 new: 192.168.1.191:53246-192.168.1.24:22000/tcp-client/TLS1.3-TLS_CHACHA20_POLY1305_SHA256)
2021-10-01 09:51:39 New NAT port mapping: external TCP address 64.82.190.79:65493 to local address [::]:22000.
2021-10-01 09:51:39 Detected 1 NAT service
2021-10-01 09:51:48 quic://0.0.0.0:22000 detected NAT type: Port restricted NAT
2021-10-01 09:51:48 quic://0.0.0.0:22000 resolved external address quic://64.82.190.79:22000 (via stun.syncthing.net:3478)
2021-10-01 09:52:24 Joined relay relay://74.15.231.214:22067
2021-10-01 10:21:32 Sent usage report (version 3)
2021-10-01 10:21:39 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 10:21:39 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 10:21:39 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 10:21:39 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 10:51:49 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 10:51:49 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 10:51:49 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 10:51:49 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 11:21:59 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 11:21:59 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 11:21:59 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 11:21:59 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 11:52:09 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 11:52:09 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 11:52:09 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 11:52:09 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 12:22:20 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 12:22:20 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 12:22:20 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 12:22:20 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 12:52:30 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 12:52:30 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 12:52:30 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 12:52:30 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 13:22:40 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 13:22:40 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 13:22:40 http://192.168.1.1:33516/rootDesc.xml - malformed InternetGatewayDevice description: no WANDevices specified.
2021-10-01 13:22:40 UPnP parse: [http://192.168.1.1:33516/rootDesc.xml] Malformed device description: no compatible service descriptions found.
2021-10-01 13:27:58 Wrong credentials supplied during API authorization from 192.168.1.24:61185

What’s the path of this folder?

I can ssh in, but don’t know where or necessarily how to look for privileges. I have WinSCP. I’ll see what I can learn with that. I’m about out of options. thanks for the help, jts