2024-04-16, 02:00 AM
(This post was last modified: 2024-04-16, 03:49 AM by Babamania. Edited 2 times in total.)
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!!
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 0E0E1C4F5DD13F47