Mount an SMB or NFS share without Rclone
This page shows how to mount a share from your NAS on your Deployrr server with the SMB Mount or NFS Mount option. You fill in a short form and pick a folder. Deployrr mounts the share and adds it to /etc/fstab, the file Linux reads at boot to mount shares again. Use it when you don’t want Rclone.
SMB Mount, NFS Mount or Rclone?
Section titled “SMB Mount, NFS Mount or Rclone?”All three are under System > Mounts.
| SMB Mount | NFS Mount | Rclone | |
|---|---|---|---|
| Works on | VPS, Barebones, Virtual Machine | VPS, Barebones, Virtual Machine | Not blocked in a Proxmox LXC container |
| License | Basic, Plus or Pro | Basic, Plus or Pro | Basic, Plus or Pro |
| What you need from the NAS | Server IP, share name, user name, password | Server IP, export path | Server IP, user name, password, plus a remote name you choose (no share name) |
| Other requirement | None | The NAS user’s UID must match your Deployrr user’s UID | Three menu steps: Install, SMB Remote, Automount |
| Extra software | cifs-utils is installed for you |
The NFS client (nfs-common on Debian or Ubuntu) is installed for you |
Rclone and fuse3 |
| After a reboot | Entry in /etc/fstab |
Entry in /etc/fstab |
Its own service |
| Delay Media Apps | Not offered | Not offered | Offered |
| If the NAS is off at boot | The boot usually waits, then goes on without the share | The boot usually waits, then goes on without the share | With Delay Media Apps, your media apps wait about 15 minutes for the mount, then Deployrr removes their containers. App data stays. |
Pick SMB Mount or NFS Mount if your server is a VPS, a bare-metal machine or a virtual machine and you want a plain mount. Pick Rclone if your server is a Proxmox LXC container, or if you want Delay Media Apps to hold your media apps back until the share is ready. See Mount a NAS share with Rclone.
If your NAS is sometimes off or slow to start when the server boots, plan for it:
- With SMB Mount or NFS Mount, the share stays unmounted until you turn the NAS on and run
sudo mount -a. - The lines Deployrr adds don’t have
nofail. A network share without it usually only delays the boot, but this can differ between distros. To add it, see Server won’t boot after an /etc/fstab change. - To start your media apps only once an SMB or NFS share is mounted, set up the service in step 6 of Apps are stopped or show empty folders after a reboot.
- With Rclone and Delay Media Apps, fix the mount and start the apps again as in step 5 of the same page.
Before you start
Section titled “Before you start”- You have a Basic, Plus or Pro license. If you don’t, Deployrr shows a Requirements Not Met box that says “License - Basic, Plus, or Pro required”.
- You finished the Prerequisites steps. See Quick start.
- Your server is a VPS, Barebones or Virtual Machine system. In a Proxmox LXC container, SMB Mount and NFS Mount do not work. See the note below.
- Your server can reach the NAS on your network.
- For SMB, you know the NAS IP address, the share name, and a NAS user name and password that can read the share.
- For NFS, you know the NAS IP address and the export path, such as
/volume1/media. The NAS user that owns the files must have the same UID as your Deployrr user. The first NFS prompt shows your Deployrr user’s name and UID. Look up the NAS user’s UID on your NAS. - You have an empty folder for the mount, or you are happy to let Deployrr create one.
Mount an SMB share
Section titled “Mount an SMB share”- Open System > Mounts.
- Select SMB Mount (“Mount a remote SMB Share”). The number before “defined” counts the SMB entries Deployrr has added to
/etc/fstab. - Read the SMB Mount Setup box and choose Yes. It lists what you need, including “You need the share name”.
- Wait while Deployrr checks for
cifs-utilsand installs it if it is missing. If you see “Failed to install required packages. Please check your internet connection and try again.”, check that your server can reach the internet and start again. - Fill in the form:
- Server IP is the IP address of your NAS, such as
192.168.5.112. - Share Name is the name of the share on the NAS, such as
media. - Username is your NAS user name.
- Password is your NAS password.
- Server IP is the IP address of your NAS, such as
- Select OK. If you cancel instead, you see “SMB mount setup was cancelled.”
- Read “Select an empty directory as mount point for the SMB share” and select OK.
- Read the Directory Browser - Instructions and select OK.
- In the browser, pick the mount folder. It starts at
/. Up and Down move, Spacebar opens a folder, Tab switches to the buttons and Esc cancels. To make a new folder, type its name at the end of the path, such as/media/nas. - Select Select, then choose Confirm. Deployrr creates the folder if it does not exist. If you choose Cancel here, you see “Directory selection cancelled” and go back to the Mounts menu.
- Wait for the Success box: “SMB share mounted successfully at” and your folder.
Mount an NFS share
Section titled “Mount an NFS share”- Open System > Mounts.
- Select NFS Mount (“Mount a remote NFS Share”).
- Read the NFS Mount Setup box. Check that the UID it shows for your user matches the NAS user’s UID, then choose Yes.
- Wait while Deployrr checks for the NFS client package (
nfs-commonon Debian or Ubuntu) and installs it if it is missing. If it fails, you see the same “Failed to install required packages” message as for SMB. - Fill in the form:
- Server IP is the IP address of your NAS, such as
192.168.5.112. - Export Path is the path the NAS exports, such as
/volume1/media.
- Server IP is the IP address of your NAS, such as
- Select OK. If you cancel instead, you see “NFS mount setup was cancelled.”
- Read “Select an empty directory as mount point for the NFS share” and select OK.
- Read the Directory Browser - Instructions and select OK.
- Pick the mount folder as in the SMB steps and choose Confirm.
- Wait for the Success box: “NFS share mounted successfully at” and your folder.
NFS does not ask for a user name or password. Deployrr’s setup box says the UIDs must match. If they don’t, you may not be able to read or write the files. To understand how this works, read UDMS part 08: Permission Denied Errors (manual setup, background only).
Point your apps at the share
Section titled “Point your apps at the share”Your NAS files now appear in the mount folder. Tell Deployrr to use it in System > Folders (see Set your media, downloads and other folders), then recreate your apps. Part 4 of Mount a NAS share with Rclone covers the folder steps and the recreate command. Use your mount folder where it shows the Rclone path.
Fix “Selected directory is not empty”
Section titled “Fix “Selected directory is not empty””You picked a folder that already has files in it. Deployrr shows:
Selected directory is not empty. Please choose an empty directory or empty (if safe!) the selected directory and retry.Select OK. Deployrr takes you back to the mount folder step. You can fix this in one of two ways.
Pick a different folder. This is the safest choice. Select OK on the instructions, then pick or create a new folder, such as /media/nas2.
Empty the folder. Do this only if the files are leftovers, such as folders your apps created while the share was not mounted. Replace MOUNT_FOLDER with the folder you picked.
-
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, pick a different folder. -
Look at what is in it, hidden files included:
Terminal window ls -A MOUNT_FOLDER -
Move the files somewhere else. Replace
BACKUP_FOLDERwith any path outside the mount folder:Terminal window mkdir -p BACKUP_FOLDERsudo find MOUNT_FOLDER -mindepth 1 -maxdepth 1 -exec mv -t BACKUP_FOLDER {} + -
In Deployrr, select OK on the message, then pick the same folder again.
If apps keep writing into the folder, stop them first. If you installed the Deployrr bash aliases, dcdown stops and removes all your containers, including orphaned ones. Your app data folders are not touched.
dcdownWithout the aliases, run this. Replace DOCKER_FOLDER with your Docker folder path and HOSTNAME with your server’s hostname:
sudo docker compose --profile all -f DOCKER_FOLDER/docker-compose-HOSTNAME.yml down --remove-orphansStart them again with dcup when the mount works. The Rclone version of this problem is a different error. See Rclone mount folder is not empty.
Check it worked
Section titled “Check it worked”-
Check that the folder is a mount. Replace
MOUNT_FOLDERwith your folder:Terminal window mountpoint MOUNT_FOLDERIt says
MOUNT_FOLDER is a mountpoint. -
List the folder. You should see your NAS files:
Terminal window ls MOUNT_FOLDER -
Check the entry Deployrr added to the end of the file. It starts with
# SMB mount added by Deployrror# NFS mount added by Deployrr:Terminal window tail -n 5 /etc/fstab -
Reboot, then run the first two commands again:
Terminal window sudo reboot -
In System > Mounts, the number before “defined” next to SMB Mount or NFS Mount has gone up. It counts entries in
/etc/fstab, so failed runs count too.
If the mount fails
Section titled “If the mount fails”Deployrr shows “Failed to mount SMB share. Please check your settings and try again.” (or “NFS” in place of “SMB”). The box adds that you must edit /etc/fstab by hand to remove or change the mounts Deployrr added.
If you see “Failed to add SMB mount entry to /etc/fstab. Please check permissions and try again.” instead, Deployrr could not write the file. Check that your user can use sudo, then run the option again.
Deployrr keeps the entry in /etc/fstab even when the mount fails. Running the option again adds a second entry. Fix the entry first.
-
Make a copy of the file:
Terminal window sudo cp /etc/fstab /etc/fstab.before-editDeployrr also saved copies before each of its own changes, as
/etc/fstab_followed by the date and time. -
Open the file:
Terminal window sudo nano /etc/fstab -
Find the line that starts with
# SMB mount added by Deployrror# NFS mount added by Deployrr. The mount line is right below it. -
Correct the server, share or export path, or delete the comment line and the mount line. Leave every other line as it is.
-
Save the file, then test it:
Terminal window sudo mount -aNo output means the file is fine. If you see an error, fix the line it names, or put your copy back with
sudo cp /etc/fstab.before-edit /etc/fstab. Don’t reboot untilsudo mount -aruns without errors. For how a manual setup tests an fstab entry, see UDMS part 07: Test fstab Configuration (manual setup, background only).
Check the IP address, share name or export path, and (for SMB) the user name and password in /etc/samba/credentials. Also check that the NAS is on and allows your server to connect.
Remove a mount
Section titled “Remove a mount”SMB Mount and NFS Mount have no remove option. To remove a mount, edit /etc/fstab with the same care as above.
-
Unmount it. Replace
MOUNT_FOLDERwith your folder:Terminal window sudo umount MOUNT_FOLDERIf you see
target is busy, an app or a terminal still uses the folder. Stop your apps (see Fix “Selected directory is not empty”), leave the folder in every terminal, and run the command again. -
Make a copy of the file:
Terminal window sudo cp /etc/fstab /etc/fstab.before-edit -
Open
/etc/fstab, delete the# SMB mount added by Deployrr(or NFS) line and the mount line below it, and save. Leave every other line as it is.Terminal window sudo nano /etc/fstab -
Test the file before you reboot:
Terminal window sudo findmnt --verifysudo mount -afindmnt --verifyends withSuccess, no errors or warnings detectedor lists the problems.mount -aprints nothing when the file is fine. If you see an error, put your copy back withsudo cp /etc/fstab.before-edit /etc/fstab. -
In System > Folders, point any folder that used the mount to a new place, then recreate your apps.
Clean up old copies
Section titled “Clean up old copies”Each time you get past the mount folder step of SMB Mount or NFS Mount, Deployrr saves a copy of /etc/fstab before it changes the file. So you may have several. They are small and harmless. To remove the ones you don’t need, list them first:
ls -l /etc/fstab_*The names end with the date and time, such as /etc/fstab_20261112_143005. Keep the newest one and your own /etc/fstab.before-edit until the server has rebooted fine. Delete the others one at a time, with the full name:
sudo rm /etc/fstab_20261112_143005If no SMB mount line is left in /etc/fstab, you can also delete the file that holds your NAS user name and password. Check first. The command prints 0 when no line uses it:
grep -c "credentials=/etc/samba/credentials" /etc/fstabOnly if you saw 0, delete the file. The next SMB Mount run creates it again.
sudo rm /etc/samba/credentials
