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 Inaccessible through gui/ssh after cpu upgrade

Featured Replies

Gday

I upgraded from a 1600x to a 3900x and have had issues accessing the server after a couple of days time.

The only way to regain access that I've found is to hard shutdown.

I believe the bios is up to date enough to handle the new cpu and have disabled global c states.

Docker apps all work going in and out of the network but can't see each other (radarr can be connected to but can't access jackett)

I have captured the logs via write to usb function and have uploaded to take a look at.

Thanks for reading and anyone who wants to help me solve the puzzle!

Cheers

Jan26 log1

  • Author

Thanks Jorge!

In my research before posting I checked that the bios was up to date a couple years past the 3900x release and set it to typical idle current and disabled the global c-states.

I'm also not overclocking the ram

  • Community Expert

I'm, afraid there's nothing relevant logged in the syslog, so if all that is correctly set, it may be a hardware issue.

  • Author

Thinking about how the issue comes out I would think it has something to do with the internal network crashing.

I can't access the gui but the dockers are still accessible.

Can't wrap my head around it but server is only staying accessible for 2-3 days at a time

  • Community Expert
1 hour ago, sl0pz said:

I can't access the gui but the dockers are still accessible.

If it's an Unraid issue it leave something logged on the syslog, but post a new persistent syslog when that happens, and point out the time code it happened.

  • 4 weeks later...
  • Author

It's still happening but seemingly faster and faster.

I don't think there is anything on the log, is there a different way to preserve the log that might show the error (that I'm not doing)?

About to have time to deep dive into it, any other guides I can follow to try to figure it out?

edit: I did update to 7.2.3 and also updated the bios to the latest one just in case

Edit 2: Looking at glances I have /usr/libexec/unraid/shfs /mnt/user -disks 127 -o default_permissions,allow_other

taking 70%+ of the cpu but also going over 100%

edit 3: https://forums.unraid.net/topic/195401-cpu-being-hammered-by-shfs-and-other-errors-memory-related/#findComment-1593075
followed this post to move appdata to cache, increased the fuse file descriptors, ran fastusr to keep os in ram, and removed plexstreams plugin as well as unassigned devices
looks like lower cpu usage, don't know if it will change the lockups tho.

syslog

Edited by sl0pz

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.