Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

UNRAID Kernel panic not syncing Fatal exception in interrupt

Featured Replies

Been up for 11 days, 1 hour, 20 minutes certainly a record and only as Docker was disabled.

 

Today started docker with no containers running.

 

Appeared anytime Docker Containers were running I would have a UNRAID "Kernel panic not syncing Fatal exception in interrupt" and then this caused an Array Rebuild, that took 33 hours, and this was happening all the time essentially making UNRAID unusable.

 

As some people were pointing to pihole, I uninstalled it from Docker.

 

Have messed with this and read entirely too much and disappointed in UNRAID as I was expecting it to hide these type of complexities.

 

Have made so many changes in network configurations, with no help and admittedly not understanding half of the changes talked bout in several forums in regards to many of the settings.

 

Any ideas?

 

tower-diagnostics-20210807-0736.zip

  • Author

Thanks for the help.

 

I have attached the syslog file.

syslog-127.0.0.1.log

  • Community Expert
Jul 25 17:08:43 Tower kernel: macvlan_broadcast+0x10e/0x13c [macvlan]
Jul 25 17:08:43 Tower kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 might fix it, or 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/

  • Author
1 hour ago, JorgeB said:
Jul 25 17:08:43 Tower kernel: macvlan_broadcast+0x10e/0x13c [macvlan]
Jul 25 17:08:43 Tower kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 might fix it, or 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/

While I really appreciate your help, those posts are quite complex with many different steps, many different pages, and no clear answers.
I have also spent several minutes exploring how to even find v6.10 to even begin to install with no success.

I was expecting more support for a product which requires payment.

  • Community Expert
57 minutes ago, -jim said:

I have also spent several minutes exploring how to even find v6.10 to even begin to install with no success.

 

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.