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.

Error: Call Traces found on your server

Featured Replies

Hi, the fix common problems plugin told me to ask for help in the forums. I would really appreciate it if someone looked at my attached diagnostics and told me if there's anything I should be worried about. 

tower-diagnostics-20180309-2139.zip

  • Community Expert

Some page stalls and docker issues, image seems to be fine now, but if there are more errors or any docker issues better to delete and recreate.

 

During the time covered by the syslog were you disconnecting and re-connecting various disks?

  • Author

Thank you!

 

Yes, I had the array offline and disconnected/re-connected a few disks to identify the parity disk (upgrading to 8TB). 

  • 4 weeks later...
  • Author

Hi, I got another warning regarding call traces today. I suspect it is related to the file system error on disk 4 that I had to fix using XFS_repair -L, but can someone check the attached diagnostics just in case? 

tower-diagnostics-20180402-1328.zip

  • Community Expert
59 minutes ago, Mith said:

I suspect it is related to the file system error on disk 4

Yep, there's another one related to a kernel problem, fixed in rc3

  • Author
29 minutes ago, johnnie.black said:

Yep, there's another one related to a kernel problem, fixed in rc3

Thanks for lightning fast response! 

 

Can you elaborate what you mean by fixed in rc3? Do I need to do anything other than the XFS_repair command I did earlier to avoid something like this happening again? 

  • Community Expert

The first call trace:

 

Mar 31 06:43:17 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038

is unrelated to the second one (and xfs_repair), it's a kernel bug fixed on rc3, the second one was filesystem corruption and should be fine now after running xfs_repair.

  • Author

Ok, thanks again :-)

Archived

This topic is now archived and is closed to further replies.

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.