allanp81

Maybe just try creating a blank motion.conf in that path?

do you have any other boot devices attached? I've had issues in the past with devices and option rom.

Yes, you'll need to terminal into the docker (you can access this from the docker page on your server): https://www.digitalocean.com/community/tutorials/how-to-reset-your-mysql-or-mariadb-root-password

Heidisql is a simple tool and you can use a portable version of it as well I believe.

I've lost the disk that was saving all of my recordings and now I can't start the docker as I presume it's expecting to see some folders in the new location that now don't exist. What's the best way to fix this? If I take a copy of the appdata config and then do a full reset on the docker and then copy the config files back?

Wiping the appdata would cause it to start afresh I think.

Reinstalling the docker wouldn't necessarily change anything as the appdata directory would still exist. What did you set the password as in the docker config as that's what it should be set as.

I thought I'd fixed this issue but no, still occurring so add me to the list of people with this issue and Kodi.

Others may have other insights, but for me with DVB-T/T2, continuity errors were normally caused by poor signal. Do you ever get dropouts in heavy rain or anything like that?

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/

Solved this myself, not sure how, as I haven't done a BIOS update for ages, but VT-D had become disabled in the BIOS. The server is on 24/7 but I guess it's possible that the battery is dead and it reset when I powered the server off?

Hi all, my board used to have no issues passing through PCI-E nics etc. to VMs but for some reason recently it's not working anymore and I don't know what's going wrong. I've tried all sorts, pci-stub vfio bind etc. I've ACS override on and off but not having much luck. My hardware configuration hasn't changed for years apart from adding an NVME drive maybe a year or 2 ago. Asrock say installing a drive here disables PCIE-5. When I go to Tools > System Devices it'sdownloadbox-diagnostics-20210601-1340.zip now saying "No IOMMU Groups Available" rather than listing all of the IOMMU groups like it used to.

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've just got 1 of these drives and can confirm it's still an issue. I'm mounting via the unassigned devices plugin as well.

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.

Get the User Scripts plugin, that will allow you to set any schedule you like.