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 becomes unresponsive after random time intervals

Featured Replies

After anywhere from 30mins to 7+days, Unraid becomes almost completely unresponsive until hard shutdown.

This started happening with some 6.12.x version iirc. after almost 2 years of flawless operation.

 

What still works when "unresponsive"

  • responds to pings
  • responds to bare-metal keyboard input but logging in times out
  • wireguard vpn

 

What I have tried so far

  • disable C-states
  • slightly decrease vm.dirty_background_ratio and vm.dirty_ratio
  • disable expo profile
  • running in a minimal working scenario with only 5 dockers and no vms
  • play with quite a few more settings (1 at a time), which i should have all reverted due to not helping

 

System hardware

  • MSI B550M Pro-VDH
  • Ryzen 5600g
  • 64GB RAM
  • Samsung 980 Pro 1TB
  • Samsung 870 QVO 4TB

 

Software setup

  • Unraid v6.12.4
  • Plugins: CA, Active Streams, System Temp, Fix Common Problems, FolderView, Tips and Tweaks, UD, UD+, Unraid Connect, User Scripts
  • 1TB cache
  • 4TB array
  • 2 auto-start ubuntu VMs, 1 auto-start windows VM
  • several docker containers including typical services like nextcloud behind swag

 

Syslog server recording

The attached syslog was recorded during following sequence;

  • Normal operation for 7 days (cut from log except for last 2 entries)
  • 15:01 unresponsive
  • 15:05 hard shutdown
  • 15:43 temporary unresponsiveness (just ~2mins, first time ever noticed by us in this fashion)
  • 15:56 unresponsive

 

syslog_oct_2.txt server-diagnostics-20231002-1714.zip

Edited by Alintya

  • Community Expert

Unfortunately there's nothing relevant logged, other than a OOM event*, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker/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.

 

* If it's a one time thing you can ignore, if it keeps happening try limiting more the RAM for VMs and/or docker containers, the problem is usually not just about not enough RAM but more about fragmented RAM, alternatively a small swap file on disk might help, you can use the swapfile plugin:

 

https://forums.unraid.net/topic/109342-plugin-swapfile-for-691/

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.