Sparkbox install stopped

Posted by Newworld

Hi I'm really new at all of this, so much so it has taken a little while to figure out how to get the the terminal prompt. I ran the script but it froze at the Boot self-heal enabled line. I came complete out of it thinking I had done something wrong and then re ran it. But the same thing has happened again. It's been hanging for 20 mins and there is very little on my nas Please could yo have a look at this and let me know what i've miss? [SparkBox] Downloading SparkBox... [SparkBox] Verifying release integrity... [SparkBox] SHA256 digest verified [SparkBox] ed25519 signature verified [SparkBox] Stopping running containers for a safe upgrade snapshot... [INFO] Stopping SparkBox... Warning: No resource found to remove for project "sparkbox". time="2026-06-27T22:40:54+01:00" level=warning msg="The \"SBADMINPASSWORDHASH\" variable is not set. Defaulting to a blank string." Warning: No resource found to remove for project "sparkbox". [OK] SparkBox stopped. [SparkBox] Upgrade applied atomically. Rollback copy preserved at /opt/sparkbox.rollback-1782596454 until health probe confirms success. [SparkBox] SparkBox downloaded to /opt/sparkbox [SparkBox] SparkBox installed to /opt/sparkbox 100 155k 100 155k 0 0 49543 0 0:00:03 0:00:03 --:--:-- 49553 [SparkBox] NAS mode: skipping firewall configuration. [SparkBox] Configure port forwarding through your NAS or router admin panel. [SparkBox] Non-interactive install detected (piped from curl). Skipping wizard. [SparkBox] Bringing up core services so the dashboard is reachable... [SparkBox] Keeping existing .env from previous install. [SparkBox] Rendering module templates... [SparkBox] Pi-hole pre-configured with NAS telemetry blocklist [SparkBox] Gotify admin password pre-seeded (plaintext saved to state/gotify-admin-password.txt) [SparkBox] FileBrowser admin password pre-seeded (init runs after first boot via filebrowser-init.sh) [SparkBox] qBittorrent admin password pre-seeded (plaintext saved to state/qbittorrent-admin-password.txt) [SparkBox] Boot self-heal enabled (sparkbox-boot.service runs 'sparkbox up' after every reboot)

1 replies

Chris wrote:

Hey Newworld — sorry this got missed, and sorry for the long silence you saw. Good news: you didn't actually break anything. Right after "Boot self-heal enabled," the installer pulls all the container images with no on-screen progress, and on a slower connection that step alone can eat 10-30 minutes looking completely frozen. That silent stretch was a real bug and Tom shipped a fix for it back in v1.6.459 — a fresh install now prints a live log path plus a heartbeat every couple minutes so it never looks dead. If your box still isn't up, run sudo sparkbox update then sudo sparkbox up and you should see real progress this time. If you're already running fine, just ignore this!