thedinz

https://github.com/thedinz/KAM KAM is a small web app that makes Kometa/Plex artwork management painless. It lets you upload artwork for movies, TV series, seasons, and collections and will: Import existing Plex assets — movie posters/backgrounds, series posters/backgrounds, and season posters — into your mapped Kometa assets structure Convert uploads to .jpg Replace existing poster.*, background.*, or SeasonNN.* in the correct asset folder Keep everything in the same structure Kometa expects Provide a simple web UI with a fallback image to quickly spot missing artwork ⚠️ Important constraints What this means in practice: Pick one assets root for a given library and stick with it. If you have multiple libraries, each should have its own mapped directory or its own container. Put all Collections in a single Collections directory under one assets root. Required Kometa settingsFor KAM to function properly, Kometa needs to be configured to create and manage asset folders ahead of time. In your Kometa configuration (example shown for Movies), make sure these settings are enabled: Movies: operations: assets_for_all: true assets_for_all_collections: truesettings: create_asset_folders: trueWhy this is requiredKAM does not create folders. It only places artwork into existing Kometa asset folders. These Kometa options ensure asset folders are created automatically for every movie, show, and collection. Once the folders exist, KAM will safely upload and replace artwork inside them. ⚠️ If the folders don’t exist first, uploads from KAM will fail. ⚠️ REMEMBER, this is an addon for Kometa, not a stand alone application. Paths: avoid /mnt/user (FUSE) for hot I/OUnraid’s /mnt/user uses a FUSE layer (shfs) that’s noticeably slower for lots of small file ops (like checking asset folders) and can incur spin-up delays across disks. Fix: map your volumes to the cache SSD directly (or a single disk) for KAM’s hot paths: Use /mnt/cache/... (preferred) or /mnt/diskX/... instead of /mnt/user/.... In your Unraid template, bind: /mnt/cache/appdata/kam:/config /mnt/cache/kometa/assets:/assets (or wherever your Kometa assets live) Also: ensure the share(s) backing those paths are set to Use cache: Prefer/Only so mover doesn’t push them to the array. Please visit the github page for more information

that would explain it, i will reach out to the DEV about possibly changing the back end to not format them that way.

Just windows explorer SMB share. If i go up and into another folder in appdata everythign is normal.

I have tried matching owner and permissions as other folders that work fine but if you look at the attached sreenshots the files in the SMB share do not even present the same as in the unraid WebUI. I am at a loss as to why.

actually follow up question, if my flash backup is from today, and the flash is having issues, is it safe to use it?

understood, ill prepare a new one now and plug it in when i get home. Thank you kindly.

Its happening pretty regularly so didnt take long for me to be able to grab the logs, here they are. tifa-diagnostics-20250218-1023.zip

This happened overnight while i was asleep, i use docker in directory mode. If i reboot the server things seem normal but after an unknown amount of uptime it will say this, then i reboot and all is well again. I dont know what to do here to fix this or why it just happened so suddenly

how do i get the onlyoffice secret? i read the instructions, did i just overlook it?

Same here but i am running another instance of mySQL and wondering if thats why the conflict

Hello, with only office is there anyway for me to change the port for mySQL as its conflicting with an other instance im running.

It seems the fix from what i read is to replace the bz files on the flashdrive from the same version i run. I run 6.12.8 https://docs.unraid.net/unraid-os/download_list/ I dont see that version to download, what do i do?

Yeap, bye bye to this plugin, not deaing with this. Sometimes old school wins, just gonna write down the locations of the disk using acient tools know as paper and pen.

pigallery2 will not even start for me, it starts and stops and there are 0 logs so i really have no idea where to start.

Ok fair enough, i just change it from array the proper cache drive and for now i will consider this resolved.

Is it normal for the system to keep making shares on its own? So part of the fix was i moved the nextcloud appdata from cache_nextcloud/appdata to cache_nextcloud/config and now i have a new share called config that i didnt create. And of coarse if i delete it, there goes the files too, why did it make this a share? Further more it says the share is on array and not cache_nextcloud

WHAT A NIGHTMARE!! Ok its fixed lol, but talk about stressful, didnt know what i was gonan break aside from everything but i made some changes moved some files now everything is where i want them and none of those errors come up on fix common problems when i do a rescan. I also realize that was a nightmare i created for myself but still not sure what i did wrong to get there.

Ok and thank you for the help and most importantly the patience, i had already moved these files prior to opening the ticket. Problem is the files still exist in the old locations but docker and VM is working FROM the new location, according to the paths in the settings. So in theory, cant i skip the move part and just delete the duplicates?

ah i see your right about all my cache, that i was clearly trying to redesign. Can we focus on this one for a sec Common Problems: Warning: Share NextCloud set to use pool cache_nextcloud, but files / folders exist on the cache pool How would i fix that? it seems easy but like i said i seem to have the share itself pointing to the cache drive of cache_nextcloud and in the nextcloud container its pointing to the cache_nextcloud filesystem.

Understood, here we go... cloud-diagnostics-20240202-1128.zip

Please see the attached screenshot, how can i fix this, cache_nextcloud is the only thing that should be there, i have double checked the nextcloud container settings and nothing is pointing to the main cache only to the new cache, the share it self is set to cache_nextcloud only as well. How do i delete this? and will it delete my files to, inside that nextcloud folder some the of the files say the same thing they belong to both shares. If i go into cache > user > and delete Nextcloud share will it take the files with it that belong in both shares? I hope this makes sense because is breaking my brain to be honest. Not sure how i made such a mess. I have plex running on its own cache drive too with its own share and this is not an issue, again, not sure how the nextcloud shares got like this but i just want to fix...

I really want to add external storage, NFS share. Doesnt support it but supports SMB Says i cannot install because im missing a component The library libsmbclient is not available. Can i, and if so, how can i add this to my install

Nothing found, i searched high and low, i cant make this share dissapear.

Its not listed there sadly

I have this share mounted in my unraid from when i was using googledrive and rclone but now i cant recall how to get rid of it, i dont use rclone anymore, i uninstalled the plugin, but added it back to see if that would help rid myself of this rouge share mount, i have attached a screenshot, the folder called GDrive-cloud i want to go away, i cannot for the life of me figure out how.