[SOLVED ]Unraid becomes unresponsive randomly - no GUI/Docker/Ping - hard reboot needed

[daquint]

Its a fairly new system and has been doing this since I brought it up.
Sometimes it happens after a few days, and sometime it happens 2 days in a row.

Can anyone take a look at my diagnostics/syslog and see if there's something that stands out?

Mucho thanks!

 

syslog-192.168.0.5.zipsmashboogie-diagnostics-20220506-0747.zip

Edited May 15, 2022 by daquint

[JorgeB]

May  3 05:13:01 smashboogie kernel: macvlan_broadcast+0x116/0x144 [macvlan]
May  3 05:13:01 smashboogie kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

 

 

Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.

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/

[daquint]

45 minutes ago, JorgeB said:

May  3 05:13:01 smashboogie kernel: macvlan_broadcast+0x116/0x144 [macvlan]
May  3 05:13:01 smashboogie kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

 

 

Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.

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/

Thanks! I am on 6.10.0 -rc6 and have switched it to ipvlan.
 

[daquint]

On 5/6/2022 at 8:04 AM, JorgeB said:

May  3 05:13:01 smashboogie kernel: macvlan_broadcast+0x116/0x144 [macvlan]
May  3 05:13:01 smashboogie kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

 

 

Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.

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/

So far so good - I think this solved it - thanks @JorgeB! Will mark as solved