Afternoon all, I currently run my sparkbox on my dell optiplex 5040 i have just fished out my old synology 1812+ I basically want the decoding to be done on my optiplex and then shipped across to the NAS and then streamed from the NAS? would that be sensible and doable? also any help or guidance would be great around that
50 replies
tomspark wrote:
Yes, totally sensible setup — the Optiplex handles all the transcoding, the Synology just stores and serves the files. To wire them up, SparkBox mounts a network share from your 1812+ and uses that as its media folder. First: is the Synology already on the same network as the Optiplex? If yes, run sparkbox doctor in a terminal and paste the output here and I'll walk you through the exact steps.
iBangax132 wrote:
yes it will be the same network: interestingly i cant connect to my sparkbox tonight - looks like my ip has changed is there anyway i can update the system to my new ip? (i should of created a static ip.....) [Install location] [OK] SparkBox is installed at: /opt/sparkbox [OK] Settings file (.env): /opt/sparkbox/.env [OK] Media library folder (MEDIAROOT): /opt/sparkbox/data/media [Docker] [ERROR] Cannot connect to Docker daemon - Is Docker running? - Is your user in the docker group? Run: sudo usermod -aG docker $(whoami) [Docker Socket] [OK] Docker socket exists at /var/run/docker.sock [WARN] Docker socket is not readable by current user [User IDs] [INFO] Current user: scott (UID=1000, GID=1000) [OK] PUID=1000 (containers run as UID 1000) [OK] PGID=1000 (containers run as GID 1000) [Container Egress] [WARN] Docker unreachable — skipping egress test (fix Docker first) [Port Conflicts] [OK] Port 53: available [WARN] Port 80: in use by non-Docker process LISTEN 0 4096 0.0.0.0:80 0.0.0.0: [WARN] Port 443: in use by non-Docker process LISTEN 0 4096 0.0.0.0:443 0.0.0.0: [OK] Port 8080: available [WARN] Port 8443: in use by non-Docker process LISTEN 0 4096 0.0.0.0:8443 0.0.0.0: [WARN] Port 9000: in use by non-Docker process LISTEN 0 4096 0.0.0.0:9000 0.0.0.0: [OK] Port 9092: available [Portainer Auth] [INFO] sb-portainer not running — skipping (run: sudo sparkbox up) [VPN Tunnel] [INFO] sb-gluetun not deployed — media stack not installed (or VPN module skipped) [Hardware Transcoding] [OK] /dev/dri exists -- GPU devices detected total 0 drwxr-xr-x 3 root root 100 Jul 31 2026 . drwxr-xr-x 21 root root 4440 Jul 31 2026 .. drwxr-xr-x 2 root root 80 Jul 31 2026 by-path crw-rw----+ 1 root video 226, 0 Jul 31 2026 card0 crw-rw----+ 1 root render 226, 128 Jul 31 2026 renderD128 [OK] Intel Quick Sync / GPU render device available (renderD128) [OK] Render device is accessible by current user [Media Storage] [OK] MEDIAROOT=/opt/sparkbox/data/media exists [OK] MEDIAROOT is writable [WARN] Your apps (user id 1000) can't READ what's in MEDIAROOT — common with media already on a UGREEN/UGOS NAS. [WARN] Fix (read access without taking ownership): sudo chmod -R o+rX '/opt/sparkbox/data/media' [WARN] Guide: https://tomsparkbox.com/guides/use-existing-ugreen-media.html [INFO] Free space at MEDIAROOT: 227GB [System Resources] [INFO] Total RAM: 15878MB [INFO] Available RAM: 11742MB [OK] RAM looks sufficient for 4 enabled modules [INFO] Free disk at SBROOT: 227GB [NAS-Specific] [INFO] NAS type: generic [INFO] Install directory: /opt/sparkbox [WARN] Install directory is on system partition -- consider moving to a data volume [Container Health] [WARN] Docker unreachable — skipping container health (fix Docker first) ============================================ 7 issue(s) found. Review warnings above and fix as needed. ============================================
tomspark wrote:
SparkBox doesn't need any config change when your IP moves — just find the new one and connect to it directly. On the Optiplex, open a terminal and run hostname -I; the first number is your current IP. Then visit http://that-ip:8443 in your browser as normal. That sparkbox doctor output also shows Docker isn't running. Run sudo systemctl start docker first, then sudo sparkbox up to bring everything back. For the static IP: your router should have a 'DHCP reservation' option under connected devices — bind it to your Optiplex's MAC address and it'll always get the same IP from now on.
iBangax132 wrote:
okay fab - ran those two commands and it still says [Docker] [ERROR] Cannot connect to Docker daemon when i then run the doctor line
tomspark wrote:
Good news — Docker is actually running now, your systemctl command worked. The 'Cannot connect' error you're seeing is because your user (scott) doesn't have permission to talk to Docker directly yet — it's a group membership step that's separate from starting Docker. Fix it with this one command: sudo usermod -aG docker $USER Then fully log out and log back in (a proper log-out, not just a new terminal window). After that, sparkbox doctor should show Docker as OK and you'll be able to pick back up on the Synology share setup.
iBangax132 wrote:
ran the command logged out and back in still getting the error below: [Docker] [ERROR] Cannot connect to Docker daemon - Is Docker running? - Is your user in the docker group? Run: sudo usermod -aG docker $(whoami)
tomspark wrote:
Before we try anything else, run this in a terminal and paste the output: groups That tells us whether the docker group actually got added to your account — it should appear in the list. If it's not there, try the same command but with your actual username typed out: sudo usermod -aG docker scott — then log out fully and back in again. If docker IS showing in the groups list but sparkbox doctor still errors, let me know and we'll try a different approach.
iBangax132 wrote:
ok that worked using the direct username, below is the output: SparkBox Doctor Running diagnostics... [Install location] [OK] SparkBox is installed at: /opt/sparkbox [OK] Settings file (.env): /opt/sparkbox/.env [OK] Media library folder (MEDIAROOT): /opt/sparkbox/data/media [Docker] [OK] Docker daemon is accessible [OK] Docker version: Docker version 29.6.0, build fb59821 [OK] Docker Compose: 5.1.4 [Docker Socket] [OK] Docker socket exists at /var/run/docker.sock [OK] Docker socket is readable [User IDs] [INFO] Current user: scott (UID=1000, GID=1000) [OK] PUID=1000 (containers run as UID 1000) [OK] PGID=1000 (containers run as GID 1000) [Container Egress] [OK] Containers can reach webhook.tomsparkbox.com (license server) [Port Conflicts] [OK] Port 53: available [WARN] Port 80: in use by non-Docker process LISTEN 0 4096 0.0.0.0:80 0.0.0.0: [WARN] Port 443: in use by non-Docker process LISTEN 0 4096 0.0.0.0:443 0.0.0.0: [OK] Port 8080: available [WARN] Port 8443: in use by non-Docker process LISTEN 0 4096 0.0.0.0:8443 0.0.0.0: [WARN] Port 9000: in use by non-Docker process LISTEN 0 4096 0.0.0.0:9000 0.0.0.0: [OK] Port 9092: available [Portainer Auth] [OK] Portainer admin login verified (HTTP 200) [VPN Tunnel] [OK] Gluetun tunnel is healthy [Hardware Transcoding] [OK] /dev/dri exists -- GPU devices detected total 0 drwxr-xr-x 3 root root 100 Aug 1 2026 . drwxr-xr-x 21 root root 4440 Aug 1 2026 .. drwxr-xr-x 2 root root 80 Aug 1 2026 by-path crw-rw----+ 1 root video 226, 1 Aug 1 2026 card1 crw-rw----+ 1 root render 226, 128 Aug 1 2026 renderD128 [OK] Intel Quick Sync / GPU render device available (renderD128) [OK] Render device is accessible by current user [Media Storage] [OK] MEDIAROOT=/opt/sparkbox/data/media exists [OK] MEDIAROOT is writable [WARN] Your apps (user id 1000) can't READ what's in MEDIAROOT — common with media already on a UGREEN/UGOS NAS. [WARN] Fix (read access without taking ownership): sudo chmod -R o+rX '/opt/sparkbox/data/media' [WARN] Guide: https://tomsparkbox.com/guides/use-existing-ugreen-media.html [INFO] Free space at MEDIAROOT: 224GB [System Resources] [INFO] Total RAM: 15878MB [INFO] Available RAM: 11747MB [OK] RAM looks sufficient for 4 enabled modules [INFO] Free disk at SBROOT: 224GB [NAS-Specific] [INFO] NAS type: generic [INFO] Install directory: /opt/sparkbox [WARN] Install directory is on system partition -- consider moving to a data volume [Container Health] [OK] All SparkBox containers are running ============================================ 5 issue(s) found. Review warnings above and fix as needed. ============================================
tomspark wrote:
That's Docker fully green now — nice work getting through that. One thing left from that doctor output: your apps still can't read the files in your media folder. This one command fixes it: sudo chmod -R o+rX '/opt/sparkbox/data/media' The port 80/443 warnings are from your other software running on the same machine, not SparkBox — those won't cause issues since SparkBox uses port 8443. Once that chmod runs, open Jellyfin and your media should appear.
iBangax132 wrote:
ran it and here is the output now, the media does show in jellyfin: SparkBox Doctor Running diagnostics... [Install location] [OK] SparkBox is installed at: /opt/sparkbox [OK] Settings file (.env): /opt/sparkbox/.env [OK] Media library folder (MEDIAROOT): /opt/sparkbox/data/media [Docker] [OK] Docker daemon is accessible [OK] Docker version: Docker version 29.6.0, build fb59821 [OK] Docker Compose: 5.1.4 [Docker Socket] [OK] Docker socket exists at /var/run/docker.sock [OK] Docker socket is readable [User IDs] [INFO] Current user: scott (UID=1000, GID=1000) [OK] PUID=1000 (containers run as UID 1000) [OK] PGID=1000 (containers run as GID 1000) [Container Egress] [OK] Containers can reach webhook.tomsparkbox.com (license server) [Port Conflicts] [OK] Port 53: available [WARN] Port 80: in use by non-Docker process LISTEN 0 4096 0.0.0.0:80 0.0.0.0: [WARN] Port 443: in use by non-Docker process LISTEN 0 4096 0.0.0.0:443 0.0.0.0: [OK] Port 8080: available [WARN] Port 8443: in use by non-Docker process LISTEN 0 4096 0.0.0.0:8443 0.0.0.0: [WARN] Port 9000: in use by non-Docker process LISTEN 0 4096 0.0.0.0:9000 0.0.0.0: [OK] Port 9092: available [Portainer Auth] [OK] Portainer admin login verified (HTTP 200) [VPN Tunnel] [OK] Gluetun tunnel is healthy [Hardware Transcoding] [OK] /dev/dri exists -- GPU devices detected total 0 drwxr-xr-x 3 root root 100 Aug 1 2026 . drwxr-xr-x 21 root root 4440 Aug 1 2026 .. drwxr-xr-x 2 root root 80 Aug 1 2026 by-path crw-rw----+ 1 root video 226, 1 Aug 1 2026 card1 crw-rw----+ 1 root render 226, 128 Aug 1 2026 renderD128 [OK] Intel Quick Sync / GPU render device available (renderD128) [OK] Render device is accessible by current user [Media Storage] [OK] MEDIAROOT=/opt/sparkbox/data/media exists [OK] MEDIAROOT is writable [WARN] Your apps (user id 1000) can't READ what's in MEDIAROOT — common with media already on a UGREEN/UGOS NAS. [WARN] Fix (read access without taking ownership): sudo chmod -R o+rX '/opt/sparkbox/data/media' [WARN] Guide: https://tomsparkbox.com/guides/use-existing-ugreen-media.html [INFO] Free space at MEDIAROOT: 224GB [System Resources] [INFO] Total RAM: 15878MB [INFO] Available RAM: 11698MB [OK] RAM looks sufficient for 4 enabled modules [INFO] Free disk at SBROOT: 224GB [NAS-Specific] [INFO] NAS type: generic [INFO] Install directory: /opt/sparkbox [WARN] Install directory is on system partition -- consider moving to a data volume [Container Health] [OK] All SparkBox containers are running ============================================ 5 issue(s) found. Review warnings above and fix as needed. ============================================
tomspark wrote:
The media showing in Jellyfin is what matters — the chmod did its job. That remaining warning in sparkbox doctor is safe to ignore now that things are actually working. Ready to hook up the 1812+ whenever you are. First question: is Synology file sharing set to SMB in Control Panel → File Services? That's the most common setup and from there I can give you the exact mount steps to point SparkBox at it.
iBangax132 wrote:
set the box does have smb service enable
tomspark wrote:
Perfect — that's all we need on the Synology side. Next step is your 1812+'s IP address: in Synology DSM, go to Control Panel → Network → General (it'll be listed there), or check your router's connected devices list. Also grab the name of the shared folder you want SparkBox to use. Once I've got those two things I'll give you the exact command to hook it all together.
iBangax132 wrote:
so the ip im using for my NAS is: 192.BLANK.1.9 shared folder is: \\SWMediaBox inside there i have a sparkbox folder called 'sparkbox'
tomspark wrote:
Perfect, that's all we need. Two commands to mount the Synology first — replace BLANK with your actual IP numbers and fill in your Synology username and password: sudo apt-get install -y cifs-utils && sudo mkdir -p /mnt/synology sudo mount -t cifs //192.BLANK.1.9/SWMediaBox /mnt/synology -o username=YOURUSER,password=YOURPASS,uid=1000,gid=1000 If it goes through without an error message, that means it worked. Let me know and I'll send you the one config command to point SparkBox at the sparkbox subfolder so your media shows up in Jellyfin.
iBangax132 wrote:
so i get these responses: scott@scottmedia:~$ sudo apt-get install -y cifs-utils && sudo mkdir -p /mnt/synology Reading package lists... Done Building dependency tree... Done Reading state information... Done cifs-utils is already the newest version (2:7.0-2ubuntu0.3). 0 to upgrade, 0 to newly install, 0 to remove and 44 not to upgrade. scott@scottmedia:~$ sudo mount -t cifs //192.168.1.9/SWMediaBox /mnt/synology -o username=username.Admin,password=Password,uid=1000,gid=1000 mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
tomspark wrote:
That error means the file-sharing version your computer is trying by default doesn't match what the Synology 1812+ is expecting. Add vers=2.0 to the command — just tack it on at the end: sudo mount -t cifs //192.168.1.9/SWMediaBox /mnt/synology -o username=YOURUSER,password=YOURPASS,uid=1000,gid=1000,vers=2.0 (Replace YOURUSER and YOURPASS with your actual Synology login.) If it runs without printing any error, it worked. Let me know how it goes!
iBangax132 wrote:
now get something a bit different: scott@scottmedia:~$ sudo apt-get install -y cifs-utils && sudo mkdir -p /mnt/synology sudo mount -t cifs //192.168.1.9/SWMediaBox /mnt/synology -o username=Spark.Admin,password=uid=1000,gid=1000vers=2.0 Reading package lists... Done Building dependency tree... Done Reading state information... Done cifs-utils is already the newest version (2:7.0-2ubuntu0.3). 0 to upgrade, 0 to newly install, 0 to remove and 44 not to upgrade. mount: /mnt/synology: failed to parse mount options 'rw,username=user.Admin,password=password,uid=1000,gid=1000vers=2.0': Invalid argument.
tomspark wrote:
Almost there — just a missing comma. You have gid=1000vers=2.0 but it needs to be gid=1000,vers=2.0: sudo mount -t cifs //192.168.1.9/SWMediaBox /mnt/synology -o username=YOURUSER,password=YOURPASS,uid=1000,gid=1000,vers=2.0 Replace YOURUSER and YOURPASS with your Synology login. No error message = success — let me know and I'll send the last SparkBox step to point it at your sparkbox subfolder. Also worth knowing: your Synology username and password appeared in plain text in this thread. Worth changing that password in DSM when you get a moment (Control Panel → User & Group → select your user → Edit).
iBangax132 wrote:
lol good spot thats been changed! here is the new output: Reading package lists... Done Building dependency tree... Done Reading state information... Done cifs-utils is already the newest version (2:7.0-2ubuntu0.3). 0 to upgrade, 0 to newly install, 0 to remove and 44 not to upgrade. mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
tomspark wrote:
That error means the Synology 1812+ is rejecting the protocol version — vers=2.0 is the oldest form of SMB2, and your NAS probably needs 2.1 or newer. Try swapping to vers=3.0: sudo mount -t cifs //192.168.1.9/SWMediaBox /mnt/synology -o username=YOURUSER,password=YOURPASS,uid=1000,gid=1000,vers=3.0 Replace YOURUSER and YOURPASS with your Synology login. No error message = it worked. If it still fails, go into DSM → Control Panel → File Services → SMB tab → Advanced Settings and check what 'Minimum SMB protocol' is set to — share a screenshot and I'll take a look.
iBangax132 wrote:
so you were right it was only accepting 1.b for some reason so pumped it to 3 but revert back to 2.0 in the script. here is the new output ,uid=1000,gid=1000,vers=2.0 Reading package lists... Done Building dependency tree... Done Reading state information... Done cifs-utils is already the newest version (2:7.0-2ubuntu0.3). 0 to upgrade, 0 to newly install, 0 to remove and 44 not to upgrade. mount error(2): No such file or directory Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
tomspark wrote:
That 'No such file or directory' means the connection reached the Synology but it couldn't find the share — usually the name doesn't match exactly (capitals matter). In DSM go to Control Panel → Shared Folders and check what the folder is actually called there. Also, since you bumped DSM to SMB3, the mount command version needs to match — use vers=3.0 not 2.0: sudo mount -t cifs //192.168.1.9/SWMediaBox /mnt/synology -o username=YOURUSER,password=YOURPASS,uid=1000,gid=1000,vers=3.0 Replace YOURUSER and YOURPASS with your Synology login. No error printed = it worked!
iBangax132 wrote:
The folder is called 'SparkBox' inside the DSM shared folders section below is the whole input and output am i missing anything here? scott@scottmedia:~$ sudo apt-get install -y cifs-utils && sudo mkdir -p /mnt/SparkBox sudo mount -t cifs //192.168.1.9/SWMediaBox /mnt/SparkBox -o username=user.Admin,password=pass,uid=1000,gid=1000,vers=3.0 Reading package lists... Done Building dependency tree... Done Reading state information... Done cifs-utils is already the newest version (2:7.0-2ubuntu0.3). 0 to upgrade, 0 to newly install, 0 to remove and 44 not to upgrade. mount error(2): No such file or directory Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
tomspark wrote:
That's the clue — the share name in the mount command needs to match exactly what Synology calls it. You've been using SWMediaBox but the actual share is SparkBox, so swap them: sudo mount -t cifs //192.168.1.9/SparkBox /mnt/SparkBox -o username=YOURUSER,password=YOURPASS,uid=1000,gid=1000,vers=3.0 No error message = it worked. Let me know and I'll send the one SparkBox config command to point it at your media.
iBangax132 wrote:
waaaay thats done the trick! whats the new command to get this show on the road?
tomspark wrote:
Two commands to wire SparkBox up to your Synology — run them in order: sudo sed -i 's|^MEDIAROOT=.|MEDIAROOT=/mnt/SparkBox/sparkbox|' /opt/sparkbox/.env sudo sparkbox up The second one takes a minute while everything restarts. After that, open Jellyfin — if your media doesn't appear automatically, go to Dashboard → Libraries and add the folders from inside your sparkbox share (e.g. /data/Movies, /data/TV, whatever subfolders you've got on the Synology). One heads-up: the Synology mount won't survive a reboot yet. Once everything's working as you'd like, shout and I'll send the one-liner to make it stick permanently.
iBangax132 wrote:
so ive ran the scripts but jellyfin only shows movies in the dell optiplex and not in the DSM. didnt get any errors from terminal should it automatically pick up the movies in there?
tomspark wrote:
Jellyfin doesn't switch over automatically — it still has the old folder saved and needs pointing at the Synology. In Jellyfin go to Dashboard → Libraries, edit each library (pencil icon), and under "Folders" you'll see the old path listed. Remove it and add the new one. The path will start with /data/ followed by whatever subfolder names you have inside your SparkBox folder on the Synology — so if you have a Movies folder there it'd be /data/Movies. What are the folder names inside that sparkbox share on the Synology? Once I know I'll give you the exact paths to put in.
tomspark wrote:
Jellyfin wont auto-swap when the storage moves — its still showing its old cached list from the Optiplex. First lets confirm it can actually SEE the Synology movies now. On the box, run: docker exec sb-jellyfin-media ls /data/Movies - If you see your movie files/folders listed → the mount is working; just trigger a rescan in Jellyfin (Dashboard → Libraries → click the ... on your Movies library → Scan Library, or Scan All Libraries from the top). That drops the old Optiplex entries and pulls in the Synology ones. - If its empty or errors → your movies on the Synology are sitting in a different subfolder (not exactly /Movies), or the share path needs a small tweak. Paste what that command shows and Ill get you sorted.
iBangax132 wrote:
so i have currently the folder setup like this dsm - Sparkbox-Movies-moviesub folder-movie file also another one with 'Series' instead of 'movies'
tomspark wrote:
Two things jump out: 1) Your Movies folder name is spot-on — SparkBox looks for exactly Movies. But your shows folder is called Series, and SparkBox/Jellyfin expects TV. Easiest fix: rename the Synology Series folder to TV. (Or, if you want to keep the name, add a library in Jellyfin pointing at /data/Series.) 2) For the movies still not showing, I need that one command to know whether Jellyfin can actually see them. On the box run: docker exec sb-jellyfin-media ls /data/Movies - If it lists your movie folders → the mount is good, just do a rescan: Jellyfin Dashboard → Scan All Libraries, and theyll show up. - If its empty or errors → the Synology mount isnt live yet and thats the real issue — well fix that. Paste what the command prints and Ill take it from there.
iBangax132 wrote:
that command didnt return anything so i assume it cannot see it yet
tomspark wrote:
Right — empty means the container isnt seeing your Synology yet. Lets find out why. Run these two on the box (a normal terminal, NOT inside a container): mount | grep -i cifs ls -la /mnt/SparkBox The first shows whether your Synology share is actually mounted (SMB shows up as cifs). The second shows whats really sitting at that path. My hunch is a path/capitalization mismatch: SparkBox is currently pointed at /mnt/SparkBox/sparkbox (lowercase), but your folder might actually be Sparkbox (capital S), or your Movies folder might sit directly in /mnt/SparkBox with no sub-folder. Linux paths are case-sensitive, so even a one-letter difference makes it come up empty. Paste both outputs here and Ill give you the exact one-line command to point SparkBox at the right spot.
tomspark wrote:
"that command didnt return anything" tells us the Synology connection has dropped — temporary mounts don't survive a reboot or a short network blip. Remount it with the same command as before (fill in your Synology username and password): sudo mount -t cifs //192.168.1.9/SparkBox /mnt/SparkBox -o username=YOURUSER,password=YOURPASS,uid=1000,gid=1000,vers=3.0 No error message = it's back. Then run that docker exec command again — if it lists your movie folders, just go to Jellyfin Dashboard → Scan All Libraries and they'll appear. Once it's working, shout and I'll give you the one command to make the mount permanent so a reboot won't knock it off again.
iBangax132 wrote:
it comes back with: mount line came back with nothing but the other line did double checked folder and it does have a capital S and B but doesnt in the path file total 12 drwxr-xr-x 3 root root 4096 Jul 3 09:57 . drwxr-xr-x 4 root root 4096 Jul 3 00:30 .. drwxrwxr-x 6 scott scott 4096 Jul 3 09:58 sparkbox i reran a terminal code now it shows the following: total 16 drwxr-xr-x 4 root root 4096 Jul 3 14:26 . drwxr-xr-x 4 root root 4096 Jul 3 00:30 .. drwxrwxr-x 6 scott scott 4096 Jul 3 09:58 sparkbox drwxrwxr-x 6 scott scott 4096 Jul 3 14:27 SparkBox
tomspark wrote:
That pins it down: mount line empty = your Synology share is NOT actually mounted. Those sparkbox / SparkBox folders at /mnt/SparkBox are just empty LOCAL folders that got auto-created — none of it is your NAS, so the media literally isnt reachable. Thats why /data/Movies is empty. Lets mount it properly. Run this — fill in YOUR-NAS-IP and your Synology login (dont paste your password here in the thread): sudo mkdir -p /mnt/synology sudo mount -t cifs //YOUR-NAS-IP/SWMediaBox /mnt/synology -o username=YOUR-SYNOLOGY-USER,password=YOUR-SYNOLOGY-PASS,uid=1000,gid=1000,vers=3.0 Then confirm it worked: ls /mnt/synology/SparkBox/Movies If your movies show up there, reply and Ill give you the exact one-liner to point SparkBox at /mnt/synology/SparkBox (and rename that Series folder to TV). Once its working well make the mount permanent so it survives reboots too.
iBangax132 wrote:
so the first sudo line runs without outputting anything i then run the second sudo and get this error: mount error(2): No such file or directory Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
tomspark wrote:
My mistake from the last message — I sent you SWMediaBox but we already worked out earlier that your actual share name is SparkBox (that's what got us to the working mount a few replies back). Use this: sudo mount -t cifs //192.168.1.9/SparkBox /mnt/synology -o username=YOURUSER,password=YOURPASS,uid=1000,gid=1000,vers=3.0 Replace YOURUSER and YOURPASS with your Synology login. No error = it worked. Then run ls /mnt/synology and paste what you see.
iBangax132 wrote:
so ran the code above and that did work - although i then ran ls /mnt/synology it replied nothing so i then did the following to see folder structure: scott@scottmedia:~$ ls /mnt/synology scott@scottmedia:~$ ls -la total 140 drwxr-x--- 16 scott scott 4096 Jul 3 09:55 . drwxr-xr-x 3 root root 4096 Jun 18 22:19 .. -rw------- 1 scott scott 4267 Jul 3 01:02 .bashhistory -rw-r--r-- 1 scott scott 220 Jun 18 22:19 .bashlogout -rw-r--r-- 1 scott scott 3771 Jun 18 22:19 .bashrc drwxrwxr-x 12 scott scott 4096 Jun 19 15:23 .cache drwxr-xr-x 19 scott scott 4096 Jun 30 22:15 .config drwxr-xr-x 2 scott scott 4096 Jul 3 01:02 Desktop -rw-r--r-- 1 scott scott 27 Jun 18 22:28 .dmrc drwxr-xr-x 3 scott scott 4096 Jun 28 20:19 Documents drwxr-xr-x 2 scott scott 4096 Jul 1 21:50 Downloads -rw-r--r-- 1 scott scott 22 Jun 18 22:19 .gtkrc-2.0 -rw-r--r-- 1 scott scott 516 Jun 18 22:19 .gtkrc-xfce drwxrwxr-x 4 scott scott 4096 Jun 18 22:29 .linuxmint drwxr-xr-x 4 scott scott 4096 Jun 18 22:28 .local drwx------ 4 scott scott 4096 Jun 18 22:31 .mozilla drwxr-xr-x 2 scott scott 4096 Jun 18 22:28 Music drwxr-xr-x 2 scott scott 4096 Jun 18 22:28 Pictures -rw-r--r-- 1 scott scott 807 Jun 18 22:19 .profile drwxr-xr-x 2 scott scott 4096 Jun 18 22:28 Public -rw-r--r-- 1 scott scott 0 Jun 18 22:28 .sudoasadminsuccessful drwxr-xr-x 2 scott scott 4096 Jun 18 22:28 Templates drwxr-xr-x 3 scott scott 4096 Jun 19 13:35 .var drwxr-xr-x 2 scott scott 4096 Jun 18 22:28 Videos -rw------- 1 scott scott 55 Jul 3 09:55 .Xauthority -rw------- 1 scott scott 20714 Jul 3 15:18 .xsession-errors -rw------- 1 scott scott 15325 Jul 3 01:02 .xsession-errors.old
tomspark wrote:
Mount worked — that's the tricky bit done. Run this to see what's actually inside (make sure to include the full path): ls -la /mnt/synology If that also shows nothing, open DSM File Station on the Synology and click into your SparkBox share — have a look at what folders are actually sitting in there. Sometimes files end up in a subfolder a level deeper than expected. Tell me what you see and I'll give you the exact path to set SparkBox to.
iBangax132 wrote:
ls -la /mnt/synology this returns nothing ive looked at the DSM file share and it only has the folders ive manually created which are Movies and TV - hasnt been modified or touched i manually also put a movie in there but it cannot see it this is the folder structure ive created: dsm - Sparkbox-Movies-moviesub folder-movie file /SparkBox/Movies/Dune Part Two (2024) (example)
tomspark wrote:
Empty means the mount still isnt taking hold. Two quick things will crack this: 1) When you ran the mount command, did it print an ERROR line (something like "mount error(13): Permission denied" or "Host is down" or "No such device")? That message tells us exactly whats wrong — run the mount command again and paste any error text it shows. 2) The share NAME has to match your Synology EXACTLY (case-sensitive). In DSM go to Control Panel → Shared Folder — whats the exact name of the top-level shared folder? You mentioned SWMediaBox earlier but your paths now show SparkBox, and those are two different names. Whatever its actually called goes in place of SWMediaBox in the mount command. Paste the exact share name + any error text, and Ill hand you the corrected one-liner.
iBangax132 wrote:
the folder structure is exactly this: /SparkBox/ the mount command didnt error at all
tomspark wrote:
"the mount command didnt error at all" is the key bit — that means the connection reached your Synology fine, so something on the Synology side is blocking the files from coming through. Almost always this is the share permissions: your Synology user can connect, but doesn't have read access to the SparkBox folder contents yet. Fix it in DSM: Control Panel → Shared Folders → click SparkBox → Edit → Permissions tab. Make sure your user (the same one you typed in the mount command) has Read/Write ticked. Save, then run ls -la /mnt/synology again — you should see your Movies and TV folders listed.
iBangax132 wrote:
already had the correct permissions and still coming back empty
tomspark wrote:
Lets change tack — permissions arent the blocker here. Heres the logic: the mount command DIDNT error (so it connected to your Synology fine), but the folder is empty. That means we mounted the WRONG share — an empty one — not that files are being blocked. Your files live in a share called SparkBox (thats what your /SparkBox/Movies path shows), but the mount used SWMediaBox. Lets point it at the right one: sudo umount /mnt/synology 2/dev/null sudo mount -t cifs //YOUR-NAS-IP/SparkBox /mnt/synology -o username=YOUR-USER,password=YOUR-PASS,uid=1000,gid=1000,vers=3.0 ls /mnt/synology/Movies If your Dune folder shows up there, were golden — reply and Ill give you the MEDIAROOT one-liner. If it errors this time, run: mount | grep cifs — and paste it so I can see exactly whats mounted.
iBangax132 wrote:
yes that worked! i can now see the dune movie in there
tomspark wrote:
Two commands to finish the setup — run them in order: sudo sed -i 's|^MEDIAROOT=.|MEDIAROOT=/mnt/synology|' /opt/sparkbox/.env sudo sparkbox up After that, Jellyfin → Dashboard → Scan All Libraries should pull your Movies and TV folders through. To make the mount survive reboots, run this once (fill in your Synology login): echo '//192.168.1.9/SparkBox /mnt/synology cifs username=YOURUSER,password=YOURPASS,uid=1000,gid=1000,vers=3.0,nofail 0 0' | sudo tee -a /etc/fstab No error message = saved. It'll reconnect automatically from now on.
iBangax132 wrote:
didnt out put anything but no errors so i assume thats working and the media files are showing! a side note this to this how do i make all the transcoding happen on my PC and ship it over to the nas? so it would go like this: Seer downlods, after it ran that process it transcode on my optiplex then is placed in the correct area in the nas?