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 crashing after update to 7.0.1

Featured Replies

  • Author

Ran in safe mode with no gui and it still crashed (before I could pull the logs), running a full memory test now to cehck if there are perhaps issues there.

  • Author

Alright so it isn’t the ram, any help would be appreciated 

image.jpg

  • Author

syslog from the dumped file, maybe it has the crash in it.syslog-192.168.1.50.log

 

Running in safe mode with GUI is somehow more stable today...

  • Author
8 hours ago, JorgeB said:

Make sure that this has been taken cared of:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173

 

Also note that memtest is only definitive if it finds errors, since you have multiple RAM sticks, try using the server with just one pair, if the same try with the other one, that will basically rule out bad RAM.

Alright, what I am parsing from the above post.

1. [done global c-state disabled] In bios check for disabling c-states

2. [done Advanced -> AMD Overclocking -> Curve +4] Change bios with
```

To solve this problem you need to supply higher voltage to your CPU so that it is stable when running at peak frequencies. The easiest way to achieve this is to use the AMD curve optimiser which is accessible via your motherboard's UEFI. Access it and put a positive offset of 4 points, which will increase the voltage your CPU is getting at higher loads. It will limit overclocking potential due to higher heat dissipation requirements, but it will run stable.

```

3. [was already disabled changed speed from 2377 to 2666] Make sure XMP is disabled and instead use slower supported speeds

image.png.46336d7ba39a0a235475019ed317a786.png
4. [running server now start time 5/12/25 5:39pm EST] Test 
5. if still having issues, try different ram stick pairs

6. next,
```

Reducing frequencies to within non-overclocked standards and increasing voltages of CPU or RAM helps, but might not fix the issue. A potential fix is to update the UEFI (also misnamed "BIOS updates"), and then apply the PBO+4 curve for more stability on higher frequencies. Per silicon lottery, some CPUs might need +6 or higher offsets.

```

7. next, not sure how to do this one, but I'll take a gander.
```

This seems to be related to the C6 c-state, that does not seem to be well supported (if at all) in Linux.

To fix this issue, go into UEFI Setup and search for an option labelled something like this: "Power idle control". Change its value to "Typical current idle". Note that these names are dependent on what the motherboard manufacturer calls them, so they may be a little different in your particular case.

Other less ideal solutions include disabling c-states in the UEFI Setup or adding processor.max_cstate=1 to your kernel command line arguments.

```

Edited by abc123
Updating with steps taken

  • Author

I should mention I made one other change, I used to run a Window VM for gaming and I had half the CPU cores pinned to not be used by unraid, I disabled this, likely causing this instability.

  • Community Expert

Still nothing logged, suggesting a hardware issue.

  • Author

Bumped up to +6 on the curve for silicon lottery mention, also already had typical idle current set in bios, since server was stable before update + giving all cpu cores to unraid through the boot command, I believe this is a CPU issue I wasn’t hitting when only running half the cores.

 

ill continue boosting the curve to test, current setting +6

  • Author

Looks like the +6 positive curve modifier got it stable, no crashing.

There was a weird stutter...tower-syslog-20250313-1352.zip

 

Where the server didn't load everything but still was responding some to the HTTP requests?

  • Author

Crashing appears to be resolved, I believe +6 postive curve modifier was the solution for me.

I already had

- BIOS: Disable global c-state

- BIOS: Power idle control = Typical current idle

 

I don't know what happened for the stuttering, also I changed the Docker Network type to ipvlan, and setup a VLAN on my router to move all the unraid server + containers to 192.168.13.2-255

  • 2 weeks later...
  • Author

Crashing is back up to +8 on the curved now

  • Author

Just enabled eco mode and bumped to +9…

going to research other settings from above post as perhaps something else is up, not seeing anything in logs still

  • Author

Still crashing...

Tried:

- Updating bios to 5.60 https://www.asrock.com/mb/AMD/X570 Taichi/index.asp#BIOS

- Removing two sticks of ram
- Trying the other two sticks of ram

- trying different ram slots with different 2 sticks

 

Nothing seems to be resolving the issue, system is now unstable after less than 1 hour.

 

- BIOS: Disable power boost

- BIOS: Disable global c-state

- BIOS: Power idle control = Typical current idle

- BIOS: IMMOU enabled

- BIOS: Curve +6

- BIOS: RAM 1.35V speed 2666

 

  • Author

Current change: Updated to utilize Profile and XMP Profile for ram to get correct timings, then changed the speed down to 2666, to match the required speed setting but also hopefully to make the ram more stable, it has currently lasted 

 

- BIOS: Enabled power boost

- BIOS: Curve +7

 

Uptime 1 hour 25 minutes

 

However, I've had intermittent stability for over 5 days.

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.