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 server keeps crashing constantly with internally added HD (with UD plugin)

Featured Replies

Hi guys,

 

In order to backup my media fast I am lately using an internal HD (removable HD frame) mounted with the Unassigned Disks plugin formatted with different file systems (I tried HFS, NTFS and XFS). Each time I start copying files from the array I takes about 10-30 minutes when the CPU is stuck with the first core at 100% and the the other cores follow. The server gets unresponsive to pings and looking at the console (monitor attached to server) error messages run fast across the monitor and I only can switch off the server hard. I never encountered problems before, so I think it has to do with the attached drive. Is there a way to analyze the problem, because I cannot see anything in the sys log.

I tried to setup a remote syslog-ng server and turned on the remote and local syslog folder, the server crashed but no log, neither on the remote nor on the server.

Is there another way to upload a system report (I read the syslog section, but as I said it didn't work).

 

Any help would be greatly appreciated ... greetings from Berlin (Germany) .... retox

Unraid Startup Log 12.02.2022.txt

A picture of what's on the screen would also be helpful

  • Author

Hi Squid,

 

as I said, the screen kept constantly scrolling ... here is the only photo where the screen was stuck. Do you have an advice how to log this?

 

 

CrashPhoto.jpg

I don't see a disk in your arrangement that is a UD disk.  I see:

  • flash drive.
  • 3 data disks.
  • 1 parity disk.
  • 1 cache disk.

Can you post a screen shot of the UD screen showing the UD disk you are trying to use?

  • Author

You are absolutely right … I forgot that I removed the HD yesterday … I’ll be back tomorrow with a new report. Thank you …

  • Author

Hi there, back again. Here are my latest diagnostic files. I thought I post 3 states (if this is included in the diagnostics script).

I'll also add a photo of the monitor screen after the crash. What i noticed is: Copying files internally without copying at once from a client to the server does nothing.

Copying externally and internally leads to a crash. I thing it has something to do with the network/memory, maybe an overflow?

I think you'll better know what it could be looking at the protocols.

 

Thank you in advance ... retox

Unraid crash site.jpg

datacore-diagnostics-20220216-1309 (before crash).zip datacore-diagnostics-20220216-1329 (while copying).zip datacore-diagnostics-20220217-1852 (after crash).zip

  • Author

Hi Trurl, not yet. Is there not enough information provided thru/by the diagnostic files?

10 minutes ago, retox said:

Hi Trurl, not yet. Is there not enough information provided thru/by the diagnostic files?

The logs are stored on RAM with all the OS and are lost on reboot/crash.

So your diagnostics can only tell us so much and probably not what happens before a crash.

 

The syslog server is permanent and provide more information about crashes.

  • Author

So all my diagnostic files reveal the same information? I tried to setup a syslog server, if you read my first post, but it didn't work ... i follow the infos ... could you guide me through in an easy way? I'm a linux newbee ...

  • Author

Hi there, so here at last my syslog and a photo of the latest crash on the monitor . I'm really excited what kind of problem this is ...😉

 

telegram-photo-0-5787348262926268477.jpg

syslog

I see several things:
 

Feb 18 21:08:28 DataCore cache_dirs: Arguments=-i Backups -i Media -i Software -i Temp -i appdata -i domains -i isos -i system -l off
Feb 18 21:08:28 DataCore cache_dirs: Max Scan Secs=10, Min Scan Secs=1
Feb 18 21:08:28 DataCore cache_dirs: Scan Type=adaptive
Feb 18 21:08:28 DataCore cache_dirs: Min Scan Depth=4
Feb 18 21:08:28 DataCore cache_dirs: Max Scan Depth=none
Feb 18 21:08:28 DataCore cache_dirs: Use Command='find -noleaf'
Feb 18 21:08:28 DataCore cache_dirs: ---------- Caching Directories ---------------
Feb 18 21:08:28 DataCore cache_dirs: Backups
Feb 18 21:08:28 DataCore cache_dirs: Media
Feb 18 21:08:28 DataCore cache_dirs: Software
Feb 18 21:08:28 DataCore cache_dirs: Temp
Feb 18 21:08:28 DataCore cache_dirs: appdata
Feb 18 21:08:28 DataCore cache_dirs: domains
Feb 18 21:08:28 DataCore cache_dirs: isos
Feb 18 21:08:28 DataCore cache_dirs: system
Feb 18 21:08:28 DataCore cache_dirs: ----------------------------------------------

Don't cache appdata, domains, isos, or system.  It doesn't help on those shares.  I assume you have them on a SSD cache or Pool device.  For the moment, I'd remove the cache dirs plugin.

 

Also remove S3 sleep and preclear plugins for now.

 

There's nothing wrong with these plugins, I just want to limit the number of things that could get in the way.

 

I also see these, but I don't know if this is an issue or not:

Feb 18 21:09:03 DataCore root: Starting Nginx server daemon...
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.974 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.974 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *13 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *13 limiting requests, excess: 20.973 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.972 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *60 limiting requests, excess: 20.972 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.972 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *13 limiting requests, excess: 20.972 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.971 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *59 limiting requests, excess: 20.971 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *14 limiting requests, excess: 20.971 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *60 limiting requests, excess: 20.971 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *15 limiting requests, excess: 20.969 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *13 limiting requests, excess: 20.969 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *61 limiting requests, excess: 20.969 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *59 limiting requests, excess: 20.969 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *14 limiting requests, excess: 20.968 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:03 DataCore nginx: 2022/02/18 21:09:03 [error] 9771#9771: *60 limiting requests, excess: 20.966 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:08 DataCore nginx: 2022/02/18 21:09:08 [error] 9771#9771: *15 limiting requests, excess: 20.384 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"
Feb 18 21:09:08 DataCore nginx: 2022/02/18 21:09:08 [error] 9771#9771: *61 limiting requests, excess: 20.383 by zone "authlimit", client: 192.168.178.140, server: , request: "GET /login HTTP/1.1", host: "192.168.178.21", referrer: "http://192.168.178.21/Main"

 

You said this is a disk mounted with UD.  Can you give a screen shot of the UD page?  Also, how are you doing your copying?

On 2/17/2022 at 12:38 PM, retox said:

could you guide me through in an easy way?

This post will give you a step-by-step guide for setting up the Syslog Server.

  • Author

Hi Hoopster ... Syslog is already uploaded ... thank you ...

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.