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.

server not responsive

Featured Replies

hi so this is the third time within this week to have this problem

 

the server is unreachable at all even from the server itself i only get black screen

some dockers keep working like plex 

 

it is only media server no VM plex and arr apps 

 

i don't know what the issue is any help is appreciated 

attached the logs this is the only time i was able to get logs because i enabled the syslog server otherwise i can't get access to the server until a hard reboot 

 

 

syslog-192.168.100.21.log

Solved by Alansari

  • Author
8 minutes ago, trurl said:

Attach Diagnostics ZIP to your NEXT post in this thread.

attached the file

 

and i remember this problem started when i tried  to remove the ca mover plugin the server became unresponsive and after that every few days i will get the same thing

alansari-diagnostics-20250409-0052.zip

  • Community Expert
15 minutes ago, Alansari said:

tried  to remove the ca mover plugin

I think many who think they want that are overthinking how cache should be used.

 

Have you done memtest?

  • Author
1 minute ago, trurl said:

I think many who think they want that are overthinking how cache should be used.

 

Have you done memtest?

I did when i first built the server a year or so ago and everything was fine and never changed anything beside adding hhd

 

should i run memtest again ?

  • Community Expert
Just now, Alansari said:

should i run memtest again ?

yes

  • Author

The memtest passed 

 

anything else to check ?

9 hours ago, trurl said:

yes

image.thumb.jpg.37a9e654e3b486c657ee759802c0392e.jpg

  • Community Expert

Note that memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

 

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, including the docker containers. 

  • Author
9 minutes ago, JorgeB said:

Note that memtest is only definitive if it finds errors, if you have multiple sticks try using the server with just one, if the same try with a different one, that will basically rule out bad RAM.

 

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, including the docker containers. 

 

alright I will try that but is there anything in the syslog indicate I have a bad ram ? because I don't understand anything from it sorry if this stupid question 

  • Author

I found these as well in the plugin page should I delete them?

Screenshot 2025-04-09 at 11.39.14 AM.png

  • Community Expert
2 hours ago, Alansari said:

there anything in the syslog indicate I have a bad ram ?

No, it's just one of the more common reasons for stability issues.

 

You can delete those.

  • 3 weeks later...
  • Author

so i tried new rams i still got the same problem the server crashed after few days

 

is there anything i can check to see what is the problem

 

and the problem started when i tried to delete the mover plugin the server crashed then i hard rebooted the server and the mover plugin was still there so i deleted it and from that day every few days the server will crash and i don't know why

syslog-192.168.100.21.log

  • Community Expert

Still nothing logged that points to the issue, this typically means hardware, but one 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, including the docker containers. 

  • Author
  • Solution
On 4/25/2025 at 2:40 PM, JorgeB said:

Still nothing logged that points to the issue, this typically means hardware, but one 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, including the docker containers. 

 
can it be from the usb stick? because after every crash the server won't boot it will keep going to bios page until i pull the usb out and then in again and restart

  • Community Expert

What do you get from command line with this?

df -h /

 

  • Author
5 hours ago, trurl said:

What do you get from command line with this?

df -h /

 

IMG_1729.thumb.jpeg.33ecc92d54c17295b128e77d1f5faece.jpeg

  • Community Expert
11 hours ago, Alansari said:

can it be from the usb stick?

It's a possibility.

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.