Trying to install unpackerr (or any app) and they're all stalling out. The log when I install shows "[1;33m[WARN][0m Media check skipped: MEDIAROOT '/Data/media' doesn't exist right now (unmounted share, or MEDIAROOT points somewhere wrong)." but this is the correct path, the share is mounted correctly in linux, and the media stack is seeing everything correctly.
7 replies
Chris wrote:
That warning is a heads-up, not what's stopping your installs — the installer warns and keeps going, so nothing's broken. What it's really saying: when the box checked, it couldn't find a folder at exactly /Data/media. Linux is picky about exact spelling and capitalization, so your drive is probably mounted at a slightly different path than the one saved. To confirm, run this in the box's terminal: ls -ld /Data/media If it prints "No such file or directory", that's the answer. Point SparkBox at the real folder with: sudo sparkbox set-env MEDIAROOT /the/real/path (paste the actual path), then run sudo sparkbox up. When that warning stops appearing, your installs should stop stalling.
atlashugged wrote:
the path is correct and i'm still getting the error. The media stack sees the path and is working correctly but I can't install other apps.
atlashugged wrote:
sparkbox check-media-perms also returns that the apps can read and write to the downloads folder
Chris wrote:
Good — that rules out the path and permissions, so the warning really is just noise like I said, not your blocker. Since check-media-perms comes back clean, the stall has to be happening somewhere else in the install (image pull, a health check, something in that specific app's startup), and the dashboard's install spinner doesn't surface that underlying error. Could you SSH in and run: sudo sparkbox up unpackerr — then paste back the full output? That will show the actual reason it's stalling instead of the harmless warning we already cleared. If other apps besides unpackerr are stalling too, run the same command with that app's name and paste that too.
Chris wrote:
Checking in on the installs that were stalling even though your media path and permissions checked out. Did they start successfully after the last step, or does the dashboard still hang? If it is still stuck, please share the app name and the first non-sensitive error you see now (redact any passwords or tokens). I’ll use that to narrow the next safe check rather than revisiting the media warning. — checking in
atlashugged wrote:
it's still hanging, yes - here's the full log from the window: Asking server to apply: enable=[unpackerr] disable=[(none)]... sparkbox up [1;33m[WARN][0m Your media folder (/Data/media) doesn't exist right now — is the drive plugged in and mounted? [1;33m[WARN][0m Until it is, media apps will see an empty library and downloads can land on the system disk instead. [1;33m[WARN][0m If the path is just wrong, fix it in Settings → Media (or: sudo sparkbox set-env MEDIAROOT /the/right/path). [0;36m / | | | | ) \ \| ' \ / | '| |/ / \ / \ \/ / ) | |) | (| | | | <| |) | () < |/| ./ \,|| ||\\/ \//\\ || [0m [1mSparkBox[0m v1.6.670 - Self-Hosted Privacy Stack Created by Tom Spark | youtube.com/@TomSparkReviews Network profile: private [0;34m[INFO][0m Starting SparkBox... [0;34m[INFO][0m Skipping the one-time storage-pool moves here: this is running inside the [0;34m[INFO][0m dashboard container, which cannot see your storage pool. They run on the [0;34m[INFO][0m host instead (at install, at boot, and on 'sudo sparkbox up'). [0;34m[INFO][0m Active modules: core dashboard ebooks media unpackerr [1;33m[WARN][0m sbproxy exists but its network bridge is missing (stale after a crash) — recovering so containers can attach... [1;33m[WARN][0m The Docker network needs a daemon restart, but SparkBox is running inside a container here. [1;33m[WARN][0m Run this on the HOST: sudo systemctl restart docker && sudo sparkbox up [0;34m[INFO][0m .env changed since last up — recreating the affected containers to pick up new values [1;33m[WARN][0m VPNPROVIDER=surfshark with VPNDOT='on': Surfshark blocks encrypted DNS inside the tunnel — if the VPN connects but apps report DNS/SSL errors, set VPNDOT=off. [0;34m[INFO][0m core: configuration changed — recreating its containers Container sb-portainer Recreate Container sb-homepage Recreate Container sb-npm Recreate Container sb-homepage Recreated Container sb-portainer Recreated Container sb-npm Recreated Container sb-npm Starting Container sb-homepage Starting Container sb-portainer Starting Container sb-portainer Started Container sb-homepage Started Container sb-npm Started [0;34m[INFO][0m ebooks: configuration changed — recreating its containers Container sb-calibre-web Recreate Container sb-kavita Recreate Container sb-kavita Recreated Container sb-calibre-web Recreated Container sb-calibre-web Starting Container sb-kavita Starting Container sb-kavita Started Container sb-calibre-web Started [0;34m[INFO][0m media: configuration changed — recreating its containers Container sb-bazarr Recreate Container sb-seerr Recreate Container sb-deunhealth Recreate Container sb-gluetun Recreate Container sb-jellyfin-media Recreate Container sb-deunhealth Recreated Container sb-jellyfin-media Recreated Container sb-gluetun Recreated Container sb-prowlarr Recreate Container sb-sabnzbd Recreate Container sb-chaptarr Recreate Container sb-radarr Recreate Container sb-byparr Recreate Container sb-qbittorrent Recreate Container sb-lidarr Recreate Container sb-sonarr Recreate Container sb-seerr Recreated Container sb-byparr Recreated Container sb-chaptarr Recreated Container sb-bazarr Recreated Container sb-prowlarr Recreated Container sb-lidarr Recreated Container sb-radarr Recreated Container sb-qbittorrent Recreated Container sb-sonarr Recreated Container sb-sabnzbd Recreated Container sb-bazarr Starting Container sb-gluetun Starting Container sb-jellyfin-media Starting Container sb-seerr Starting Container sb-deunhealth Starting Container sb-deunhealth Started Container sb-jellyfin-media Started Container sb-bazarr Started Container sb-seerr Started Container sb-gluetun Started Container sb-gluetun Waiting Container sb-gluetun Waiting Container sb-gluetun Waiting Container sb-gluetun Waiting Container sb-gluetun Waiting Container sb-gluetun Waiting Container sb-gluetun Waiting Container sb-gluetun Waiting Container sb-gluetun Healthy Container sb-prowlarr Starting Container sb-gluetun Healthy Container sb-qbittorrent Starting Container sb-gluetun Healthy Container sb-byparr Starting Container sb-gluetun Healthy Container sb-chaptarr Starting Container sb-gluetun Healthy Container sb-lidarr Starting Container sb-gluetun Healthy Container sb-sonarr Starting Container sb-gluetun Healthy Container sb-sabnzbd Starting Container sb-gluetun Healthy Container sb-radarr Starting Container sb-prowlarr Started Container sb-sonarr Started Container sb-qbittorrent Started Container sb-chaptarr Started Container sb-lidarr Started Container sb-radarr Started Container sb-sabnzbd Started Container sb-byparr Started [0;34m[INFO][0m unpackerr: configuration changed — recreating its containers Container sb-unpackerr Recreate Container sb-unpackerr Recreated Container sb-unpackerr Starting Container sb-unpackerr Started [0;32m[OK][0m SparkBox is running! [1;33m[WARN][0m Couldn't create the Calibre library in /opt/sparkbox/data/books yet (Calibre may still be downloading inside sb-calibre-web). Will retry on the next 'sparkbox up'. [1;33m[WARN][0m Media check skipped: MEDIAROOT '/Data/media' doesn't exist right now (unmounted share, or MEDIAROOT points somewhere wrong).
Chris wrote:
Thanks for the full log — reading it end to end, the important finding is that this run actually finished. unpackerr is listed in your active modules, its container was recreated and started ("Container sb-unpackerr Started"), and SparkBox printed "[OK] SparkBox is running!". So first, check the dashboard's Apps page: does the unpackerr tile now open? If the answer is the install window sat on its spinner, that can clear on its own once the underlying issue below is fixed — but please verify the tile first. Two things about the warnings in that log, so they don't send you in the wrong direction: 1. The "/Data/media doesn't exist" lines are not a statement about your host. That log came from inside the dashboard container — it literally says "running inside the dashboard container, which cannot see your storage pool". So it can't see /Data/media even when the drive is mounted on the host. The check that runs on the host proper is check-media-perms, which you already ran and it came back clean. Those in-container warnings can be ignored. 2. The line that actually matters is: "sbproxy exists but its network bridge is missing (stale after a crash)". A missing proxy network is the usual reason installs/appears stall or hang, because containers have trouble attaching. The log even prints the command you need — but it must run on the HOST (the Linux terminal on the box itself, not the dashboard), because the dashboard container can't restart Docker: sudo systemctl restart docker && sudo sparkbox up This restarts the Docker daemon (apps come back automatically) and rebuilds the missing bridge. After it completes, check whether the bridge warning is gone and the unpackerr tile opens. If the tile still won't open after that, paste the fresh output here.