JF folder locations

[noob]

Ok, thank you for your help.

Any suggestions where else to look, what to check?
The "Slow HTTP Response" record does creep up often and around the times when I have the issue.

Thank you.

[TheDreadPirate]

Look in /var/log/messages. It is the system's log file. But it is very verbose and I don't know specifically what to look for.

The slow response messages are generally not helpful due to A) how generic it is and B) even on fast systems they still appear. There is a setting to turn them off so they don't clutter the logs, but its up to you if you want to keep them or not.

Dashboard > Logs > Uncheck "Log a warning message if the server was slow to answer".

[noob]

Hello,

Apologies for absence, had a busy period.

Thank you, will try to sort those logs. I did notice when I was next to NAS that it made a solid continuous trrrr sound (yes, technical description  ) for a second and then had self-rebooted - at the same time when I am crashing JF. So now I think it is to do with the NAS. Is there a limitation on the size of the HDDs disks it can/should work with?

On a separate note, I added folders for animation etc. where the movies, tvseries folders are.

Then I try to add it to a new library, but it just hangs.

What am I missing?

Thank you.

[TheDreadPirate]

You'd have to make sure that the permissions on the new folder matches the other folders. Or that you mounted that folder in the docker compose. Based off of the drop down from the library folder settings you are passing each folder under /data individually (this is fine), so you'd need to add /data/animation to the docker settings.

[noob]

Hello,

Permissions - looks the same as the other, as you said,I created the folder in the same location as the default ones.

Found where to add it to the docker service and rebooted it.

           

Indicated to add " /data/animation" when creating new library in JF dashboard

Still does not find it

[TheDreadPirate]

You have the same source folder mapped to two different container mount points. That's not going to work.

If you have animation movies in the movies folder, you would have to move them to a different source folder.

[noob]

Thank you, will look into that.

Is the "library folder" the one that contains the JF Files (the one that require SSD)?

Thank you!

[TheDreadPirate]

The library folder you configured to map to /config has all of your permanent jellyfin data, including the database. And that should be on a SSD, if possible. Not required, but strongly recommended.

[noob]

Then it all makes sense now, it would explain why is crashes as it is installed on the HDD. I was not sure if these were the JF permanent data or just directory created to where to store media. I will move it. I was thinking to move it to the RPi SD card, it has 50gb. But would it better be on a non-OS SSD? The recommended minimum size is 50GB, any idea on what it is based, would future library size matter as I may have a media library of thousands of titles, over 12TB?

I have been uploading the video files into those /movies and /tvseries folders. I assume that I should not and it is used to store all the metadata for JF to operate?

Many thanks!

[TheDreadPirate]

The size of your library in TB matters less than the number of items since the amount of metadata Jellyfin stores grows with each item added. 50GB is the bare minimum due to the size of the database, the size of the metadata folder (biggest contributor), caching, and then there's the transcode directory, which can grow very large for 4K media. The transcode directory can be relocated in Dashboard > Playback, but by default it is in /config/transcodes.

You can have jellyfin's /config directory on the same drive as your media. Just be aware of how much free space is left. Many, many, users have come here asking how their database got corrupted only to realize the disk is completely full.

Don't feel like you NEED to have the /config directory on a SSD. Many people run it from the SD card in their RPi.