Energen

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

Well after a bunch of messing around I'm back to Kodi 16 and still have this issue. I can't figure out where the issue is but since I didn't have the problem with FreeNAS I'm thinking it's something with unRaid, although apparently nobody else has issues like this. I just don't know what to do at this point. I can't pause a video without it crashing. It's as though the connection to the SMB share is lost by the time I press play again, as though unRaid is dropping the open connection and therefore killing the stream. I've been using OpenElec and LibreElec to build the database but neither of those should be effecting the end-device play-ability, I created a custom VM to run the latest version of LibreElec to try and use the latest dev build of Kodi on the device that I thought had fixes for SMB in it, but ultimately still had the crashing issue. Nothing seems to work, and again now that I've changed so much stuff all at once I don't know if it's a hardware or software related problem. Maybe the Kodi forums are a better place for troubleshooting, but is it Kodi or is it unRaid that is the problem? I can't say for sure.

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.

You won't go wrong with an APC or a CyberPower. My first UPS was a CyberPower CP1500AVRLCD purchased in 2011, and it's still going, still with the original battery. No problems whatsoever. When I went with a server setup, on FreeNAS, I couldn't quite get the UPS to play nicely with 2 computers... despite all sorts of attempts I couldn't really get two pcs running off one UPS where I felt confident that they would both shut down in a power outage, so I opted to just bite the bullet and buy another UPS just for the server (small cost compared to the money spent on hard drives). I picked up a CyberPower LE825G for $56 on sale at Newegg in January of '17. They are both simulated sine wave and both have AVR. For the specs and prices CyberPower has always fulfilled my needs, apparently. I looked at APC units but for one reason or another I didn't get APC. For the second UPS if I had come across a decent APC on sale I would have picked up it, but it just so happened that CyberPower was on sale and that's what I got.

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

Did you upgrade to 17 from 16? It seems only fresh installs of 17 experience the problem. Here's a post from the kodi forums where a user tried a few different installation methods and the results he experienced.. I'll try a couple things to see if I can get this resolved but ultimately it looks like I may have to revert back to 16. While typing this sentence though, my test stick with 16 was paused, and I just pressed play, and it started to buffer but now it's frozen. And then crash. So, hmm..

Actually, this seems to be directly related to a bug(s) in Kodi 17 now that I was able to search for a connection timeout error message. Although I'm surprised nobody else here has experienced this if they are on 17 as well?

Generally, about as long as it takes to go to the refrigerator and refresh a drink. 30 sec to a couple minutes on average. I just fired up one of my old Fire TV sticks with Kodi 16 and it is not experiencing the same problem, but it's not loaded up completely with all the shares, though I don't see that making a difference. Doesn't have all the addons, etc, either. Edit -- I just turned on the stick I was watching last night and although my database was destroyed (maybe because of the old stick I just tested?) my shares were still set up so I started playing a file and paused it... played it and this time I received a pop up error message, connection timed out. So it would appear that the SMB connection is timing out somewhere/somehow and that's why the pause is having a problem. Where do I address connections that time out? Never experienced this before... I had my FreeNAS set up with a shared db and never had anything time out.

Hey guys.. new to unraid, came over from freenas because I liked unraid's gui better and apps/docker options.. as well as the ability to mix drive sizes.. everything is basically going good until now. I set up fresh Kodi 17.1 installs (where they were previously 16.x) on my Fire TV sticks and got them all set up how I wanted them.. connected my SMB shares from unraid and everything was good. Centralized db with Mariadb on unraid (after I finally figured out how to get that going ;)) Then I pause a movie. When I start to play the movie again it might play for a couple seconds and then it will "crash" out of the movie back to the kodi menu. When I play the movie again it generally doesn't resume from the same spot. This happens every time I pause. I enabled kodi buffering with around 60mb of cache but that didn't solve the problem. I'm not sure where to even begin looking to try and fix this, there's so much new stuff since my freenas box was running without issues. I have a new motherboard/cpu combo running now, Kodi 17.1 versus 16.x, unraid vs freenas, etc. But this seems like a pretty specific problem that I haven't been able to find anyone else experiencing on these forums. Any ideas where to start? Kodi streaming is a major part of what the server is used for, so it has to be resolved. Perhaps I'll put one device back on Kodi 16 and see if it still happens. Thanks.