Jellyfin Forum
Bulk File Deltion Issue - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Bulk File Deltion Issue (/t-bulk-file-deltion-issue)



Bulk File Deltion Issue - Scrat134 - 2025-05-02

Hi there,

Unfortunately this is another 'classic' Jellyfin noob issue I think... Embarrassing.

I still don't understand what's caused this to occur though, hence reaching out here.

I'm running Jellyfin 10.10.7, on a Synology NAS.

It's all been setup working fine, including remote access etc, for a few days, no issues... Until...

About an hour or so ago I ran a Scan Library > Replace All Metadata on one of my libraries...

My thinking was that this would re-baseline everything within nice and fresh, and I could begin polishing from there. However, what seems to have happened is that I waited for the scan to complete, and re-visited the library in Jellyfin to see it's shiny newness, what I encountered was a load of missing folder thumbnails, no problem I thought, I'll Re-scan for missing metadata... No effect. So I then check my actual hard drive, and all of the files (MP4 and JPGs) that previously made up that library are just - gone. Deleted from the hard drive, not in any kind of recycle bin that I can see. Just gone.

So having a look around here, I can see that some people are saying it (Jellyfin) should have read-only access, but I had setup read/write not foreseeing any issue like this... Silly, or trusting, maybe a bit of both?

I also haven't got my Jellyfin cache set to any of my actual mapped library directories....

So, please, can someone advise...

A) What seems to have happened here, as I really am stumped?

B) If there is any way at all this action can be reversed from within Jellyfin or the NAS, or restored from wherever its stuffed my files?

Many thanks

Confounded-face


RE: Bulk File Deltion Issue - bitmap - 2025-05-02

Are you running Jellyfin via docker on your NAS? The ONLY time I've ever seen this is when media libraries are mapped somewhere within the cache/transcode directories. These are meant to be wiped and will hard delete anything inside. More information about how you've installed and where your libraries reside would be helpful.


RE: Bulk File Deltion Issue - Scrat134 - 2025-05-02

No problem.

I’ve not got Jellyfin installed via Docker, but instead via SynoCommunity's repository for the Synology Package Centre.

My media libraries are in my Synology's shared "homes" directory, and are simply 3 directories located within that. They're browsable via File Station etc, or via the mapped drive on my PC etc.

Eg...
/volume1/homes/directory-1
/volume1/homes/directory-2
/volume1/homes/directory-3

My cache / transcode directories etc, are those specified by default upon install, ie, they’re hidden directories I cannot access in a straightforward manner (eg: not browsable via File Station etc). The paths to these are below...

Cache
/volume1/@appdata/jellyfin/cache

Logs
/volume1/@appdata/jellyfin/log

Metadata
/volume1/@appdata/jellyfin/data/metadata

Transcodes
/volume1/@appdata/jellyfin/cache/transcodes

Web
/volume1/@appstore/jellyfin/web

Based on the above, I can't fathom why this has occured.


RE: Bulk File Deltion Issue - Scrat134 - 2025-05-17

I never did get to the bottom of why this happened.

However thankfully, I had a backup, which I rescued my files from.

I have also since reinstalled Jellyfin via Docker / Container Manager on my Synology.

Jellyfin now has read-only access to my files, I do not require it to delete anything, nor do I wish it to.

I assume interaction here stops when SynoCommunity is mentioned lol.


RE: Bulk File Deltion Issue - bitmap - 2025-05-17

Not entirely, but there's not really official support for community containers/installs. I'm not familiar with Synology's ecosystem at all, but screenshots and explanations of how you interact with it are helpful. When talking about container manager, it's basically docker/portainer with a fancy UI that's more confusing than anything (IMO). You can still get help, but you might wait a bit longer for folks more familiar. Using a NAS isn't particularly recommended due to how underpowered they tend to be.