# Simple Setup - Folder Marker Missing

**URL:** https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189
**Category:** Support
**Created:** [May 26, 2024, 12:53pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189 "2024-05-26T12:53:15Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![RichardU](https://forum.syncthing.net/user_avatar/forum.syncthing.net/richardu/32/8542_2.png) [@RichardU](https://forum.syncthing.net/u/RichardU)
#### Post date: [May 26, 2024, 12:53pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/1 "2024-05-26T12:53:15Z")

</div>

I add a folder to SyncTrazor (Windows 10) and sync it with an unRaid server. `.stfolder` is created on my source drive, but I still get the `folder marker missing` error.

Other folders with the same source/destination machines work without problems. v1.27.7 on both machines. I have tried `Ignore Permissions` and I think I’ve done every permutation of deleting and rebooting on both ends before asking for help here.

Any ideas are welcomed.

---

<div class="post-metadata">

### Author: ![gadget](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/g/dec6dc/32.png) [@gadget](https://forum.syncthing.net/u/gadget)
#### Post date: [May 26, 2024, 6:10pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/2 "2024-05-26T18:10:43Z")

</div>

Depending on what the source directory is used for, there might be some kind of cleaner routine removing the empty marker folder. Pull up the file manager and manually verify that `.stfolder` still exists.

---

<div class="post-metadata">

### Author: ![RichardU](https://forum.syncthing.net/user_avatar/forum.syncthing.net/richardu/32/8542_2.png) [@RichardU](https://forum.syncthing.net/u/RichardU)
#### Post date: [May 26, 2024, 8:35pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/3 "2024-05-26T20:35:43Z")

</div>

It’s still there. The error pops up within seconds of accepting the sync – seems likely not enough time for something else to interfere. Thanks for the suggestion.

---

<div class="post-metadata">

### Author: ![gadget](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/g/dec6dc/32.png) [@gadget](https://forum.syncthing.net/u/gadget)
#### Post date: [May 26, 2024, 9:10pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/4 "2024-05-26T21:10:05Z")

</div>

> [@RichardU](#):
>
> The error pops up within seconds of accepting the sync

So the error is being reported by the UnRaid server?

---

<div class="post-metadata">

### Author: ![RichardU](https://forum.syncthing.net/user_avatar/forum.syncthing.net/richardu/32/8542_2.png) [@RichardU](https://forum.syncthing.net/u/RichardU)
#### Post date: [May 27, 2024, 3:23am UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/5 "2024-05-27T03:23:23Z")

</div>

Correct. The error message is: `2024-05-26 23:20:14: Error on folder "D:\\TestMe"` when the the folder being shared is: D:\TestMe

---

<div class="post-metadata">

### Author: ![gadget](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/g/dec6dc/32.png) [@gadget](https://forum.syncthing.net/u/gadget)
#### Post date: [May 27, 2024, 3:25am UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/6 "2024-05-27T03:25:07Z")

</div>

So when you confirmed that `.stfolder` existed, was that on the Windows 10 PC?

---

<div class="post-metadata">

### Author: ![RichardU](https://forum.syncthing.net/user_avatar/forum.syncthing.net/richardu/32/8542_2.png) [@RichardU](https://forum.syncthing.net/u/RichardU)
#### Post date: [May 27, 2024, 11:18am UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/7 "2024-05-27T11:18:18Z")

</div>

Correct. On the unRaid side, I’ve tried both creating the destination folder myself manually or having syncthing create the destination folder, which it does accurately. In either case, there is no `.stfolder` file.

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [May 27, 2024, 1:48pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/8 "2024-05-27T13:48:01Z")

</div>

This is confusing. You seem to be confirming multiple contradictory things.

---

<div class="post-metadata">

### Author: ![RichardU](https://forum.syncthing.net/user_avatar/forum.syncthing.net/richardu/32/8542_2.png) [@RichardU](https://forum.syncthing.net/u/RichardU)
#### Post date: [May 27, 2024, 2:02pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/9 "2024-05-27T14:02:48Z")

</div>

Sorry for the confusion:

Source:

- SyncTrazor (Windows 10)
- `.stfolder` is created

Destination:

- unRaid
- no `.stfolder`
- Error: `2024-05-26 23:20:14: Error on folder "D:\\TestMe"`

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [May 27, 2024, 2:20pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/10 "2024-05-27T14:20:54Z")

</div>

So based on that; UnRAID is a Linux-based system. It will not have a directory called `D:\\TestMe`, unless you’re intentionally doing something quite weird indeed. A path name on the UnRAID server will likely be something Unixy like `/mnt/user/whatever`.

If you’re somehow describing this confusingly and that path name is used on Windows, you don’t want the double backslashes.

As usual, screenshots would be worth a lot here, because we could see what’s actually going on.

---

<div class="post-metadata">

### Author: ![RichardU](https://forum.syncthing.net/user_avatar/forum.syncthing.net/richardu/32/8542_2.png) [@RichardU](https://forum.syncthing.net/u/RichardU)
#### Post date: [May 28, 2024, 2:47am UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/11 "2024-05-28T02:47:33Z")

</div>

You’re right. `D:\\TestMe` is the folder label. The actual folders are:

- Source: `D:\TestMe`
- Destination: `/media/Backup/TestMe`

In my container, `/media` is mapped to `/mnt/user` That works with other folders I’ve added previously.

---

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [May 28, 2024, 5:50am UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/12 "2024-05-28T05:50:59Z")

</div>

Then I suspect Syncthing simply doesn’t have permissions to create the marker. That’s the traditional problem on NASes. If you want more help troubleshooting, post screenshots and logs.

---

<div class="post-metadata">

### Author: ![gadget](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/g/dec6dc/32.png) [@gadget](https://forum.syncthing.net/u/gadget)
#### Post date: [May 28, 2024, 4:16pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/13 "2024-05-28T16:16:28Z")

</div>

> [@RichardU](#):
>
> - Source: `D:\TestMe`
> - Destination: `/media/Backup/TestMe`
> 
> In my container, `/media` is mapped to `/mnt/user` That works with other folders I’ve added previously.

It means that Syncthing running inside your container on your Unraid server must be able to create the path `/mnt/user/Backup/TestMe` on the host side – i.e. Syncthing requires write access to `/mnt/user/` to create the `/mnt/user/Backup` directory before it can create the `TestMe` directory.

You’ll need to verify that every directory in the path is accessible to the Syncthing user inside the container.

---

<div class="post-metadata">

### Author: ![system](https://forum-uploads.syncthingcdn.net/original/2X/0/0b50e0a202b22ae6a67190759e8c868805b8ed9f.png) [@system](https://forum.syncthing.net/u/system)
#### Post date: [June 27, 2024, 4:16pm UTC](https://forum.syncthing.net/t/simple-setup-folder-marker-missing/22189/14 "2024-06-27T16:16:31Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
