+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: No files will play on clients. (/t-no-files-will-play-on-clients)
RE: No files will play on clients. - damnsignin - 2024-03-16
Because I'm that lost. I've been following guides, reading articles, jumping through manuals and more. It took my two weeks to find instructions for how to mount multiple partitions that are persistent through reboots using fstab and labels because the original Youtube guide for "How to SetUp JellyFin Media Server in 10 Minutes With Raspberry Pi 5 (2024)" only gave the narrowest instructions for setting up with one drive with basic permissions. I've been clawing for answers since my Pi was finally delivered by Sparkfun after four months in January.
All I want is to be able to drag-and-drop files from my PC to the storage on the Pi and then play them over the server to devices in my house. I followed the CasaOS guide because it gave me a GUI for that which I could use, but permission problems got in the way. So I dumped it and moved to trying to use Docker with Docker Desktop to get it done, but now that's more complicated.
I'm just so lost and I'm sorry to vent like this, but I don't know how to get this running because every guide and every recommendation is different and I can't find one clear path to follow to get this set up cleanly.
RE: No files will play on clients. - TheDreadPirate - 2024-03-16
Bruh. Whatever guides you followed are massively overcomplicating this. Probably some "home lab" guides from some rando tech tuber.
https://jellyfin.org/docs/general/installation/linux/#repository-automatic
Literally run this command and jellyfin is installed directly on Debian.
Code:
curl https://repo.jellyfin.org/install-debuntu.sh | sudo bashAdd your media that, I'm assuming, are on external drives that are now mounted via fstab. Done.
RE: No files will play on clients. - damnsignin - 2024-03-16
I ran it and rebooted. Jellyfin is opening as a webpage now.
But I'm having problems accessing the drives. When I open folders to add them to a media library, they lag, and then the mounted partition disappears from the options list.
RE: No files will play on clients. - damnsignin - 2024-03-16
This is showing up on the Pi with head on.
EXT4-fs error (device sdb1): ext4_wait_block_bitmap:574: comm ext4lazyinit: cannot read block bitmap - block_group = 510 block_bitmap = 16252942
EXT4-fs error (device sdb1): ext4_wait_block_bitmap:574: comm ext4lazyinit: cannot read block bitmap - block_group = 511 block_bitmap = 16252943
EXT4-fs (sbd1): shut down requested (2)
RE: No files will play on clients. - TheDreadPirate - 2024-03-16
What kind of external drive is this? A USB bus powered laptop drive or a wall powered USB drive?
RE: No files will play on clients. - damnsignin - 2024-03-16
Three 5TB Seagate Firecuda external drives (https://www.amazon.com/Seagate-FireCuda-Gaming-Drive-External/dp/B08Y1S6R1V/) plugged into a Orico 12v desktop hub (https://www.amazon.com/gp/product/B07XHL5399/), connected to the Rpi5 running on the stock 27w supply.
Everything was running fine before, when I had Jellyfin running with no play access. I'm 99.999% sure all those Docker commands I ran messed up the bitmap for everything and I need to reformat the micro sd card and start from scratch.
My head is absolutely pounding from all this, so I'm gonna call it a week for the this for now. I'll come back on Monday with a fresh install of Pi and all the setup done and see how it works.
Thank you so much again for putting up with my BS and helping me with this. I'm sorry I've made this so difficult.
RE: No files will play on clients. - damnsignin - 2024-03-19
Heylo, just wanted to leave an update that my entire project server is on hold.
It looks like a rolling blackout last week completely screwed up the EXT4 partitions on all three of the hard drives I'm using. I ran S.M.A.R.T. test and sector scans over the weekend and everything came up clear, so until I can afford a UPS to run the Pi server on so this corruption doesn't happen again, I'm pausing any further work on this.
Thank you again for all your help. I'm sorry this was such a long drag to end up with this.