12 hours ago, krasty said:

I am on Intel, Intel N100.

Nothing changed in 7.2.4 that would explain the crashing; the kernel is the same. Please try downgrading and retesting.

So the server has been up and running for a day and a half now and it has not crashed. I did stop docker now and seems like docker is crashing the server.

It is currently doing a parity sync and waiting till that finish before moving to an intel and see if it happens there. I believe it will because it seems related to docker.

10 hours ago, Tucubanito07 said:

I did stop docker now and seems like docker is crashing the server.

Try starting just half of the container; if the same, try the other half, then keep drilling down, it may be a specific container.

@JorgeB I built the nee server with Intel 265K and seems like there is no issues. However, seems like I don't have the option to pass through the Intel quick sync to plex.

eleanor-y-diana-diagnostics-20260307-1801.zip

In Tools - System Devices, is your VGA controller checked?

I don't see it checked. Here is a screenshot @trurl

Delete config/vfio-pci.cfg on flash and reboot.

10 hours ago, Tucubanito07 said:

However, seems like I don't have the option to pass through the Intel quick sync to plex.

I believe that iGPU requires a newer kernel, the first Unraid 7.3 beta should be out very soon, and that release will support it.

20 hours ago, trurl said:

Delete config/vfio-pci.cfg on flash and reboot.

I just did that. Thank you. Does this matter? Maybe intel is not loaded because of the blacklist? I don't know, I don't remember ever placing that there.

cat /boot/config/modprobe.d/i915.conf

blacklist i915

Edited March 8Mar 8 by Tucubanito07

12 hours ago, JorgeB said:

I believe that iGPU requires a newer kernel, the first Unraid 7.3 beta should be out very soon, and that release will support it.

Okay thank you. So, with the new hardware the server crashed again. New Motherboard, New CPU, and New RAM.

I got new logs. So, I disabled all the docker containers and have the service running by itself and see if it crashes. This is very annoying. Here are some new logs in case you see something. I do see some errors but can't make anything out of it. Thank you @JorgeB

eleanor-y-diana-diagnostics-20260308-1735.zip

Edited March 8Mar 8 by Tucubanito07

I assume the syslog in the diags is after rebooting?

56 minutes ago, JorgeB said:

I assume the syslog in the diags is after rebooting?

Once it lock up, I held the power button to turn it off and then once it came back up, I grabbed a support file.

The normal syslog starts over after every boot, you can enable the syslog server to see if it catches something.

23 minutes ago, JorgeB said:

The normal syslog starts over after every boot, you can enable the syslog server to see if it catches something.

I already did that, see screenshot. I’ll check again but I had enabled it already when I had the AMD system.

Edited March 9Mar 9 by Tucubanito07

You would need to separately attach the log file that is being stored in the 'restore' share as that is not automatically included in the diagnostics.

1 hour ago, itimpi said:

You would need to separately attach the log file that is being stored in the 'restore' share as that is not automatically included in the diagnostics.

I apologize, I didn't know. Here it is.

syslog-10.10.1.43.log.zip

Mar 8 17:14:30 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303807 exited on signal 9 (SIGKILL) after 25.402777 seconds from start

Mar 8 17:14:48 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303817 exited on signal 9 (SIGKILL) after 24.972842 seconds from start

Mar 8 17:14:53 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303827 exited on signal 9 (SIGKILL) after 21.638930 seconds from start

Mar 8 17:15:02 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303828 exited on signal 9 (SIGKILL) after 24.133611 seconds from start

Mar 8 17:15:19 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303838 exited on signal 9 (SIGKILL) after 27.755060 seconds from start

Mar 8 17:15:27 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303848 exited on signal 9 (SIGKILL) after 28.885932 seconds from start

Mar 8 17:15:34 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303858 exited on signal 9 (SIGKILL) after 30.369778 seconds from start

Mar 8 17:15:47 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303869 exited on signal 9 (SIGKILL) after 25.853157 seconds from start

In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.

It could also be one or more containers hogging the CPU, try pinning only some cores to them, and leave cores 0/1 available for Unraid.

Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

7 minutes ago, JorgeB said:

Mar 8 17:14:30 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303807 exited on signal 9 (SIGKILL) after 25.402777 seconds from start

Mar 8 17:14:48 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303817 exited on signal 9 (SIGKILL) after 24.972842 seconds from start

Mar 8 17:14:53 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303827 exited on signal 9 (SIGKILL) after 21.638930 seconds from start

Mar 8 17:15:02 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303828 exited on signal 9 (SIGKILL) after 24.133611 seconds from start

Mar 8 17:15:19 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303838 exited on signal 9 (SIGKILL) after 27.755060 seconds from start

Mar 8 17:15:27 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303848 exited on signal 9 (SIGKILL) after 28.885932 seconds from start

Mar 8 17:15:34 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303858 exited on signal 9 (SIGKILL) after 30.369778 seconds from start

Mar 8 17:15:47 Eleanor-Y-Diana php-fpm[10926]: [WARNING] [pool www] child 1303869 exited on signal 9 (SIGKILL) after 25.853157 seconds from start

In my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.

It could also be one or more containers hogging the CPU, try pinning only some cores to them, and leave cores 0/1 available for Unraid.

Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this:

https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-down

I have 32 gigs of ram and I see that there is 28.6 available. Obviously, I have the containers off but the docker service on. I also checked in Settings under Docker and I don't see where I can limit the Ram usage. Do you know where that settings is located?

I just ran this command "touch /boot/config/fastusr". I have to stop the array to change that setting in Global Share settings as well. I know I have to reboot but I am doing a Parity Sync and waiting for that to be finished so I can reboot and see if that helps.

Also, I will pin cpu on some of the containers and see if that helps but once the parity sync finishes. I ran one first to fix the sync errors and now running another one to make sure it is good before continuing. I will let you know what comes of the steps you advise to take. Thank you @JorgeB

Had the same issue with 7.2.4. Never had a single problem on my 9950X/ProArt X670E before 7.2.4.

After upgrading, I would have a crash every 12 hours - and syslog would not capture any issues. No changes in hardware/bios/or ram - all tests I tired passed with no issues. Tried upgrading the bios then with conservative settings and still crashed.

After downgrading back to 7.2.3 - system is 100% stable. So, it seems there is something causing stability issues in 7.2.4.

I have 2 other systems with AMD Ryzen 5 5500U and Ryzen 5 3600 - that both upgraded to 7.2.4 and have no stability issues. So, something with the newer AMD CPUs.

Since the kernel is the same, there might be a driver issue impacting newer AMD CPUs/Motherboards and causing crashes?

Edited March 9Mar 9 by mutunekk

11 hours ago, mutunekk said:

Since the kernel is the same, there might be a driver issue impacting newer AMD CPUs/Motherboards and causing crashes?

The kernel includes the drivers; they are all the same, really doubt the upgrade was the problem.

On 3/7/2026 at 11:06 PM, Tucubanito07 said:

However, seems like I don't have the option to pass through the Intel quick sync to plex.

Looks like I was wrong, I now have confirmation that 245K works with Plex in 7.2.4 using stock settings.

1 minute ago, JorgeB said:

Looks like I was wrong, I now have confirmation that 245K works with Plex in 7.2.4 using stock settings.

Now the real question is, why it does not work for me? If the requirement is 7.2.4 and is the same kernel as 7.2.3, then it should work on the version Ami am on.

Recommend starting a new thread and posting the diagnostics there.

12 minutes ago, JorgeB said:

Recommend starting a new thread and posting the diagnostics there.

I just started a new thread for that issue. Thank @JorgeB . I will let you know once my Parity Sync is done and completed everything you recommended.

Should I still have this on my GO file. I no longer have a AMD.

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/zenstates --c6-disable

/usr/local/sbin/emhttp