Omega666

Yes, as it looked it was a problem of Makemkv, not of the Docker. With the current version everything works again.

Hi, i have massiv Problems with this Container. Maybe someone can help me. I have a Licens for Makemkv and i done this: after starting the container, go into the config directory you created, edit the file called enter-your-key-then-rename-to.settings.conf, and add your key between the quotes app_Key = "[ENTER KEY HERE]" then save and rename the file to settings.conf In the Log File i still get the error that the application is to old and i should use a valid key or update to the newest makemkv. Can someone help? cheers

My server has been running stable for 24 hours. Apparently it was really the plugin. My perity check has also gone through now and I have successfully upgraded the server to the i5 11600T and am very happy with the results. Also my cache is now running with 1TB Raid 1. Thanks for the help.

Thank you very much. That sounds good. I have removed the plugin. I also have a new CPU i5 11600T here because I want to use the second NVMe slot of my board, The question is, swap the CPU now, do parity check or do parity check first and then swap. General recommendation?

Is this a general recommendation or did you see something in the logs? Thanks for the help

I have a new Unraid system. after about 15 hours of parity check the interface freezes, the nas can no longer be reached via png, http or otherwise. i have set up a syslog so that i have log files. i have already replaced the USB stick with a new one. I need help urgently, it is my productive NAs with 26TB of data. it helps only a cold power off. I have attached the syslog log and the diagnostiv file. Bios is up to date. syslog.zipmothership-diagnostics-20220209-1227.zip