Rclone mount fails with "is not empty, use --allow-non-empty to mount anyway"
You set up an Rclone mount for your NAS in Deployrr, but the share does not appear. The Rclone log says the mount folder is not empty. This page shows how to clear the folder safely and mount again.
Symptoms
Section titled “Symptoms”You run System > Mounts > Rclone > Automount. On a first setup, Deployrr shows:
Mount verification failedIf the automount already exists and you agreed to start it, Deployrr shows:
Failed to start service. CheckBoth messages are followed by the path of the Rclone log file. The log has this line. NAME stands for your own folder name:
Fatal error: failed to mount FUSE fs: "/media/rclone/NAME" is not empty, use --allow-non-empty to mount anywayYou may also see the problem after a reboot. Your apps run, but the NAS files are missing.
Rclone refuses to mount a share on a folder that already has files in it. This protects those files from being hidden by the mount.
The usual reason is that apps wrote into the folder while the share was not mounted. For example, Jellyfin or Radarr started before the mount was ready and created folders there. Files left over from an earlier mount attempt can also cause it.
Those files sit on your server’s own disk. They are not your NAS files. Deployrr does not check the folder for stray files before it mounts, so you only find out from the log.
To see how an empty mount folder is made and mounted by hand, watch Rclone SMB mount: creating the mount folders at 10:28 (manual setup; Deployrr does these steps for you).
Replace MOUNT_FOLDER in the commands with the path from the error line, such as /media/rclone/NAME. Replace NAME with the name of your Rclone remote. These are values you fill in.
-
Stop your apps so nothing writes to the folder. This Deployrr command stops and removes all your app containers. Your app data stays. See Bash aliases.
Terminal window dcdown -
Stop the Rclone mount service:
Terminal window sudo systemctl stop rclone-NAME.serviceIf you are not sure of the name, list the Rclone services with
systemctl list-units --all 'rclone-*'. -
Check that the folder is not a mount:
Terminal window mountpoint MOUNT_FOLDERYou must see
MOUNT_FOLDER is not a mountpoint. If it saysis a mountpoint, stop here. The share is mounted, so the folder is not the problem. -
Look at what is in the folder:
Terminal window ls -la MOUNT_FOLDERYou should see folders or files your apps created, not your NAS files. If you see your NAS files, stop and ask for help.
-
Create a backup folder outside the mount folder. Pick any path you like. Replace
BACKUP_FOLDERwith it:Terminal window mkdir -p BACKUP_FOLDER -
Move the contents into the backup folder, hidden files included:
Terminal window sudo find MOUNT_FOLDER -mindepth 1 -maxdepth 1 -exec mv -t BACKUP_FOLDER {} + -
Check that the mount folder is empty:
Terminal window ls -A MOUNT_FOLDERThe command prints nothing.
-
In Deployrr, open System > Mounts > Rclone > Automount.
-
What you see next depends on your setup:
- “An automount is already configured but not active. Would you like to start it now?”: choose Yes. Deployrr shows
Rclone service started successfully. This is the usual case, because a failed first setup still creates the service. - “Confirm Rclone SMB Automount”: choose Proceed. Pick the mount folder and the cache folder, then enter the cache size in GB (a number only). Deployrr shows
Rclone SMB successfully mounted and configured for auto-start. - “An automount is already defined and active for this remote.”: the share is already mounted. Go to “Check it worked”.
- “An automount is already configured but not active. Would you like to start it now?”: choose Yes. Deployrr shows
-
Start your apps again. This command also recreates containers if needed:
Terminal window dcup -
Look through the backup folder. When you are sure you do not need anything in it, delete it:
Terminal window sudo rm -rf BACKUP_FOLDER
If the error comes back, read the end of the Rclone log. The log is in your Docker folder, under logs/YOUR_HOSTNAME/. Replace YOUR_DOCKER_FOLDER with your Docker folder path and YOUR_HOSTNAME with your server’s hostname. To see the Docker folder path, open Prerequisites > Docker Folder in Deployrr.
sudo tail -n 30 YOUR_DOCKER_FOLDER/logs/YOUR_HOSTNAME/rclone-NAME.logCheck it worked
Section titled “Check it worked”-
The folder is now a mount:
Terminal window mountpoint MOUNT_FOLDERIt says
MOUNT_FOLDER is a mountpoint. -
Your NAS files show up:
Terminal window ls MOUNT_FOLDER -
In Deployrr, open System > Mounts > Rclone. The Automount line reads “Rclone SMB Share (MOUNT_FOLDER mounted)”. If it says “not mounted” in red, the mount is still not working.
Stop it coming back
Section titled “Stop it coming back”Apps that use the mount can start before the mount is ready. They then write into the empty folder. Deployrr warns about this: “Typically, Docker containers that rely on Rclone mounts start before the mount is active. This can cause crashes.”
In System > Mounts > Rclone, choose Delay Media Apps (“Set Media apps to Start after Rclone”). Run it after Automount works, because it needs a mounted share. It stops your media apps from starting on their own at boot. Instead, they start once the Rclone mount is ready. The menu shows “DONE” next to it when it is set up. To see why it matters, watch Deployrr 5 walkthrough: Delay Media Apps at 19:36 (shows Deployrr v5; menus differ in v6). Mount a NAS share with Rclone covers the whole Rclone setup.
If the mount is still not ready after about 15 minutes, the media apps stay stopped. Check the timer logs rclone-NAME-timer.log and rclone-NAME-timer.err in the same logs folder as the Rclone log.

