My question: my media is on a USB Drive how do I add it into jellyfin SparkBox AI replied: I stopped myself before handing you a command that would change ownership or permissions across your whole media library. That class of command has broken more libraries than it fixed — it can lock your NAS's own apps out of your files, and it can't be undone. The safe version grants access through an ACL without changing owners: sudo setfacl -R -m u:1000:rwX -d -m u:1000:rwX '/opt/sparkbox/data/media' or, if the app only needs to READ your media: sudo setfacl -R -m u:1000:rX -d -m u:1000:rX '/opt/sparkbox/data/media' If your share doesn't support setfacl, add the app's user to the folder's group instead of using a recursive chmod. If the problem you were fixing still needs something else, tell me exactly what the app showed you and I'll find a safer command. What I still need help with: (describe what didn't work or what's still broken)
19 replies
Allenhaus1 wrote:
this is a linux mint desktop with the multiple USB drives mounted, all have media. When I put in the path I get the following error, "The path could not be found. Please ensure the path is valid and try again."
Chris wrote:
Sorry, the earlier answer on this post pointed you at permission commands for a problem you don't have. Please don't run the setfacl lines from it. Jellyfin only sees the folders SparkBox connects to it, so a USB drive has to be set up in SparkBox before Jellyfin can use it. On the new dashboard (V2, from 1.7.23 on), Settings → Storage can do that for Legend members. On Mint, SparkBox only accepts a drive mounted under /media, usually /media/<your username/<drive name, and the folder name can't contain spaces. To narrow down the error, tell me which screen showed it: Jellyfin's add-library screen, or the Storage page in SparkBox. There's no need to paste the path. What our assistant knows about adding drives has been corrected so it doesn't happen to the next person.
Allenhaus1 wrote:
Jellyfin's add-library screen,
Chris wrote:
Thanks, that narrows it down. That message comes from Jellyfin's own add-library check. Jellyfin can only browse folders that SparkBox has connected to it, and a USB drive mounted on the desktop isn't one of them until SparkBox is told to use it. One check next: open SparkBox, go to Settings → Storage, and tell me whether your USB drive is listed there with a "Use this drive" button. A yes or no is enough, and please don't paste the folder path. If there's no Storage tab under Settings at all, tell me that instead and I'll point you the other way.
Allenhaus1 wrote:
for some reason my legend status shows on the hone screen but when when i go to dashboard to V2 it doesnt see this
Chris wrote:
Thanks, Allenhaus1. A Legend status that shows on the Home screen but not in V2 is worth pinning down. It may also be why the USB drive isn't listed under Settings → Storage yet, since Storage is a Legend-only page. One check: reload the V2 page once (Ctrl+F5 on Windows or Linux, Cmd+Shift+R on a Mac), open Settings, and tell me what the "Your License" section shows: LEGEND, LICENSED, or no badge. No license key is needed, so please don't paste one.
Allenhaus1 wrote:
when I ran Jellyfin before it saw all but i wanted to automate thats why I chose this configuration and paid for the whole package. I am 20years ago in programming experirnce, been retired a while. Don't mean to sound like im complaining just letting you know I am 1 step above on a stupid rookie scale.
Allenhaus1 wrote:
Reset and my legend status fixed. All drives are shown. Now I need to figure out how to point the libraries in Jellyfin and other apps at the mounted usb drives
Chris wrote:
Glad the Legend status is showing now and your drives are listed. That was the blocker. Next step: in Settings → Storage, press "Use this drive" on the USB drive you want your media on. That gives Jellyfin read-only access to it. Then, on Jellyfin's add-library screen (the one that showed the error), browse to the /storage folder and choose the folder for that drive. Jellyfin only gets read-only access, and download apps never see the drive. Plex and Emby can use it the same way. One check: does Jellyfin's add-library screen now list a folder under /storage? A yes or no is enough.
Allenhaus1 wrote:
If I rename the Drives (Plural). and pick let my apps see it nothing happens and it goes back to the let my apps see it state. I haven't picked Make it my media folder yet because of warning that all addressing would change
Chris wrote:
Sorry, my last step left out a button. After 'Use this drive', the drive's form has a second button, 'Let my apps see it'. That is the button that gives Jellyfin, Plex or Emby read-only access, so use it rather than 'Make it my media folder'. The name you type is only a label, so renaming is not what's stopping it. On recent versions, pressing 'Let my apps see it' can first open a 'Confirm your password' box. It wants your SparkBox dashboard admin password, the one you use to sign in to the dashboard, not a Jellyfin password. If that box is closed with Cancel, Escape or a click outside it, nothing is applied and the screen goes back to the same state. That is my most likely explanation for what you're seeing, but I haven't confirmed it on your box. Please leave 'Make it my media folder' alone for now. It changes the folder all your apps use, which is why it warns that addressing would change. One check: press 'Let my apps see it' again. Did the 'Confirm your password' box appear? A yes or no is enough, and please don't type your password here. What our assistant knows about adding drives has been corrected, so this doesn't happen to the next person.
Allenhaus1 wrote:
followed to the letter, put in password, then I get a little red dot in the corner that says "SparkBox could not apply the change. Your apps keep what they had." I have also opened the drive permissions wide open in Linux
Chris wrote:
Thanks for trying each step, and I'm sorry. My guess that the password box was the problem was wrong: you got past it, so the password is not what is failing. The red dot means the save step itself failed. The message doesn't say why, so we need one more check. When a save fails, SparkBox puts everything back: your apps keep what they had and the drive comes off the list. Please also set the drive's Linux permissions back to how they were before, or to the narrowest setting your user can still read. SparkBox doesn't change the permissions on a drive and doesn't need it open to everyone. Please don't run any other permission commands for now. One check: in a terminal on the box, run sudo sparkbox storage apply and tell me the last line it prints. Only that line is needed, with no paths or drive names. What our assistant knows about this step has been corrected, so it doesn't happen to the next person.
Allenhaus1 wrote:
sudo sparkbox storage only returns: [ERROR] scripts/storage.sh is missing or not SparkBox's own (it must be root's and not writable by others). Run: sudo sparkbox update I ran sudo sparkbox update it gave no change
Chris wrote:
Sorry, the message points you at sudo sparkbox update, which is the wrong command for this. Update only refreshes the app images. It does not replace SparkBox's own files, so running it again could not change anything here. What the error means: the storage part of SparkBox only runs its helper scripts when they belong to root and no other user account can write to them. On some installs those files were left owned by a regular user account, and the storage feature refuses to run them. The upgrade reinstalls those files with the correct owner. One check, which changes nothing: run sudo sparkbox upgrade --check and tell me the last line it prints. If it shows a newer version than the one you have, the next step is sudo sparkbox upgrade. If it says you are already on the latest version, tell me that line and we will look at the file owners instead. Also a correction to my earlier note: Mint is not limited to /media. SparkBox accepts drives under /mnt, /media, /srv, /data and /home. Folder names still cannot contain spaces. What our assistant knows about this step has been corrected, so it does not happen to the next person.
Allenhaus1 wrote:
this is what the last few lines states: [SparkBox] SparkBox installed to /opt/sparkbox [SparkBox] Upgrade complete. Dashboard preserved its previous login. [SparkBox] Your ship is ready — welcome to the Fleet. Dashboard: http://192.168.0.88:8443
Chris wrote:
Thanks for pasting those lines. The upgrade ran all the way through. That step resets SparkBox's own helper files to root's ownership, which is what the storage check was refusing. One check: run sudo sparkbox storage apply again and tell me the last line it prints. Only that line is needed, with no paths or drive names. If the drive's permissions are still open to everyone from earlier, please set them back the way they were.
Allenhaus1 wrote:
OK] Storage: apps already see the drives you chose. It seem to be working now thanks Ill try to get all done fom
Chris wrote:
Good, that last line is the one we were looking for: your apps can see the drives you chose. Thanks for working through the steps one at a time. Before you finish, please set the drive's permissions back the way they were if they were opened to everyone during the troubleshooting. If the drive or its apps drop out again, reply here with the last line of sudo sparkbox storage apply and we'll pick it up from there.