• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting SOLVED: (Ubuntu) user permissions

    Pages (2): 1 2 Next »

     
    • 0 Vote(s) - 0 Average

    SOLVED: (Ubuntu) user permissions

    Can't copy media to my external media drive
    mjpatey
    Offline

    Junior Member

    Posts: 20
    Threads: 4
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #1
    2024-10-19, 05:57 PM (This post was last modified: 2024-10-23, 02:05 PM by mjpatey. Edited 2 times in total.)
    I'm running Jellyfin Server on Ubuntu 24.04 with my media files on an external exFAT hard drive, mounted in /media/Media. Jellyfin can see the files, navigate through them, and write new files to the drive.

    But I can't copy a new media file to the drive myself, so I need to set up the proper permissions. If I do this:

    Code:
    chmod -r 750 "/media/Media"

    ...will that allow both me and Jellyfin to do what we need? It looks like my Jellyfin installation did create a "jellyfin" user, per this line in /etc/passwd:

    Code:
    jellyfin:x:122:124:Jellyfin default user,,,:/var/lib/jellyfin:/bin/false

    I've never gone this deep into this sort of thing, so thanks for any insight!

    EDIT: I have read TheDreadPirate's excellent primer, but I'm still having a hard time wrapping my brain around it. All subfolders of the drive are currently set to:

    Code:
    drwxr-xr-x
    Go to solution
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-10-19, 10:05 PM
    exFAT does not support Linux permissions. You have to add "umask=0002" to the fstab options for your exFAT drive. Then reboot or umount/mount.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    mjpatey
    Offline

    Junior Member

    Posts: 20
    Threads: 4
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #3
    2024-10-19, 10:30 PM
    @TheDreadPirate thank you again. I just tried doing that, and rebooted. I'm sure I have something wrong... here's the line with the "umask=0002" added:

    Code:
    UUID=6646-2F9B /media/Media exfat defaults umask=0002 0 0

    I googled a bit to see where it's supposed to go, and it looked like that was the place to put it. Hoping I'm wrong because it's not working yet.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2024-10-19, 10:35 PM (This post was last modified: 2024-10-19, 10:35 PM by TheDreadPirate.)
    Comma separated options.

    Code:
    UUID=6646-2F9B /media/Media exfat defaults,umask=0002 0 0
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    mjpatey
    Offline

    Junior Member

    Posts: 20
    Threads: 4
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #5
    2024-10-19, 11:42 PM
    @TheDreadPirate, made the change but I still can't copy a file onto the drive (even a small one). ls -l returns this for the drive and all subfolders:

    drwxrwxr-x
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2024-10-20, 12:12 AM
    Add "noperm" to the end of the options?

    UUID=6646-2F9B /media/Media exfat defaults,umask=0002,noperm 0 0
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    mjpatey
    Offline

    Junior Member

    Posts: 20
    Threads: 4
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #7
    2024-10-20, 01:04 AM
    @TheDreadPirate that made the drive inaccessible. Error screenshot is below:

       

    I could temporarily move all the media to another drive, reformat this drive to another file system format, and move the media back. If I were to do that, what would be the best option in Ubuntu, and is there a good one that would still be readable/writable by Windows and Mac? I thought that was exFAT, but it certainly seems not to be the case for this kind of thing.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #8
    2024-10-20, 01:39 AM
    Yes, if you have the space and you're sticking with Linux, formatting to a Linux compatible FS is ideal. EXT4 is the go-to.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    mjpatey
    Offline

    Junior Member

    Posts: 20
    Threads: 4
    Joined: 2024 Sep
    Reputation: 0
    Country:United States
    #9
    2024-10-22, 03:20 PM
    @TheDreadPirate I copied all the files to another ExFAT drive and have now reformatted my Media drive as EXT4. It's currently empty. I've added the following line to /etc/fstab, based on the drive's new UUID:

    Code:
    UUID=d38f8fcf-1a16-4988-8000-bca2b02efb55 /media/Media ext4 defaults 0 0

    So far it doesn't allow me to write to the drive; I can't copy a file to it. I haven't gone into Jellyfin yet because I want to make sure it's all working properly first.

    In Nautilus, oddly, it shows up simply as "2.0TB Volume" (no name given) but upon hovering, it correctly shows the mount point as /media/Media. In Properties, it shows the following permissions:

    Owner: root (can create and delete files)
    Group: root (access files)
    Others: (access files)

    What's the correct permissions setup for Jellyfin and my user to be able to write to the drive, and can you tell me the specific command or fstab line that will do this?

    Also, is it a problem that Nautilus isn't displaying the name of the drive in the drive list (just "2.0TB Volume")?

    Thank you again for helping me trudge through this.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #10
    2024-10-22, 03:57 PM
    Make sure that you have sufficient permissions to /media/Media. It is probably owned by root with 755 permissions.

    Code:
    sudo chown yourUser:jellyfin /media/Media
    sudo chmod 750 /media/Media
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    Pages (2): 1 2 Next »

    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode