allanp81

My server used to take about 8 hours with dual parity 4Tb drives. It's now about 12 hours for dual parity 6Tb drives. I'm assuming the amount of data disks has not much bearing on how long the process will take as the size of the parity disks is the main factor?

How easy is that to migrate what I have in my DB already though?

It's a shame it seems we won't see a version of this that works with Matrix (19) as I've finally upgraded all of my clients to 19 and rely on the headless docker for DB updating. It's not critical per se, but it's very very useful and beyond my ability to create my own docker for 19.

I think I just followed the guide here: https://mariadb.com/kb/en/mysqldump/

Switching to "On demand" seems to have solved it for me as well, mine was set to power save (don't remember setting that).

if you terminal into the docker and list devices is it definitely being passed through? I think lspci might show it (unless someone else knows the answer).

I've done it, it's fairly straight forward to migrate the DB from mysql to mariadb, you can use mysqldump to backup from mysql and then import into mariadb. It's slightly more complicated to edit the nextcloud config though if you're using different DB credentials. In theory if the credentials are the same then nextcloud will just work when you restart the docker.

Yes I have to agree with others, I'm not really sure what you're trying to achieve. If you just want a simple way of browsing your collection then Emby or Jellyfish is a much easier (and nicer) way to do this. Whatever you use though will be "out of sync" with your clients if the clients have their own local libraries.

Well then in theory it'll work "standalone", don't see why not and then you can just browse via the web interface but if you have another client they'll show different results the next time you do a library scan on either. It's fairly easy to set up an SQL docker and then use a shared library.

You need to use an SQL database to store your library otherwise I don't see why you would want to use this? You can configure all of your sources on another kodi instance and then copy the sources.xml over to the docker container for the kodi headless.

I use it with others that can use the API to kick off library scans. It works great. You can set up scripts yourself to do this if you want as it's fairly easy to use the API to do certain functions.

I asked that before and was told there was no specific to use 1 over the other. I went for the docker route as I thought it was just easier to see how you're setting up directories for recordings etc. when using the docker interface. I think you still need the DVB plugin and then pass the device through to the docker. I use a networked HD Homerun so it just worked.

Sorry I'm only running beta on my backup server currently which has no cache drives.

It's so annoying, I had to re-architect my server to get around this problem (and obviously there was expense involved),.

No I realise that, just wasn't sure if anyone was experiencing the same "issue". It seems to be a DNS issue, I'm getting different IPs returned when I look up my domain name depending on what computer I'm using.

This seems to have stopped working for me this morning for no obvious reason. I've scanned all of the error logs and there's no errors logged that are any different to those that sporadically appear from time to time anyway. I'm perplexed.

*EDIT* I think I answered my own question, seems to be a let's encrypt issue. My nextcloud instance seems to have stopped working this morning for no obvious reason. The nginx log is showing the following that it wasn't showing before: 2020/06/30 09:31:14 [error] 370#370: *355 directory index of "/config/www/" is forbidden, client: 192.168.7.28, server: _, request: "GET / HTTP/1.1", host: "192.168.7.11:8443" 2020/06/30 09:31:14 [error] 370#370: *355 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.7.28, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.7.11:8443" 2020/06/30 09:31:14 [error] 370#370: *355 open() "/config/www/favicon.ico" failed (2: No such file or directory), client: 192.168.7.28, server: _, request: "GET /favicon.ico HTTP/1.1", host: "192.168.7.11:8443" 2020/06/30 09:31:14 [error] 370#370: *355 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.7.28, server: _, request: "GET /favicon.ico HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.7.11:8443" Anyone got any ideas as to why this has suddenly happened? The docker hasn't updated for a while I think but the let's encrypt docker last night did update.

I've been using kodi with sql backend for years, using different versions of kodi for front end (coreelec, libreelec, kodi for windows, kodi headless docker) and never had any issues, just works.

What changed in Unraid itself though?

Just thought I'd chime in and say this worked for me on an old H67 board that refused to POST with any SAS cards in. I was able to get this to boot with 2 H310 SAS cards installed

I was seeing this with a pool of 2 512Gb SSDs. I have since switched to a single Intel NVME drive and the problem has gone.

I kinda guessed that, but I couldn't figure out the docker run command as it fails when I try.

I mean even just getting the docker installed.

Did you get this working? I'm really struggling.

Does your kodi headless have access to that nfs path? And you've added the sources.xml etc?