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 6.12.8 - Constantly Crashing, and I have no idea why.

Featured Replies

Hello all. I've got a problem with my server that is utterly bewildering me. A couple weeks ago, and without making any changes to my server, it keeps crashing all of the time, and without any reproducible source. Genuinely, I have no idea what is going on here, and would appreciate any help anyone can offer. I've tried the following troubleshooting to no avail:

 

  1. Separated the main server IP from all docker vlan's to separate NIC's.
  2. Removed several docker containers that constantly seemed to be crashing the server.
  3. Disassembled and reassembled server to ensure no components have apparent physical damage.

 

I'm sure I'm missing a lot here, so I've also attached my syslog here. Thanks.

syslog-10.216.18.3.log

Solved by CaptainCopSuey

  • Community Expert

There are multiple call traces, suggesting more a hardware issue, I would start by running memtest.

  • Author

Memtest completed with a Pass.

  • Community Expert

Memtest is only definitive if it finds an error, one other thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. 

 

 

  • Author

Ok. I let it run for two days without docker enabled. Enabling docker, I've started slowly re-enabling containers, and it crashed on my immich. I restarted the process of enabling containers, got to jellyfin, which worked fine before, and now it crashed there. Immich still won't start without bringing my server to it's knees. Frustratingly, my syslog file, which is being saved to a separate location, shows call traces, but seems to offer no hint as to what is actually happening. I have no clue what is going, so have attached my newer syslog file here.

syslog-10.216.18.3.log

  • Author

If it helps, I have my docker containers appdata stored on a cache, in a RAID 1 configuration. I have run the extended SMART testing on both, with both returning 0 errors. I can upload their reports if needed.

  • Community Expert

Cannot say if it's software or hardware based on the call traces, but if it only crashes with those two containers maybe something in how they are configured.

  • 5 weeks later...
  • Author
  • Solution
On 3/17/2024 at 1:50 PM, JorgeB said:

Cannot say if it's software or hardware based on the call traces, but if it only crashes with those two containers maybe something in how they are configured.

Replacing my CPU seems to have alleviated this particular call trace, but I've since seen a new kind of error arise. I've created a new topic for it here:

 

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.