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.

Persistent Unraid Crashes/Hangs - System Unreachable (i7-8700K & Asus B360M-A

Featured Replies

Hello!

I’m having issues with my Unraid server hanging and becoming completely unresponsive. When this happens, it is unreachable via both SSH and the WebUI, forcing me to perform a hard reset using the physical power button. This occurs almost every day.

What I have tried so far:

  • Memtest: I have run Memtest multiple times, and it reports no errors with my RAM sticks.

  • BIOS Tweaks: Based on advice from Google Gemini, I have disabled C-states and lowered the RAM speed (clock frequency) to improve stability.

  • USB Flash Drive: I purchased a new high-quality USB stick (Samsung BAR) to rule out flash corruption, but the problem persists.

  • Thermals: I have replaced the CPU thermal paste and tried running the server with a large external fan blowing directly into the case to rule out overheating. No luck.

  • RAM Configuration: I normally run 4x8GB, but I have tested running only 2x8GB to see if a specific pair was the culprit. The crashes still occur with only 2 sticks installed.

  • Docker Networking: I am already using ipvlan for my Docker containers.

The server performs perfectly right up until the moment it suddenly "dies." I would appreciate any advice or tips on further troubleshooting steps to identify the root cause.

System Hardware:

  • Motherboard: Asus PRIME B360M-A

  • CPU: Intel® Core i7-8700K @ 3.70GHz

  • GPU: GeForce GTX 1060 6GB

  • RAM: Currently 2x8GB (Corsair Vengeance LPX CMK16GX4M2B3000C15)

The diagnostics zip file is NOT from a crash. but the other syslog files is from different crashes and the images i took right after the server crashed

1.jpg

2.jpg

3.jpg

4.jpg

syslog.txt syslog2.txt syslog-previous.txt nassen-diagnostics-20260125-1547.zip

  • Community Expert
1 hour ago, gambler32k said:

run Memtest multiple times

How long did you let it run?

  • Author

How long did you let it run?

approx 30h

  • Community Expert

1st crash was in the memory reclaim (kswapd) subsystem; the 2nd one was in the networking procfs.

When unrelated subsystems crash in core kernel code, the most realistic explanations are widespread memory corruption or faulty RAM

You can try 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, including the individual docker containers.

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.