tomspark wrote:
Hey unfied — almost certainly that SparkBox installed before the NAS mount existed, so MEDIAROOT points at the local path. Confirm the mount is live with df -h, then edit /opt/sparkbox/.env and set MEDIAROOT to the mount path, then sudo sparkbox up to restart. If the containers still can't read it after that, PUID/PGID in .env probably don't match the NAS share owner — ls -la the mount and post the output and I'll point you at the right values.
unfied wrote:
Hi i did what you said but yes it did not fix me not seeing the mount after i did the ls -la this is what i got total 4 drwxr-xr-x 2 root root 0 May 7 13:48 . drwxr-xr-x 3 root root 4096 May 8 09:11 .. drwxr-xr-x 2 root root 0 Feb 26 16:29 'Nas 2' dr-xr-xr-x 2 root root 0 Feb 26 16:20 @Recently-Snapshot drwxr-xr-x 2 root root 0 Feb 26 16:20 @Recycle
tomspark wrote:
That ls shows the mount point with one 0-byte subfolder 'Nas 2' — looks like you mounted one level above the actual share. Try ls -la /your/mount/path/Nas\ 2/ and see if your media lives there. If yes, point MEDIAROOT at that subpath (or symlink to avoid the space). If Nas 2/ is genuinely empty too, post the output of mount | grep nas and df -h so we can see what's actually mounted.
tomspark wrote:
Ah, that's a UGREEN NAS mount — the root ownership is the problem. Run sudo chown 1000:1000 /mnt/your-mount-path (replace with your actual mount), then sudo sparkbox up again and the containers will be able to read/write it.