December 2, 20232 yr System Information Unraid Version: 6.12.4 Model:Custom M/B:ASRockRack X570D4U-2L2T s/n 220923170000193 BIOS:American Megatrends International, LLC. Version P1.70 Dated 09/15/2022 PU:AMD Ryzen 7 5700X 8-Core @ 3400 MHz HVM:Enabled IOMMU:Enabled Cache:L1 - Cache: 512 KiB, L2 - Cache: 4 MiB, L3 - Cache: 32 MiB Memory:64 GiB DDR4 Multi-bit ECC (max. installable capacity 128 GiB) Network:eth0: 1000 Mbps, full duplex, mtu 1500 Kernel:Linux 6.1.49-Unraid x86_64 OpenSSL:1.1.1v At completely irregular intervals I have the problem that Unraid runs into a kernel panic. Sometimes after 3 days, but sometimes after 14 days. The last time it happened when updating a Docker container "duplicati" I have already read in other posts that it makes sense to create a syslog, but I can't find anything helpful there either. I got the kernel panic log via pi KVM. I have had this problem for several versions of Unraid, but have never been able to find the issue. robomedia-diagnostics-20231202-0952.zip syslog-192.168.5.101.log
December 2, 20232 yr Community Expert Solution Dec 2 00:10:29 RoboMedia kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Dec 2 00:10:29 RoboMedia kernel: ? _raw_spin_unlock+0x14/0x29 Dec 2 00:10:29 RoboMedia kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.
December 16, 20232 yr Author I did, it has now been running for 6 days without any problems. I would report back when I have completed the 14 days, as it has never run longer than 14 without crashing.
December 27, 20232 yr Author It seems to have worked. Unraid has now been running for almost 18 days without crashing. Thank you
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.