Library Disappears

[pcaddict]

Hi there,
I'm running Jellyfin 10.10.6 in a TrueNAS 24.10.2 container (provided by TrueNAS). The app pool is on an NVMe SSD, while media is on separate pools.
Issue:
Every so often, all media libraries disappear from Jellyfin without an obvious cause. Here’s what I’ve observed:

• The issue appears to happen around the time new media is scanned into the library.
  
• Initially, cover art disappears from items on the homepage.
  
• In the Jellyfin dashboard, under Libraries, all libraries are gone.
  
• The "Scan Media Library" scheduled task fails.
  
• Running an integrity check on both the
  jellyfin.db and library.db returns no errors.
  
• Logs don’t indicate corruption or failure to load the database. However, metadata errors appear, and I noticed that the metadata folder is significantly smaller than usual.
  
• The only way to restore functionality is reverting to a snapshot of the dataset used by Jellyfin.
  

Troubleshooting Attempted:

• Checked filesystem integrity – no issues.
  
• Removed and reinstalled Jellyfin and its dataset multiple times.
  
• Verified that *arr apps do not have direct access to Jellyfin.
  
• Examined logs but haven’t found anything obviously indicating database corruption or deletion.
  

The following log: 20250322.log shows where the problem occurs. 
If anyone has ideas for troubleshooting this further, I’d greatly appreciate your help!

[TheDreadPirate]

Can you share how Jellyfin is configured in TrueNAS? Specifically where you've mounted /config and /cache. It sounds like you've co-mingled /config and /cache in the same folder instead of creating separate folders for each. If my assumption is correct, the cache cleanup job is essentially wiping out any permanent config files that are not currently in use. So things like your databases will remain, but library configs and images will be "cleaned up"

[pcaddict]

Can you share how Jellyfin is configured in TrueNAS?  Specifically where you've mounted /config and /cache.  It sounds like you've co-mingled /config and /cache in the same folder instead of creating separate folders for each.  If my assumption is correct, the cache cleanup job is essentially wiping out any permanent config files that are not currently in use.  So things like your databases will remain, but library configs and images will be "cleaned up"

Your assumption is correct, I had the config and cache folders mapped to the same directory. I've redeployed the app with cache in its own folder and will see how it goes. Thanks for taking a look.