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.

lcadmedia

Members
  • Joined

  • Last visited

Solutions

  1. lcadmedia's post in Server Crashed during parity build was marked as the answer   
    *** UPDATE #2 ***
    Disabling vCore offset mode and set to auto did the trick while enabling XMP on my RAM but I have 4 Samsung B-Die 3200Mhz CL14 @ 1.35v RAM which had no errors on memtests a while back when I ran it.
     
    Unraid Server has been running w/o any crashes now, despite enabling XMP which can increase instability rather than setting it to 2933Mhz ; but everything seems to be stable now.
    The downside is that my CPU (Ryzen 3800X) runs hot (PBO on Auto) on idle at 50 C - 60 C, and goes to 70 C - 75 C during load based on Tctl.
    I wish I could lower the voltage but I don't want any instability at the moment while I'm finalizing all my Parity Sync, Time Machine, and Windows VM Backups.
     
    But uptime currently more than 2 days which is very promising!
     
    *** UPDATE ***
     
    Unraid server seems to freeze/hang during idle or when there's close to nothing going on, and with vCore on Offset mode.
    Seems like vCore too low during idle that causes instability, so I disabled offset mode and just set it on auto. 
    Seems to be working normal currently.
     
    I went back to my BIOS and changed my vCore from offset mode to Auto, and put my DRAM XMP Profile as it was intended for the RAM to 3200Mhz CL14 @ 1.35v, instead of setting it to 2933Mhz as per Official AMD Frequency.
     
    Then I disabled one of my dockers (VPN) that used br0, even though I've changed it to IPVLan since the MacVLan were crashing the entire system.
     
    And it finished my Parity Sync without hiccups!!! 
    For some reason, my RAM XMP Profile made it more stable...
     
    Now, Pre-clearing my 2nd 16TB Drive!
     
     
    Hi,
     
    The Server was running fine for 2 - 3 days online, then I started parity sync yesterday and was about 87% until the server suddenly crashed.

    pre-crash BIOS settings:
     
    CPU: Ryzen 3800X - offset mode - 0.05v
    RAM: TEAMGROUP-UD4-3200 - 2933Mhz CL14 @1.35v (Recommended settings: 3200Mhz CL14 @1.3v)
    Typical Current Idle, Global C-State disabled.
     
    Curious Question:
    - Under System Profiler > Memory Device: My RAM Voltage is shown 1.2v for min, max and configured voltage even though I've set the RAM Voltage to 1.35v, and BIOS even shows 1.36 - 1.37v. Is that accurate on Unraid?
     
    I have attached my Post crash diagnostics, if you guys can take a look at it. It would be greatly appreciated.
     
     
     
    kbnomadserver-diagnostics-20220707-2216.zip syslog-192.168.1.2.log
  2. Yes!

    as What @JonathanM mentioned, I changed my Unraid DNS Servers to Cloudflare's 1.1.1.1 while routing all devices through pihole (except unraid).

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.