+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: SOLVED: The umpteenth "Jellyfin can't see the internal HDD" thread (/t-solved-the-umpteenth-jellyfin-can-t-see-the-internal-hdd-thread)
The umpteenth "Jellyfin can't see the internal HDD" thread - Babamania - 2024-04-16
Jellyfin is on an Ubuntu server (specifically Ubuntu the desktop, not the GUI-less Ubuntu Server). I seldom ever touch the thing directly and only access Jellyfin via a Windows 10 PC. As with I assume the same with countless others, Jellyfin fresh out of nowhere is unable to see my internal SATA HDD (NTFS format) after the server reset due to some update. The issue came up when setting it up for the first time but the usual chown 777 trick or whatever I forgot I did managed to do the trick. This time, even after remounting the internal storage device, Jellyfin's UI page is blank where I should be seeing my content, some of which I was in the midst of binging.
The path of said drive is /media/<myusername>/0E0E1C4F5DD13F47. When trying to (re)build the media library, Jellyfin only ever gets as far as <myusername> despite being 100% sure that permissions and such are wide open enough that it should see the drive. Not only chown 777 but putting the service user jellyfin in the same group as myself didn't work either, despite the same terminal commands fixing this over a month ago! Did the restart and subsequent unmounting bork everything related to Jellyfin? I say "related to Jellyfin" as Putty and Filezilla can still access it, the latter even be able to swap files (basically the only other way I user/interact with the Ubuntu server) with the drive that Jellyfin somehow cannot see!! How do I fix this?! My schedule's ruined!!
Code:
drwxrwxrwx+ 4 <myusername> <myusername> 4096 Apr 15 21:03 .
drwxrwxrwx 3 root root 4096 Mar 18 22:02 ..
drwxrwxrwx 1 <myusername> <myusername> 4096 Mar 26 15:22 0E0E1C4F5DD13F47RE: The umpteenth "Jellyfin can't see the internal HDD" thread - TheDreadPirate - 2024-04-16
There is an ACL on /media/<yourUserName> (as denoted by the +). You have a couple of options, remove the ACL or manually mount this hard drive via /etc/fstab instead of relying on Ubuntu to auto mount it.
The best option is to manually mount it to ensure this doesn't happen again.
https://help.ubuntu.com/community/Fstab
RE: The umpteenth "Jellyfin can't see the internal HDD" thread - Babamania - 2024-04-16
Thank you for the advice, though I haven't a clue as to what ACL is and thus, no idea how to remove it. I managed to solve it though, at least for now. Used this command I found elsewhere and suddenly the drives became visible to Jellyfin.
Code:
sudo setfacl -m u:jellyfin:rx /media/jasonI'll look into a manual mount, though that link there is quite a lot to take in. The way it seems now whenever the media server reboots I have to click the drive on the file explorer to remount and thus, access it in any way so there doesn't appear to be an auto mount going on. Also odd is that /media/<myusername>/<drivename> is supposedly reserved for removable storage, not internal SATA drives. I used something that isn't GNOME (starts with a G but I forgot the name otherwise) to set things up regarding that HDD. Made it NTFS in case I get so frustrated I go to Windows instead for a media server. Only opted for Ubuntu because it's lighter on very old hardware.