+- 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: New install library scan issues (/t-new-install-library-scan-issues)
New install library scan issues - Tyler Smith - 2025-10-17
I'm redeploying a new instance of Jellyfin, I've tinkered with it on other devices but it was always slow and unresponsive, so I decied to try with a dedicated device. I installed ubuntu server on a mini PC with an N100, 12GB ram and a nvme drive, so it should run smoothly for basic operations. Install went fine, but I've added my network media drive and ran the library scan. In the dashboard it says it finished the scan, and in the logs I don't see any issues with permissions, but nothing is showing up under movies or music. My home videos somehow all got tagged as "Austialian's funnies home videos" (I'm in the US), and a lot of my shows were misidentified as some random asian shows. The last few times I ran Jellyfin I never had issues like this, and I'm still not sure why none of my movies are showing. I get that it would time to build the metadata but it's not showing anything. What am I missing?
https://imgur.com/a/T9jVQ7t - example of weird tagging.
RE: New install library scan issues - 34626 - 2025-10-17
Is Jellyfin running in docker, the .deb or repo method?
It sounds a lot like missing permissions, when you tested it earlir, did you also access the media over NFS/SMB?
My Jellyfin instance runs great on a Intel Nuc N5105, so it sounds like there is something you havent configured correctly.
RE: New install library scan issues - Tyler Smith - 2025-10-17
I did the direct to host install using the repo "curl https://repo.jellyfin.org/install-debuntu.sh | sudo bash" The last time instance was a smb share, and this one is an nfs to make it easier to work with linux. I'm not seeing permission issues in the Dashboard log. Would that be logged somewhere else?