Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

42 Good

About Fireball3

  • Rank
    Advanced Member


  • Gender
  • Location
    Good old Germany
  • Personal Text
    >> Engage <<

Recent Profile Visitors

2048 profile views
  1. @itimpi May I add my 2 ct. for consideration as you're still in development. Several people are using the S3 standby plugin. The plugin performs some checks to evaluate if it can issue the S3 standby command. Do you think you can use that work to implement the "pause parity" feature in such a way, as to run automatically when the server is running idle? e.g. if there is "low activity" on the NIC or if the "running hours" is the only condition that is blocking the S3 sleep. (Probably need both to be able to stop the check when NIC load goes up again) This would be a very useful feature.
  2. I moved all cards with limited drive size support to the lower table "Not recommended extension boards" some time ago. I use the DELL H310 card (SAS2008 chip) with 10TB drives - no probs.
  3. Yes, depending on your settings for sigs. You can also do a forum search for hardware wiki.
  4. Writing from my mobile. Check my signature and go to the hardware wiki. There is a table with recommended controllers of all kind. Might provide a link later if you dont find it.
  5. You're right, I had my specific setup in mind when I wrote that. If my clients were RPi's, I probably wouldn't mind also.
  6. Of course they aren't. Not even the server is up 24/7, that's why I run the database on the bananaPi. Thanks for your feedback! I pulled the armv7 docker and fiddled around with it. The management of the server is pretty nice. Had trouble to link to the server via the EmbyCon plugin but the "Emby for Kodi" plugin worked right away. I let it scrape the Movies - OK. Set up a second library for shows but that is not showing up...guess I have to sign up on the emby forums. Thanks for pointing me into this direction! Emby looks more promising than the Kodi/MySQL combo.
  7. @saarg Would you mind to shed some light on the mentioned questions above? At the moment I'm not that far into Kodi/Sql so I could still switch to something more userfriendly.
  8. The reason why I went with kodi/mysql is that I don't want to have the .nfo and album art cluttering my server shares. Kodi keeps this kind of data in it's database. Does this also apply to Emby? If so, I'm willing to read up Emby.
  9. I vaguely remember having read something similar. I doubt I can find the source again. Edit: Here it is - this thread, some posts ago... Now this raises the question how to configure the scraper on the headless... I don't use sonarr, but a cron job should be doable. If you have some hints how this trigger looks like, would come in handy. Although headless, the docker has a webUI at port 8080. There are lots of settings but when I changed language and things and came back, changes were discarded. Is this by design or should it work? Next question is, how to set the scraper on the headless? I used the universal movie scraper on a client and it did quite well. But how to install the scraper plugin and configure that thing on a headless? I will do some research on that but if you have first hand info, don't hesitate to post here. I wonder if I'm the only one with this lack of info since I haven't found any comprehensive how-to for a headless setup from a-z.
  10. Got it. After I figured out, that there was no service listening on port 3306, I checked the content of /etc/mysql/mariadb.conf.d/ and found another .cnf file. It seems the NextCloud distro uses a different name for that config file. After removing the bind-address setting in that file and restarting the service, the clients connect as expected. I still haven't found where to fire up the scraper. My expectation is, that the headless codi should do that job or am I wrong? I added a sources.xml pointing to the unRAID share into the userdata folder - is that enough?
  11. Yes, you can continue without worries. This backup step is not really necessary if you don't intend to revert back to the original firmware. Make sure you got the adapters.txt with your SAS adress.
  12. The SAS 9300-16i Host Bus Adapter and SAS 9305-16i Host Bus Adapter are rated at 12GB/s but not yet reported working with unRAID. The SAS 9300-16i uses a 2x SAS3008 controllers which is confirmed working in the 9300-8i controller. The other one is most likely also working. Depending on your location it might be a better choice getting two 9300-8i's or a pair of their OEM server pulls (see wiki) to save a significant amount of money, if you don't need the PCIe slots for other things.
  13. Thanks for clarifying! I have a mysql running - not the docker though. I followed the instructions in the kodi wiki to set up the mysql as I already have it running with nextcloud. Used the bind-address = setting. Unfortunately I can't connect to the database remotely (console login with the new user/pass is working). I tried HeidiSQL and get "Can't connect to MySQL server(10060)". I opened up iptables "iptables -I INPUT 1 -p tcp --dport 3306 -j ACCEPT". I flushed iptables for testing - all nothing. What's wrong?
  14. After looking at the advancedsettings.xml, I'm a bit confused. Do I need another docker that brings the mysql database? Isn't it included in the headless-codi docker? 😮 And finally, where/how can I set up the scraper to work through my sources?
  15. Edit: Ignore it, I used the wrong container. (x86 instead of the arm) 🤡 Now the container is running and the log shows this: Warning: MHD_USE_THREAD_PER_CONNECTION must be used only with MHD_USE_INTERNAL_POLLING_THREAD. Flag MHD_USE_INTERNAL_POLLING_THREAD was added. Consider setting MHD_USE_INTERNAL_POLLING_THREAD explicitly. Any advice where to set that flag explicitely? Finally found some time to read through the docker guides and managed to pull the kodi-headless from linuxserverio. This is what I get when trying to start the docker. root@bananapim2:/opt/appdata/kodi# docker start kodi-headless kodi-headless root@bananapim2:/opt/appdata/kodi# docker logs kodi-headless standard_init_linux.go:207: exec user process caused "exec format error" standard_init_linux.go:207: exec user process caused "exec format error" The inspect output is attached. Need help with this.