2024-04-17, 12:09 AM
From experience, Jellyfin will still try to find online metadata and overwrite existing NFOs. The only way to ensure it doesn't do this is to make them read only for the jellyfin service user.
This stackexchange post should answer you question about ensuring a mount exists before starting a service.
https://unix.stackexchange.com/questions...g-services
This stackexchange post should answer you question about ensuring a mount exists before starting a service.
https://unix.stackexchange.com/questions...g-services
Jellyfin 10.9.2
Ubuntu 24.04 LTS (bare metal)
Intel i3 12100 on Asus Prime H610M-E D4 mATX
32GB DDR4-3600
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
WD Green 3TB (Samba shares)
WD Red 3TB CMR (WIP Media, Test libraries)
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
Fractal Meshify 2
Corsair CX430
Ubuntu 24.04 LTS (bare metal)
Intel i3 12100 on Asus Prime H610M-E D4 mATX
32GB DDR4-3600
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
WD Green 3TB (Samba shares)
WD Red 3TB CMR (WIP Media, Test libraries)
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
Fractal Meshify 2
Corsair CX430