unraid_user11

Appreciate the advice, any time frame I should run the server on one stick for it to be definitive?

I ran Memtest86 on the RAM sticks (Crucial Pro 128GB Kit (2x64GB) DDR5 RAM, 5600MHz) when I purchased them roughly 6 months ago for 2 passes, no errors. Crash occurred around 16:09, wasn't doing anything heavy on the server, all drives were spun down I believe. The previous crash I attributed to a docker container being in a restart loop, I have since removed the container. Not sure what could be causing this crash. Attached diagnostics zip to post. Appreciate any help. This is a snippet of my syslog for the 12 hours before the crash, not shore what the x86/split lock detection or the Server kernel: traps: chromium[3052958] trap int3 is about. Mar 22 04:34:42 Server kernel: traps: chromium[2268916] trap int3 ip:55d2328dca0b sp:7ffe9c2921b0 error:0 in chromium[6118a0b,55d22d695000+c0b6000] Mar 22 04:42:41 Server emhttpd: read SMART /dev/sdc Mar 22 04:43:10 Server emhttpd: read SMART /dev/sdb Mar 22 04:50:01 Server rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="16905" x-info="https://www.rsyslog.com"] rsyslogd was HUPed Mar 22 04:59:00 Server emhttpd: spinning down /dev/sdb Mar 22 04:59:00 Server emhttpd: spinning down /dev/sdc Mar 22 06:56:35 Server kernel: traps: chromium[3052958] trap int3 ip:5569565c8a0b sp:7ffff5b3cb90 error:0 in chromium[6118a0b,556951381000+c0b6000] Mar 22 07:03:49 Server kernel: traps: chromium[3090581] trap int3 ip:556ada948a0b sp:7ffdc19262d0 error:0 in chromium[6118a0b,556ad5701000+c0b6000] Mar 22 08:17:08 Server kernel: x86/split lock detection: #AC: CPU 1/KVM/45742 took a split_lock trap at address: 0xfffff8037c650d8d Mar 22 09:56:36 Server kernel: traps: chromium[4040633] trap int3 ip:5636f0cc2a0b sp:7fff6f81c810 error:0 in chromium[6118a0b,5636eba7b000+c0b6000] Mar 22 10:03:49 Server kernel: traps: chromium[4078120] trap int3 ip:556432aa0a0b sp:7fff5fb89cd0 error:0 in chromium[6118a0b,55642d859000+c0b6000] Mar 22 10:34:41 Server kernel: traps: chromium[55077] trap int3 ip:55cd3603ba0b sp:7ffe98dcc760 error:0 in chromium[6118a0b,55cd30df4000+c0b6000] Mar 22 12:56:36 Server kernel: traps: chromium[856187] trap int3 ip:557abffc4a0b sp:7ffec6474450 error:0 in chromium[6118a0b,557abad7d000+c0b6000] Mar 22 13:03:50 Server kernel: traps: chromium[893618] trap int3 ip:555c4654aa0b sp:7ffc403d0780 error:0 in chromium[6118a0b,555c41303000+c0b6000] Mar 22 14:40:53 Server kernel: x86/split lock detection: #AC: CPU 3/KVM/45744 took a split_lock trap at address: 0xfffff8037c650d8d Mar 22 15:14:33 Server kernel: hrtimer: interrupt took 17448 ns Mar 22 15:56:37 Server kernel: traps: chromium[1926269] trap int3 ip:5563cb6f8a0b sp:7fff46e32ff0 error:0 in chromium[6118a0b,5563c64b1000+c0b6000] Mar 22 16:03:50 Server kernel: traps: chromium[1974396] trap int3 ip:55bb54104a0b sp:7ffe8eeb83b0 error:0 in chromium[6118a0b,55bb4eebd000+c0b6000] Mar 22 16:10:03 Server rc.rsyslogd: Syslog server daemon... Started.server-diagnostics-20260322-1624.zip

Just installed Unraid Connect plugin and came to say I have the same issue.

You are a legend mate! Just got it up and running along with the Home Assistant HACS Unraid API integration and it's working flawlessly! Thank you again!

That worked! Thank you. Out of curiosity, why did you put the commands in a function? I wonder why it adding that to the go file didn't do the trick.

I am trying to make sysctl changes stick after reboot, specifically sysctl -w fs.inotify.max_user_instances=1024 (I have too many docker containers and Git repos apparently). I tried adding it to /boot/config/go but that didn't work. I also tried creating /boot/config/sysctl.conf and adding it there. Not sure what else to do? Appreciate any help.

Thank you for the link. Would it be safe to say that in order to update the API, the Unraid OS would have to be updated? Essentially we would have to wait for the next stable release of Unraid?

You're a legend mate. Could you link to the PR so I can follow it please?

Looking at the GraphQL sandbox, I don't see temperature options either under metrics → cpu or info → cpu. Is there a way to get the CPU temperature displayed in the dashboard?

Beautiful! How you getting CPU temp? Looking at the GraphQL sandbox, I don't see temperature options either under metrics → cpu or info → cpu.

I tried moving large files from the cache to a new 22TB drive with less than 25% usage and still getting transfer speeds of less than 150 MB/s. What could possibly be causing this bottleneck???

Agree with this. I prefer the method recommended by DiscoverIt method as it is a little closer to Linux standard but I've made a few adjustments below, along with explanations on how it works and why I chose this method. Guide 1. Run this command in terminal: nano /boot/config/ssh/sshd_custom.conf 2. Copy the following into sshd_custom.conf: PermitRootLogin prohibit-password PasswordAuthentication no PubkeyAuthentication yes 3. Save and exit the editor (Ctrl+X, then Y, then Enter) 4. Run this command in the terminal: nano /boot/config/go 5. Copy the following into go: cp -p "/boot/config/ssh/sshd_custom.conf" "/etc/ssh/sshd_custom.conf" sed -i '1i #\n# CUSTOM SSHD INCLUDED IN LAST LINE\n#\n\n' "/etc/ssh/sshd_config" sed -i '$a \\n\n\n\n\n\n\n# Include overriding sshd_custom.conf for SSH key login only\nInclude "/etc/ssh/sshd_custom.conf"' "/etc/ssh/sshd_config" /etc/rc.d/rc.sshd restart 6. Save and exit the editor (Ctrl+X, then Y, then Enter) 7. Optionally, you can run each of the 4 commands individually from Step 5 in the terminal to apply the changes right away without rebooting. Explanation sshd_custom.conf is a custom configuration file for sshd that we created in Step 1 using nano. It is used to override or extend the settings in the default sshd_config file. go is a script that runs automatically at system startup as part of Unraid. It allows you to define custom commands or scripts that should execute each time Unraid boots. cp -p "/boot/config/ssh/sshd_custom.conf" "/etc/ssh/sshd_custom.conf" This command copies the sshd_custom.conf file, created in Step 1, to the /etc/ssh/ folder. sed -i '1i #\n# CUSTOM SSHD INCLUDED IN LAST LINE\n#\n\n' "/etc/ssh/sshd_config" OPTIONAL This adds a few comment lines at the start of sshd_config to indicate that changes have been made. While not necessary, it helps to alert you if you ever need to diagnose SSH settings, especially if Unraid changes how SSH is configured. sed -i '$a \\n\n\n\n\n\n\n# Include overriding sshd_custom.conf for SSH key login only\nInclude "/etc/ssh/sshd_custom.conf"' "/etc/ssh/sshd_config" By default, sshd_config has PermitRootLogin yes, but this will be overridden to PermitRootLogin prohibit-password as stated in sshd_custom.conf. The SSH daemon applies settings in order, which is why the Include command is placed at the end. This ensures that any default settings or future Unraid changes are overridden by your custom configurations. /etc/rc.d/rc.sshd restart This restarts the SSH daemon to apply the new configuration changes.

I'm officially confused... /boot/config/ssh - from my understanding this is basically the USB drive and is persistent What are these two folders for then: /etc/ssh /root/.ssh ? I can successfully SSH into my Unraid server using keys that I entered in the GUI via Settings -> Users -> root -> SSH authorized keys. Now I am trying to git commit to my Gitea docker container using SSH keys but I am unsure where to put the Gitea keys.

How did you know when it was time to replace the battery?

Batteries have to be replaced every year?!?!

Any suggestion on how I could find out if the battery is the cause?

Little over 12 days and no random reboots. One thing I did do was disable Hybrid mode on the PSU and switched it on to constantly on. It is a Seasonic FOCUS PX-750. Maybe some PSU components were getting too hot? If the server reboots again, I am thinking of swapping the PSU to a Corsair RM750x. Curious, what would be the next thing you guys would check or replace?

Downloaded and ran the newest Memtest v11.2 for over 7 hours with 0 errors. After almost finishing the 3rd pass I cancelled the test as I am sure I would have seen at least some errors by now if it was the RAM.

Appreciate you JorgeB for always being so quick to respond and offering sound advice. Sadly running an ASRock RS Pro Z790 that doesn't have SEL. Hmm that's interesting recommendation I would have never thought of. Currently running NUT server on Unraid, wouldn't I see an alert there?

Just started looking for this as I setup Matrix Synapse on Unraid and wanted to transition my notifications from Pushover. I know I could use PushBit but would prefer to use a webhook or Apprise? Hate to have a PushBit container just for Unraid notifications.

Glad you got it sorted! This tripped me up as well.

Fair enough, I will try again on an empty disk. Appreciate the guidance!

Server rebooted around 1:25am this morning and I am trying to find out the cause. Currently undergoing a parity check due to the unclean reboot and so far at 41.1% and 0 errors so far. All drives listed as healthy. The server is on a UPS (APC UPS 950VA). Running an Intel Core i5-14500 on a ASRock Z790 Pro RS (on the latest BIOS) with 128GB (4x32GB) Corsair Vengeance DDR5 RAM. Below are 3 points of info that I can provide to people smarter than me in order to hopefully narrow down the cause: 1. I have syslog server enabled already and this was the log entries before and after 1:25am: Feb 11 01:17:01 Server emhttpd: spinning down /dev/sdf Feb 11 01:17:33 Server emhttpd: spinning down /dev/sde Feb 11 01:17:58 Server emhttpd: spinning down /dev/sdc Feb 11 01:25:46 Server rc.rsyslogd: Syslog server daemon... Started. Feb 11 01:25:46 Server cache_dirs: Arguments=-p 2 -i archives -i media -l off -d 6 Feb 11 01:25:46 Server cache_dirs: Max Scan Secs=10, Min Scan Secs=1 Feb 11 01:25:46 Server cache_dirs: Scan Type=adaptive Feb 11 01:25:46 Server cache_dirs: Min Scan Depth=4 Feb 11 01:25:46 Server cache_dirs: Max Scan Depth=6 Feb 11 01:25:46 Server cache_dirs: Use Command='find -noleaf' 2. Going into the system logs via the GUI, I see the following after the reboot: Feb 11 01:24:54 Server kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks Feb 11 01:24:54 Server kernel: ACPI: Early table checksum verification disabled Feb 11 01:24:54 Server rsyslogd: omfwd/udp: socket 8: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Feb 11 01:24:54 Server rsyslogd: omfwd: socket 8: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ] Feb 11 01:24:54 Server kernel: floppy0: no floppy controllers found Feb 11 01:24:54 Server kernel: i915 0000:00:02.0: [drm] [ENCODER:235:DDI A/PHY A] failed to retrieve link info, disabling eDP Feb 11 01:25:05 Server sshd[2002]: Server listening on 10.14.1.2 port 22. Feb 11 01:25:08 Server mcelog: failed to prefill DIMM database from DMI data Feb 11 01:25:08 Server sshd[2002]: Received signal 15; terminating. Feb 11 01:25:08 Server sshd[2506]: Server listening on 10.253.0.1 port 22. Feb 11 01:25:08 Server sshd[2506]: Server listening on 10.14.1.2 port 22. Feb 11 01:25:24 Server upsmon[5158]: Warning: running as one big root process by request (upsmon -p) Feb 11 01:25:30 Server sshd[2506]: Received signal 15; terminating. I am guessing the rsyslogd errors are there just because the server is starting up and the syslog server didn't start yet. The kernal warning about split_locks, is that something I should be worried about? 3. I have also attached the diagnostic zip file below. What would be the first thing I should look into? Appreciate any guidance in advance! server-diagnostics-20250211-1139.zip

Usually disk5

Make sure you have the correct one installed, I made the mistake of installing the outdated one. There are currently 2 plugins called **Mover Tuning** in the **Community Apps**. The correct version to install has the authors: **Andrew Zawadzki, hugenbdd, and Reynald**, the incorrect plugin has the authors: **Andrew Zawadzki Modified by hugenbdd**.