Doppelherz

had the same problem. had to follow all steps, delete some files from appdata and changed jDownloader.jar, now it works again

disabling bridging on eth0 seemed to work... till last night. Three days in a row the unraid server was alive and i was not far away from happily click on the "mark as Solution" Button, but today, the server was down with all its docker containers again. Syslog Server was already disabled, of curse... Now it is turned on again and now i am waiting, to see, whats going on there. Next freeze I am posting the syslog and diagnostics again

but what, if I want to use macvlan?

Hi, I have been having problems with my Unraid machine for some time. Occasionally the PC crashes. The GUI is often no longer usable, but the Docker containers continue to run. Recently, however, everything has been crashing. But from the beginning. I have been looking for Docker containers for backups and have experimented with Duplicaty and Kopia. With both, when loads were created, the GUI could no longer be called up. I observed something similar when I tried the virtual DSM Docker Container. However, everything crashed. For this Docker container, I also changed the Docker network type to macvlan so that the custom br0 containers were also visible on my router. The problem persisted. I'm already wondering whether the PC still has XMP activated in the BIOS. In any case, I downloaded the diagnostics and started the syslog server. In the middle of the night I got the mail about Fix common Problems: * **Unable to write to nvme** * **Unable to write to Docker Image** Immediately afterwards, the PC crashes. At least that's what it looks like in the syslogs. But I don't know why. I have connected two NVMEs as brtfs single, because they should first serve as raid1 as failover, but then I wanted to separate them to have the appData folders on one and the VMs on the other, but for that I have to format the NVMEs first to separate the pool. So the single solution came in handy. But I'm afraid that it will now fill up the first NVMe and then die when the first is full. Maybe someone can fly over the logs and give me a hint what i have to change? mahome-diagnostics-20231207-0757.zip syslog