My question: Error opening input file file:/storage/drive-1/[library title 1] Season 1 to 4 Mp4 1080p/Season 1/[TV title 1].mp4. Error opening input files: No such file or directory SparkBox AI replied: The cause is a library path, not a codec or transcode problem. Jellyfin is looking for /storage/drive-1/..., and that path doesn't exist inside the Jellyfin container. The only media folder mounted into it is /data, which is your SparkBox media folder (/opt/sparkbox/data/media on the host). Whatever added that TV library pointed at a drive path from somewhere else. The disk scan also lists only downloads, Movies and Discover in your media folder. There's no big TV folder, so [library title 1] probably isn't in the SparkBox media folder at all. It's likely on another drive. Check where the show actually lives: 1. If it's already in the media folder, under a TV folder with a different name or location: In Jellyfin go to Dashboard → Libraries, open the TV library's folders, remove the /storage/drive-1/... entry, and add the real folder inside the container (/data/TV, or whatever folder holds the show). Then hit Scan Library. 2. If it's on another drive (USB or second disk): the box can't see it yet. On a Legend box, go to Settings → Storage → "Use this drive" → "Let my apps see it", then add the folder name it shows as a …(cut here — the full chat went to Tom) What I still need help with: (describe what didn't work or what's still broken)
22 replies
Allenhaus1 wrote:
this is broke and I'm not not sure where to go from here
Chris wrote:
Sorry this has you stuck. Please skip the Settings steps in the SparkBox AI reply in your post. I can't confirm that menu exists, and I'm sorry it sent you looking for it. What the error means: Jellyfin can only open files from inside its own container, and it sees your SparkBox media folder as /data. The path in the error starts with /storage/drive-1/, which Jellyfin can't reach, so the TV library still points at the old location. One question to narrow it down: is the show's folder inside your SparkBox media folder, or on a separate USB or second drive? You don't need to share the show's name.
Allenhaus1 wrote:
Second USB, we fixed this yesterday and it worked fine this morning, tonight no joy
Chris wrote:
Sorry this is back on you tonight, especially after it worked this morning. I need to correct my last reply. I said I couldn't confirm the Settings Storage "Use this drive" option. It does exist. It is a Legend feature, and it makes a drive plugged into the box visible to Jellyfin, read-only, under /storage. The path in your error, /storage/drive-1, is that location. My best guess: Jellyfin is looking at /storage/drive-1 and finding nothing, which usually means the second USB isn't mounted on the box right now, for example after an unplug or a restart. One check, on the box: run lsblk -f and tell me whether the USB drive shows a mount point. "Mounted" or "not mounted" is all I need, so you don't have to paste the output. Please leave the Jellyfin library path as it is until we know the drive is back.
Allenhaus1 wrote:
all 3 media drives show mounted
Chris wrote:
Thanks, that rules out the drive simply being unplugged, and my earlier guess that it was unmounted was wrong. Sorry for the back and forth on this. Here is my best reading, not yet confirmed on your box. SparkBox remembers the exact folder each drive was mounted at when you chose it. If the drive comes back at a different folder after a restart or replug, SparkBox counts it as not connected and starts Jellyfin without it, which gives the error you see. One check: open Settings → Storage and look at the card for the USB drive. Reply with one word: Connected or Not connected. Please leave the Jellyfin library path as it is until then. I have also corrected that earlier guess in what I work from, so it should not steer the next person with this error.
Allenhaus1 wrote:
All 3 show connected
Chris wrote:
Thanks, that helps. Both checks now show the drives connected, so an unplugged drive may not be the whole story. What matters is whether Jellyfin started with the folder attached: SparkBox only gives an app a drive that is connected when the app starts, so Jellyfin can still be missing it even though the drive shows connected now. Two read-only checks, then reply with only the results: 1. In Settings → Storage, open the card for the USB drive. It should say your apps see it as /storage/drive-1, with Jellyfin among the apps. Tell me if Jellyfin is not listed. 2. In a terminal on the box, run: sudo docker exec sb-jellyfin-media ls /storage/drive-1 If you get a list of folder names, reply "folders listed" and leave the names out. If it says No such file or directory, reply with that line. Please leave the Jellyfin library path as it is for now. Once I have those results I'll give you the next step.
Allenhaus1 wrote:
1. All 3 drives show Jellyfin 2. ls: cannot access '/storage/drive-1': No such file or directory
Chris wrote:
Thanks, that narrows it down, and it changes my read. The drive shows connected and Jellyfin is listed, but the Jellyfin container still can't see /storage/drive-1. That means my last two guesses, the drive being unplugged and the mount folder changing, don't fit. My best guess now is that Jellyfin was started without the drive link and is still running that way. I haven't confirmed that yet. Sorry for the back and forth on this. Next step, on the box: sudo sparkbox restart media This recreates the media apps, Jellyfin included, so expect a short pause. Your libraries and settings are kept, and the Jellyfin library path stays as it is. When it finishes, run: sudo docker exec sb-jellyfin-media ls /storage/drive-1 Reply with "folders listed" or the error line, as before, and leave the names out.
Allenhaus1 wrote:
ls: cannot access '/storage/drive-1': No such file or directory
Chris wrote:
Thanks for checking. The restart didn't clear it, and I need to correct my last reply. I said the drive's folder changing didn't fit, and I shouldn't have ruled that out so quickly. Here is what SparkBox does: it adds /storage/drive-1 to Jellyfin only if, when Jellyfin is recreated, the drive is still mounted at the same folder and with the same file type it was set up with. If either one differs, SparkBox starts Jellyfin without the drive. One read-only check, on the box: sudo docker exec sb-jellyfin-media ls /storage Reply "drive-1 listed" if drive-1 appears in the output, or "nothing listed" if the output is empty. Leave the names out. I'll give the next step from your answer. Please leave the Jellyfin library path as it is. I've also corrected this in what I work from, so it won't steer the next person with this error.
Allenhaus1 wrote:
ls: cannot access '/storage': No such file or directory
Chris wrote:
Thanks, that answers it. The line you pasted shows Jellyfin's container has no /storage folder at all, so it is running without your second USB drive, even though Settings shows the drive as connected. SparkBox attaches a drive to an app only when that app's container is created or recreated, and only if the drive is attached at that moment. A plain restart keeps the container as it is, so it does not bring the drive back. Next step: run sudo sparkbox restart media. It briefly restarts the media apps, including downloads, and does not change your library, your drive or your settings. When it finishes, run sudo docker exec sb-jellyfin-media ls /storage/drive-1 and reply with only "folders listed" or the "No such file or directory" line. Please leave the Jellyfin library path as it is. We have logged the gap between what Settings shows and what Jellyfin can actually see, so the team can look at it.
Allenhaus1 wrote:
No Such file or directory. I noticed when I did the media restart I also got the following statement: Storage: skipped drive-1 for media: its file is not SparkBox's own. Storage: skipped drive-2 for media: its file is not SparkBox's own. Storage: skipped drive-3 for media: its file is not SparkBox's own. Does this mean server doesn't like my drives
Chris wrote:
Sorry this has taken so long, and that the restart I asked you to run didn't fix it. That message is where the problem shows up, so it helps. No, it doesn't mean SparkBox dislikes your drives, and the drives themselves look fine. My reading from SparkBox's code, not yet confirmed on your box: during the restart SparkBox skipped the settings it keeps for each drive, because those settings files are not owned by root, and it only uses files owned by root. Without them Jellyfin starts without the drive, even though Settings shows it as connected. I'm sorry my earlier guesses about unplugging and mount folders sent you in the wrong direction. I don't know yet why those files changed owner, so please don't run chown or chmod on them. One read-only check on the box: sudo ls -ln /opt/sparkbox/state/generated/storage/media Reply with only the number in the third column of each line, such as 0 or 1000, and leave out the file names. Please leave the Jellyfin library path as it is. I've opened a record for the team, and I've corrected my notes so the next person who gets this message isn't sent through the same restart.
Allenhaus1 wrote:
any guesses
Chris wrote:
Yes, I have a best guess, and it is not confirmed on your box yet. The restart skipped all three drives because SparkBox's settings files for them are owned by user 1000 instead of root, and SparkBox only uses those files when it runs as root. Jellyfin then starts without the drive, even though Settings shows it as connected. My reading is that something changed the owner after SparkBox wrote the files, most likely an install or update step, and the team is checking which one. Please don't change the owner or permissions of those files yourself, and don't run storage apply, since it won't change the owner. Leave the Jellyfin library path as it is. I don't have a fix or a date to give you yet. One question that will help: did the box update, or was SparkBox reinstalled, between yesterday morning and last night? A yes or no is enough.
Allenhaus1 wrote:
Mint showed an update but I don't remember what it was
Allenhaus1 wrote:
I will check this tomorrow goodnight
Chris wrote:
Thanks, that helps. Sorry this has run across two nights. We don't know yet whether an update changed the owner of those drive files, so the date matters. When you check tomorrow, run this on the box: grep Start-Date /var/log/apt/history.log | tail -5 Reply with the dates only, and say yes or no to whether SparkBox itself was updated or reinstalled on any of those days. Until then, please leave the drive files and the Jellyfin library path as they are.