10 hours ago
I'm not sure if this is a problem with the configuration of my Jellyfin library or the Linux server it is running on. In the last few months, I've had some power outages, and I've noticed that, once or twice in that time, my server could not be located by the Jellyfin app or the local website, and I was forced to rebuild the library by rescanning all of my media.
To note, my media is kept on a separate drive from the boot drive, which makes me wonder if maybe the Jellyfin app is spinning up on Docker faster than the mounted drive can be recognized, leading Jellyfin to conclude there is no library where there should be one.
Any suggestions or similar concerns?
To note, my media is kept on a separate drive from the boot drive, which makes me wonder if maybe the Jellyfin app is spinning up on Docker faster than the mounted drive can be recognized, leading Jellyfin to conclude there is no library where there should be one.
Any suggestions or similar concerns?
Rescued from the Trash Optiplex Build
CPU: Intel i5 3470
RAM: 4GB DDR3-1333
GPU: NVIDIA Quadro P400 2GB GDDR5
Boot Drive: Inland Professional 240GB SSD
Storage: Seagate Ironwolf 8TB 7200 RPM HDD
CPU: Intel i5 3470
RAM: 4GB DDR3-1333
GPU: NVIDIA Quadro P400 2GB GDDR5
Boot Drive: Inland Professional 240GB SSD
Storage: Seagate Ironwolf 8TB 7200 RPM HDD
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github){kind=icon}