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.

Kernel Panic Help

Featured Replies

I have been unable to figure out the reason for the kernel panic I have been getting for about a month now. It happens at least once a day.  I am running unRaid 6.9.2 and have been since the release.  I have ran memtest86 with no errors. I have replaced the motherboard (was going to upgrade anyway). Still cannot figure out what is going on. Diagnostics and mirrored syslog are attached. Any help would be greatly appreciated.

 

syslogunraid2-diagnostics-20211102-1644.zip

  • Community Expert

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/

  • Author

I have removed my custom docker network and changed all docker containers to either Bridge or Host.  So far this seems to have solved the locking up/kernel panic issue.  While making these changes I attempted to upgrade from 6.9.2 to 6.10.0-rc2.  The upgrade processed fine but then after the reboot the server would never come back up and I just receive this over and over again on the terminal screen/syslog.

 

Nov 5 09:59:29 unRaid2 rpcbind[414]: connect from 192.168.18.81 to getport/addr(mountd)
Nov 5 09:59:31 unRaid2 kernel: usb 1-7: USB disconnect, device number 43
Nov 5 09:59:31 unRaid2 kernel: usb 1-7: new low-speed USB device number 44 using xhci_hcd
Nov 5 09:59:31 unRaid2 kernel: hid-generic 0003:09AE:2012.0A30: hiddev96,hidraw2: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:00:14.0-7/input0

Nov 5 09:59:36 unRaid2 rpcbind[587]: connect from 192.168.18.81 to getport/addr(mountd)
Nov 5 09:59:46 unRaid2 rpcbind[834]: connect from 192.168.18.81 to getport/addr(mountd)
Nov 5 09:59:46 unRaid2 kernel: usb 1-7: USB disconnect, device number 44
Nov 5 09:59:46 unRaid2 kernel: usb 1-7: new low-speed USB device number 45 using xhci_hcd
Nov 5 09:59:46 unRaid2 kernel: hid-generic 0003:09AE:2012.0A31: hiddev96,hidraw2: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:00:14.0-7/input0
Nov 5 09:59:59 unRaid2 rpcbind[1292]: connect from 192.168.18.81 to getport/addr(mountd)
Nov 5 10:00:01 unRaid2 kernel: usb 1-7: USB disconnect, device number 45
Nov 5 10:00:01 unRaid2 kernel: usb 1-7: new low-speed USB device number 46 using xhci_hcd
Nov 5 10:00:02 unRaid2 kernel: hid-generic 0003:09AE:2012.0A32: hiddev96,hidraw2: USB HID v1.10 Device [Tripp Lite Tripp Lite UPS ] on usb-0000:00:14.0-7/input0

 

This also fills up my syslog after restoring back to 6.9.2, but everything seems to be working on 6.9.2 otherwise.

 

I have attached my mirrored syslog and diagnostics. Any idea why I am not able to finish the boot after upgrading to 6.10.0-rc2?

 

Thanks

 

unraid2-diagnostics-20211105-1005.zipsyslog

  • Community Expert

Try connecting the UPS to a different USB port/controller.

  • Author
8 minutes ago, JorgeB said:

Try connecting the UPS to a different USB port/controller.

I will try that when I get home. I did disconnect it when trying to get 6.10-rc2 to boot and the message changed/went away but still wouldn't complete the boot after upgrade.

  • Community Expert

The boot issue with rc2 is likely unrelated to that.

  • Author

Turns out the issue was a bad cache drive that was not reporting any issues. The Kernel Panic issues seems to be resolved.

 

I am still unable to boot into unRaid after upgrading from 6.9.2 to 6.10-RC2. Issue seems to be the same as before for that part.

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.