Stuck on 1.6.263, attempts to update failed. Now 1.6.265 is out and still failing silently. Not sure why
7 replies
tomspark wrote:
Awesome — glad that did it! You're current now, so you've got all the recent fixes. And the upgrade choking on a mounted data drive is flagged to fix so it's smoother for you next time. Enjoy, and shout if anything comes up.
tomspark wrote:
Thanks for flagging it — and good news, the 1.6.265 build downloads cleanly on our side (checksum verified), so we just need to find what's snagging on your box. The fastest way to turn that 'silent' failure into a real answer: open a terminal on your server and run sudo sparkbox update Run straight from the terminal, it prints exactly where it stops — the dashboard's Update button hides those messages, which is why it looks silent. Paste me the last 15 or so lines and I'll pinpoint it. One common silent culprit is the system drive being low on space (a full disk makes the download/extract fail quietly) — sparkbox doctor will flag that if so. Also let me know what you're running SparkBox on (UGREEN, a VPS, something else) and we'll get you onto 1.6.265.
Frosty wrote:
I'm running sparkbox on a laptop I use as a dedicated server running xubuntu. I tried again with the web ui and it also failed ~$ sudo sparkbox update [sudo: authenticate] Password: [WARN] Heads up: a newer SparkBox release is out (v1.6.263 - v1.6.295). [WARN] 'sparkbox update' only refreshes your apps' images — it does NOT upgrade SparkBox itself, [WARN] so fixes that ship in a new release won't arrive this way. To upgrade SparkBox + get them: [WARN] sudo sparkbox upgrade [INFO] Pulling latest images for all enabled modules... [+] pull 3/3 ✔ Image jc21/nginx-proxy-manager:2.14.0 Pulled 1.5s ✔ Image portainer/portainer-ce:2.42.0 Pulled 1.2s ✔ Image ghcr.io/gethomepage/homepage:v1.13.1 Pulled 0.7s [+] pull 1/1 ✔ sparkbox-dashboard Skipped No image to be pulled 0.0s [+] pull 11/11 ✔ Image qmcgaw/gluetun:v3.41.1 Pulled 1.4s ✔ Image lscr.io/linuxserver/bazarr:1.5.6 Pulled 2.4s ✔ Image lscr.io/linuxserver/radarr:6.1.1 Pulled 2.0s ✔ Image qmcgaw/deunhealth:latest@sha256:db1e4fcd3aceeb0da34a83f7... Pulled 1.4s ✔ Image jellyfin/jellyfin:10.11.8 Pulled 0.9s ✔ Image lscr.io/linuxserver/sonarr:4.0.17 Pulled 2.4s ✔ Image lscr.io/linuxserver/qbittorrent:5.2.0 Pulled 2.4s ✔ Image lscr.io/linuxserver/prowlarr:2.3.5 Pulled 2.4s ✔ Image ghcr.io/thephaseless/byparr:2.0.0 Pulled 1.7s ✔ Image seerr/seerr:v3.2.0 Pulled 1.0s ✔ Image lscr.io/linuxserver/sabnzbd:4.4.1 Pulled 2.4s [INFO] Recreating containers... [+] up 3/3 ✔ Container sb-portainer Started 6.6s ✔ Container sb-homepage Started 6.5s ✔ Container sb-npm Started 6.4s [+] up 5/11 ✔ Contain... Recreated 3.2s ✘ Contain... Error response from daemon: cannot remove container "54b60a94e740a3fe8569c8ca00b0f19ca05738402c710328989330f5524ee5a6": container is running: stop the container before removing or force remove 4.2s 1.4s ✔ Contain... Recreated 3.1s ✔ Contain... Recreated 1.4s ✔ Contain... Recreated 3.2s ⠋ Contain... Recreate 1.0s ⠋ Contain... Recreate 1.0s ⠋ Contain... Recreate 1.0s ⠋ Contain... Recreate 1.0s ⠋ Contain... Recreate 1.0s ⠋ Contain... Recreate 1.0s Error response from daemon: cannot remove container "54b60a94e740a3fe8569c8ca00b0f19ca05738402c710328989330f5524ee5a6": container is running: stop the container before removing or force remove Sparkbox doctor: [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 140 Jun 18 16:30 . drwxr-xr-x 22 root root 4620 Jun 18 17:06 .. drwxr-xr-x 2 root root 140 Jun 18 16:30 by-path crw-rw----+ 1 root video 226, 0 Jun 18 16:30 card0 crw-rw----+ 1 root video 226, 1 Jun 18 16:30 card1 crw-rw----+ 1 root render 226, 128 Jun 18 16:30 renderD128 crw-rw----+ 1 root render 226, 129 Jun 18 16:30 renderD129 [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: 8533GB [System Resources] [INFO] Total RAM: 15895MB [INFO] Available RAM: 11222MB [OK] RAM looks sufficient for 3 enabled modules [INFO] Free disk at SBROOT: 182GB [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:
You're SO close — that warning is literally the answer. 'sparkbox update' only refreshes your apps' container images; it does NOT move SparkBox itself to a new version, which is why 1.6.263 never budged no matter how many times you ran it (and why the web Update button looked like it did nothing). The command that actually upgrades SparkBox is: sudo sparkbox upgrade Run that and let it finish — it pulls the new release and recreates things, so give it a few minutes — and you'll land on the current version. If it errors partway, paste the last ~15 lines and I'll sort it. Sorry the earlier steer pointed at 'update'; 'upgrade' is the one you want.
Frosty wrote:
[SparkBox] Downloading SparkBox... [SparkBox] Verifying release integrity... [SparkBox] SHA256 digest verified [SparkBox] ed25519 signature verified [SparkBox] Stopping running containers for a safe upgrade snapshot... Network sparkboxsbmedia Removing Network sparkboxsbmediainternal Removing Network sparkboxsbmediainternal Removed Network sparkboxsbmedia Removed [OK] SparkBox stopped. mv: cannot move '/opt/sparkbox/data' to '/opt/sparkbox.new-1781905212/data': Device or resource busy [SparkBox] Upgrade aborted: could not move data/ into staging. Live install untouched. ah, this is probably because i have my media storage setup a weird way. I have a DAS, that i mounted at /opt/sparkbox/data, i can unmount it there and do it the normal way of pointing sparkbox to my media through the ui? or i could shut down, unplug the das, boot & update then reconnect the DAS? lsblk: sda 8:0 0 232.9G 0 disk ├─sda1 8:1 0 1G 0 part /boot/efi └─sda2 8:2 0 231.8G 0 part / sdc 8:32 0 9.1T 0 disk └─sdc1 8:33 0 9.1T 0 part /opt/sparkbox/data
tomspark wrote:
Perfect diagnosis — that's exactly it, and the upgrade aborting safely means your install and media are both untouched. The upgrade stages by moving /opt/sparkbox/data aside, but it can't move a mount point (your DAS is mounted right there), hence 'Device or resource busy'. Your instinct 1 is the clean path — temporarily unmount, upgrade, remount: sudo sparkbox down sudo umount /opt/sparkbox/data sudo sparkbox upgrade sudo mount /dev/sdc1 /opt/sparkbox/data sudo sparkbox up Your media never gets touched — it's on the DAS the whole time, just hidden during the upgrade and right back after the remount. No need to re-point anything in the UI. (If the DAS is in your /etc/fstab, the remount is even simpler: just sudo mount /opt/sparkbox/data.) Separately, the upgrade really should handle a mounted data folder instead of choking on it — I've flagged that to fix so you don't have to dance around it next time. Shout if any step balks.
Frosty wrote:
Worked! Thanks for the help!