My question: chown: cannot access '/data': No such file or directory SparkBox AI replied: 🔧 working on your SparkBox… 🔧 working on your SparkBox… 🔧 working on your SparkBox… Log's from right after startup, so it doesn't show the actual per-episode import rejection reason directly — but that "Path '/data/TV' is already configured as a root folder" warning is interesting on its own (harmless, just someone tried to re-add it), and doesn't explain the block. Given all 3 stuck items are the same show/season and sitting at 100%/importBlocked with identical vague warnings, the next most common cause for this exact pattern is Sonarr matching multiple files to the same episode or a naming/parse mismatch it won't auto-resolve — that needs a look at the actual per-item rejection in Sonarr's Activity/Queue detail (the tooltip on the warning icon there shows the real reason, not just the filename). I don't have a tool that reads that per-item detail text, so I can't pull the exact rejection message for you. Can you check the little warning triangle next to those 3 items in Sonarr's Activity → Queue tab and tell me what it actually says? Or paste it here — that'll tell us if it's a "files don't match episode" issue vs a language/quality conflict vs something else, and I can give you the precise fix instead of guessing. If you'd rather not dig through the UI, flag it and I'll have you share this to demox — this pattern (importBlocked with empty-looking warnings aft …(reply truncated — full chat sent to Tom)
9 replies
Chris wrote:
Hey Wildwood32, thanks for pasting the AI chat — that helps a lot. There are two separate things bundled here: the chown error in your title, and the Sonarr imports stuck at 100%/importBlocked. For the chown message specifically, can you tell us exactly where you saw it (a docker log, a command you ran by hand, or somewhere else)? That pins down which container or script it's coming from. For the Sonarr side, Tom AI's ask was the right one — open Activity → Queue in Sonarr, hover the warning triangle on those 3 stuck items, and paste the exact tooltip text here. That tells us if it's a match conflict or something else, and we can give you the precise fix instead of guessing.
Wildwood32 wrote:
I inadvertantly went through and deleted all stuck items from Sonarr/ Radarr and overseerr. Still having a degraded system.
Chris wrote:
That's totally fine — those were just stuck queue entries, not your actual library, so deleting them didn't lose anything real. When you say still degraded, can you be specific about what you're seeing right now: is the dashboard showing anything red/unhealthy, are new downloads still failing to import, or is it just that chown error from your first message still showing up somewhere? Also, where exactly did you see that chown /data error — was it something Tom AI printed, or a command you ran yourself over SSH? That'll tell us if it's the same issue or something new.
Wildwood32 wrote:
Its stating that 3 items need attention, but all apps show green on the dashboard.
Chris wrote:
Good news, that actually makes sense and isn't a new problem. The green dots on the Launcher just show a snapshot, so a service can look fine for a second even while it's been quietly restarting itself in the background. The "3 need attention" number is catching that. On your Overview page, scroll down to the "Container health" card (or just click the amber Degraded box near the top) — it'll list exactly which 3 containers and why, with a Restart and View logs button for each one right there. That'll tell us what's actually going on instead of guessing from the overview screenshots.
Wildwood32 wrote:
Ironically, now the system is showing healthy.
Chris wrote:
Glad it settled down on its own, Wildwood32 -- that lines up with what I mentioned, a stale snapshot on the Launcher clearing itself out once things actually catch up. If those 3 items or the amber Degraded flag show up again, just click into Container health and grab the container name plus the reason shown there and we'll dig in properly. Thanks for sticking with the screenshots along the way!