cYnd Posted April 22, 2021 Share Posted April 22, 2021 So I am running UnRaid 6.9.1 on a Intel Core i3-10100 mounted on a ASUS TUF GAMING B460M-PLUS with 16GB of Kingston HyperX DDR4-2666. Everything was running smooth when I suddently noticed that occasionally my UnRaid server crashes with a Kernel panic - fatal exception in interrupt. Unfortunalety I can't attach anything else than picture, otherwise I would have provided the SysLog and diagnostics. I also ran MEMTEST and it passed, so it shouldn't be the RAM. Have you any ideas how to solve this? Quote Link to comment
JorgeB Posted April 22, 2021 Share Posted April 22, 2021 Enable this then post that syslog after a crash, also post the complete diagnostics. Quote Link to comment
cYnd Posted April 22, 2021 Author Share Posted April 22, 2021 I already enabled the SysLog, so I can provide it since the last crash. Please also find the diagnostics attached. Do you see any abnormality in this? unraidserver-diagnostics-20210422-2146.zip syslog-192.168.178.69 (2).log Quote Link to comment
mladams Posted April 22, 2021 Share Posted April 22, 2021 I'm in the same boat. Been getting a kernel panic at least once a day. Memtest clean, syslog shows nothing. I've tried every trick I've found in this forum and others... I have no idea what to do next except downgrade. Poweredge r720 - 128gb Quote Link to comment
JorgeB Posted April 23, 2021 Share Posted April 23, 2021 11 hours ago, cYnd said: Do you see any abnormality in this? Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/ Quote Link to comment
cYnd Posted April 23, 2021 Author Share Posted April 23, 2021 Okay, I indeed use docker with static IP addresses. Moreover I also enabled the setting "Host access to custom networks" in the docker settings because I am running PiHole and Unbound on my UnRaid Server as two docker containers and I want that my UnRaid Server is also using pihole and unbound as DNS servers. When I switch the setting off, I can't access these containers from within unraid itself. Since I am not an network specialist, I don't know any other workaround to use my local dns server within UnRaid. To solve the problem of the crashes I disabled the setting again and I will check if the crashes persist or if this solved my problem. However do you know how I need to configure my UnRaid server so it can access the PiHole/Unbound docker containers with custom IP addresses as a DNS server? Quote Link to comment
JorgeB Posted April 23, 2021 Share Posted April 23, 2021 First link has alternative ways of configuring dockers. Quote Link to comment
cYnd Posted April 23, 2021 Author Share Posted April 23, 2021 Since I don't think that my network components support VLAN and I only got one NIC available there is no feasible solution. Quote Link to comment
Recommended Posts
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.