+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Media Scanning & Identification (https://forum.jellyfin.org/f-media-scanning-identification)
+---- Thread: jellyfin cant access external drive on linux (/t-jellyfin-cant-access-external-drive-on-linux)
jellyfin cant access external drive on linux - bac0n0 - 2025-02-21
ive been trying to allow jellyfin access to the external hard drive. I go to the localhost control panel and look to add the drive folder but jellyfin cant even see the drives directory.
I have mounted my external hardrive in fstab to home/pirate/storage. ( yes i know its not good to mount to your home folder, i don't care, unless its the problem)
UUID=773EE99261AB03BC /home/pirate/storage ntfs defaults 0 0
It seems like no matter what I do the external drive is owned by root.
$ groups jellyfin
pirate media jellyfin
$ groups pirate
wheel lp sys network power autologin pirate
ill be honest, im not very good with the terminal, iv been playing with chown and chmod to try and give jellyfin access to my external drive.
I appreciate anyone's help and thank you
RE: jellyfin cant access external drive on linux - bitmap - 2025-02-21
So I don't think chown and chmod will work with an NTFS drive without some additional kajiggering.
I would add options to fstab regarding your user and/or default file permissions on mount. This guide seems like a good place to start: https://linuxconfig.org/changing-file-permissions-on-ntfs-partitions-in-linux.
Ignore installing ntfs-3g unless you have an ancient kernel (uname -r will show you kernel version). The guide has options for dmask and fmask, though I have also seen umask used as part of mounting. I would follow the guide, as it seems trivial to add the information there to fstab and remount.
RE: jellyfin cant access external drive on linux - LinuxGeek28 - 2025-02-21
You don't mention how you installed Jellyfin. If you didn't install it directly on the host, you may have additional permissions issues with running in a container/flatpak/snap/etc. There are ways to grant permissions to non-standard locations for each of these.
If you did install Jellyfin directly on the host, only after you've mounted it, you should be able to change permissions on the directory. My experience in Ubuntu has been you need to create the directory, mount it with fstab the first time, then sudo chown to the desired owner.
It's also a good idea to store files in a subdirectory of the mount point. This way, if the mount point becomes disconnected, your app does not assume you've deleted all the files and auto update your library. Instead, if the mount point becomes disconnected, you should get a directory not found error. At least that's the way my other apps work...
RE: jellyfin cant access external drive on linux - bac0n0 - 2025-02-22
(Yesterday, 06:15 PM)LinuxGeek28 Wrote: You don't mention how you installed Jellyfin. If you didn't install it directly on the host, you may have additional permissions issues with running in a container/flatpak/snap/etc. There are ways to grant permissions to non-standard locations for each of these.
If you did install Jellyfin directly on the host, only after you've mounted it, you should be able to change permissions on the directory. My experience in Ubuntu has been you need to create the directory, mount it with fstab the first time, then sudo chown to the desired owner.
It's also a good idea to store files in a subdirectory of the mount point. This way, if the mount point becomes disconnected, your app does not assume you've deleted all the files and auto update your library. Instead, if the mount point becomes disconnected, you should get a directory not found error. At least that's the way my other apps work...
I think its because of the ntfs partition like other person said. I didn't know ntfs would have those issues. I installed jellyfin from the aur repository for manjaro.
(Yesterday, 04:32 PM)bitmap Wrote: So I don't think chown and chmod will work with an NTFS drive without some additional kajiggering.
I would add options to fstab regarding your user and/or default file permissions on mount. This guide seems like a good place to start: https://linuxconfig.org/changing-file-permissions-on-ntfs-partitions-in-linux.
Ignore installing ntfs-3g unless you have an ancient kernel (uname -r will show you kernel version). The guide has options for dmask and fmask, though I have also seen umask used as part of mounting. I would follow the guide, as it seems trivial to add the information there to fstab and remount.
thank you, I will definitely take the time to read that soon. I had no idea that ntfs was treated different