2024-10-12, 03:34 AM
(This post was last modified: 2024-10-12, 07:05 AM by kowkow. Edited 14 times in total.)
I've just started using Jellyfin. The server runs on a Win10 desktop, and I am accessing the content on this machine itself as well as from two Android tablets.
The source media files are in two locations : some are on a USB hard drive connected to the desktop, and some are directly from the C drive (screenshots).
The initial setup went very smoothly, adding movies as the initial Library, and also grouping multiple episodes into Collections.
I then started adding various Image folders as individual photo Libraries (artbooks, screenshots), and this too went well initially.
However I suddenly started to have issues : first, getting an error when adding a folder as photo Library :
However despite the warning the Library gets created anyways ... but it is empty. Right-clicking it and performing "Refresh Metadata" properly populates it ... but only in some cases, as I have some libraries that straight up refuse to show anything at all.
And then, I am unable to delete such Libraries :
But what does this *actually* mean ? What *exactly* is this so-called "Media" folder ? Sure enough this isn't the actual folder containing the source media files on the hard drive, since I certainly do not want these source folders/files to be written to, let alone deleted (obviously !!!). So why would there ever be such a warning message ? Is this something related to the Library definitions in jellyfin\root\default ? But why would there suddenly be a need for some permission to delete these ?
In practice, what is the process to delete these libraries when getting this error (both from the Jellyfin interface, and manually in the database) ? Bruteforce deleting the .mblink, .collection and .xml seems like an obvious thing to do, but that doesn't tell me how to delete the actual topmost reference to a library in the main DB as these manually deleted Libraries remain listed in the home listing.
Overall, these blocking issues + the lack of clarity in the distinction between actual media files and their references in the Jellyfin DB are quite worrisome.
Also, I see that the function to remove something from a Library is called "delete Media" ; but in some cases it seems to literally delete the source media file from the drive (!), while in others it seems to only delete entries from the DB. I think this is very confusing, and dangerous.
Thank you for your help.
The source media files are in two locations : some are on a USB hard drive connected to the desktop, and some are directly from the C drive (screenshots).
The initial setup went very smoothly, adding movies as the initial Library, and also grouping multiple episodes into Collections.
I then started adding various Image folders as individual photo Libraries (artbooks, screenshots), and this too went well initially.
However I suddenly started to have issues : first, getting an error when adding a folder as photo Library :
However despite the warning the Library gets created anyways ... but it is empty. Right-clicking it and performing "Refresh Metadata" properly populates it ... but only in some cases, as I have some libraries that straight up refuse to show anything at all.
And then, I am unable to delete such Libraries :
But what does this *actually* mean ? What *exactly* is this so-called "Media" folder ? Sure enough this isn't the actual folder containing the source media files on the hard drive, since I certainly do not want these source folders/files to be written to, let alone deleted (obviously !!!). So why would there ever be such a warning message ? Is this something related to the Library definitions in jellyfin\root\default ? But why would there suddenly be a need for some permission to delete these ?
In practice, what is the process to delete these libraries when getting this error (both from the Jellyfin interface, and manually in the database) ? Bruteforce deleting the .mblink, .collection and .xml seems like an obvious thing to do, but that doesn't tell me how to delete the actual topmost reference to a library in the main DB as these manually deleted Libraries remain listed in the home listing.
Overall, these blocking issues + the lack of clarity in the distinction between actual media files and their references in the Jellyfin DB are quite worrisome.
Also, I see that the function to remove something from a Library is called "delete Media" ; but in some cases it seems to literally delete the source media file from the drive (!), while in others it seems to only delete entries from the DB. I think this is very confusing, and dangerous.
Thank you for your help.