Energen

Apologies if this has been asked/answered before, but is it advisable or not to preclear multiple drives at once? Does running the script on more than one drive at a time significantly reduce the performance of each individual operation? Got 2 drives preclearing now, at about 21 hours I'm "Pre-Read (2 of 3): 8% @ 152 MB/s (0:28:24)" and "Post-Read: 93% @ 114 MB/s (6:48:22)" on the second drive. (not sure if it's 1 of 3 or 2 of 3)....) Decided to add two 3TB drives that were on sale @ newegg, and further decided to use this script on them.... just getting impatient

I had this same problem, I seemed to have resolved it by deleting the folder appdata\mariadb\log and starting the docker again.

That seems to have done the trick, thanks.

Hi Squid, Came across a small issue I can't seem to resolve. The plugin wants to clean "Maria-WebSQL: /mnt/user/appdata/", because I went back and forth between Maria-WebSQL and just MariaDB, however that folder/path does not exist; yet the plugin continues to want to clean it. How/Where might it be detecting this path when it is not on the filesystem? Is it confusing mariadb with mariadb-websql because/if/maybe my mariadb-websql docker was named mariadb? Is there another place where that symbolic name would be referenced that I can edit? Thank you

So I don't know happened but I configured this, created a backup, and then found out that all of my appdata was wiped. My LibreElec vm configuration is gone (the vm itself works, but the libreelec kodi settings are gone), mariadb databases and configuration, Emby Server, Plex, all configurations and databases are gone. And even though the backup was "successful", the backup has none of those files that are now gone. I didn't change anything in the settings other than the source appdata location and the destination backup location so I don't see how this could have been my fault. Off to rebuild everything, after uninstalling this plugin.

Just wanted to chime in that I had to do this step as well to get the recycle bin working. Don't know if there's a way to do this automatically when the plugin is installed, or if that's just bad form to do automatically, but seems to be a required step. Perhaps add the command to the plugin install info or something? Thanks for this, very useful plugin.

Hey guys, got a couple questions that are going to seem dumb to all of you.. I'm still getting used to unRaid so bear with me Trying to set up this plugin, in the settings the very first option is the appdata share to set up My appdata share was not listed automatically, so I did go ahead and install the linked plugin (user scripts), but the link to the "in conjuction with this" was invalid, so I don't know what it's pointing to.. I didn't see any scripts anywhere that sounded like it related to this....... if it's still needed? Second, looking at the help for the backup plugin, it states Bold font added for emphasis. Is this just an outdated instruction? My appdata was not listed, do I just put in the /mnt/cache/appdata? or because it was not listed automatically this plugin will not work? Just trying to explore all aspects of unRaid and using plugins, I probably don't need my appdata backed up, but if I can do it then why not just go ahead and do it? This might not be the correct place to ask about something different, but are there any plugins or methods to back up the entire unRaid configuration? All settings, what plugins are installed, etc? Those are not included under the appdata umbrella that this plugin backs up, correct? Thank you for indulging me

Thanks Squid, very helpful. It appears that in the nightly builds of Kodi 17.x they have fixed that SMB issue from my other thread, so I'm going to look at redoing everything on those nightly builds and perhaps put Kodi into my windows vm.

Hey guys.. read through a lot of the pages in this thread trying to determine what the practical usage is for a headless kodi. I haven't really been able to determine what it's use is. I understand that it will keep the database updated with changes to the media, right? What's the practical use of that when every kodi-client will still have to do a library update to get the new media listed? Am I missing something here? I've previously used a shared db via advancedsettings.xml to remember play/watch status, but that didn't change anything about not having to scan for new files on each device. I guess I can't say for sure whether or not if I scanned on one device if any new files showed up on the second device without scanning --- I imagine that's what is supposed to happen? And by virtue of the headless scanning for library changes any other device will already be updated? Does Kodi, when you start it up, scan the remote database for changes automatically? It's not something I've noticed... Sorry for the newb-ness of the question, it's probably an obvious answer.. Also I imagine that this would essentially be the same as having kodi running in a windows vm updating the remote database rather than the headless docker? I've already got a windows vm running for another task, it would be just as easy to run kodi in there rather than this headless thing I'm not too sure about.. Thanks for indulging me