Quick answer
What this guide helps you do
Fix Jellyfin access to USB media drives on Ubuntu. Check mount paths, filesystem type, permissions, fstab options, and reboot behaviour step by step.
Jellyfin beginner path
New to Jellyfin? Follow this order.
These guides form the SmallGrid Jellyfin path: install it, fix folder access, solve empty libraries, reduce unnecessary transcoding, then choose the right mini PC.
- Jellyfin on Ubuntu: Low-Power Setup, Media Folders and Reboot Checks
- Give Jellyfin Access to Media Folders on Ubuntu
- Jellyfin Library Not Showing Files: Fix Scans, Paths and Permissions
- Jellyfin Direct Play vs Transcoding: Differences, CPU Use and How to Check
- Best Mini PC Specs for Jellyfin: What Actually Matters
Difficulty
Beginner-friendly
Focus
Jellyfin setup and troubleshooting
Best used for
Practical setup, fixes, and checks
Quick answer
If Jellyfin cannot access an external USB drive, first confirm where Ubuntu mounted it:
lsblk -f
findmnt
Then test the actual path as the Jellyfin user:
sudo -u jellyfin ls -la /mnt/media
If that returns Permission denied, the fix depends on the filesystem type. ext4 normally works well with ACLs. NTFS and exFAT often require the correct mount options in /etc/fstab.
Step 1: Find the drive and filesystem
Run:
lsblk -f
Look for:
- device name
- filesystem type
- UUID
- mount point
Example:
sdb1 ext4 1234-ABCD /mnt/media
Do not assume the path is /media/username/DriveName. Desktop auto-mount paths can change and may not be suitable for a server.
Step 2: Confirm the drive is mounted
Run:
findmnt /mnt/media
ls -la /mnt/media
If findmnt shows nothing, Jellyfin is not looking at the real USB disk.
A stable server mount such as /mnt/media or /srv/media is easier to maintain.
Step 3: Test access as Jellyfin
sudo -u jellyfin ls -la /mnt/media
sudo -u jellyfin find /mnt/media -maxdepth 2 -type f | head -20
Possible results:
- files listed: permissions are probably fine
- permission denied: fix access
- empty folder: the disk may not be mounted
Use namei to inspect the full path:
namei -l /mnt/media/movies
Step 4: Fix ext4 permissions
For ext4, ACLs are usually the cleanest option:
sudo apt install -y acl
sudo setfacl -R -m u:jellyfin:rx /mnt/media
sudo setfacl -R -d -m u:jellyfin:rx /mnt/media
sudo systemctl restart jellyfin
Verify:
getfacl /mnt/media
sudo -u jellyfin ls -la /mnt/media
Step 5: Fix NTFS or exFAT mounts
NTFS and exFAT permissions are often controlled by mount options rather than normal Linux ACLs.
Check the current options:
findmnt -no SOURCE,FSTYPE,OPTIONS /mnt/media
Find the Jellyfin group ID:
id jellyfin
An /etc/fstab entry may need options such as:
uid=
gid=
umask=
fmask=
dmask=
The exact values depend on which user or group should manage the files.
Test changes with:
sudo mount -a
Do not reboot until mount -a completes without errors.
Step 6: Make the mount persistent
Find the UUID:
lsblk -f
Create a stable mount point:
sudo mkdir -p /mnt/media
Back up and edit fstab:
sudo cp /etc/fstab /etc/fstab.backup
sudo nano /etc/fstab
Example ext4 entry:
UUID=YOUR-UUID /mnt/media ext4 defaults,nofail 0 2
Then test:
sudo mount -a
findmnt /mnt/media
Step 7: Add the correct path in Jellyfin
In Jellyfin, open:
Dashboard → Libraries → Manage folders
Add the stable Linux path, for example:
/mnt/media/movies
/mnt/media/tv
Avoid using a temporary desktop auto-mount path.
Step 8: Reboot and verify
sudo reboot
After reconnecting:
findmnt /mnt/media
sudo -u jellyfin ls -la /mnt/media
systemctl status jellyfin --no-pager
If the library disappears after reboot, use Jellyfin Media Disappears After Reboot.
Related guides
- Give Jellyfin Access to Media Folders on Ubuntu
- Jellyfin Media Disappears After Reboot
- Jellyfin Library Not Showing Files
- Install Jellyfin on Ubuntu
Recap
Find the real mount point, identify the filesystem, test access as the jellyfin user, and make the mount persistent.
Use ACLs for ext4. Use appropriate mount options for NTFS or exFAT.
Jellyfin guide cluster
More Jellyfin fixes and setup guides
These guides link the main Jellyfin setup, permissions, remote access, direct play, and hardware topics together.
Jellyfin on Ubuntu: Low-Power Setup, Media Folders and Reboot Checks
Build a reliable low-power Jellyfin server on Ubuntu. Install Jellyfin, mount storage, fix media access, favour Direct Play, measure power, and verify the server after reboot.
Give Jellyfin Access to Media Folders on Ubuntu
Fix Jellyfin permission denied errors on Ubuntu. Test the service user, find blocked parent folders, apply safe ACLs, verify inheritance, and check mounted-drive options.
Jellyfin Library Not Showing Files: Fix Scans, Paths and Permissions
Fix an empty Jellyfin library when scans find no media. Check storage mounts, paths, Linux permissions, Docker mappings, new-file access, scans, and logs in the correct order.
Jellyfin Docker Permissions: Fix Media Folder Access and UID/GID Errors
Fix Jellyfin Docker permission denied errors. Check bind mounts, container paths, UID and GID values, read-only media access, active mounts, and file visibility step by step.
Jellyfin Direct Play vs Transcoding: Differences, CPU Use and How to Check
Compare Jellyfin Direct Play, Direct Stream and transcoding. Learn how each affects CPU use and quality, why transcoding starts, and how to diagnose it.
Best Video Format for Jellyfin Direct Play: MKV, MP4, H.264 and HEVC
Choose the best video, audio, subtitle, and container formats for Jellyfin Direct Play. Compare MKV vs MP4, H.264 vs HEVC, and avoid unnecessary transcoding.