Hi everyone,

First off, apologies for any errors or ignorance on my part. Both in my expertise (or lack of) with Unraid and with the forum rules. While I have been able to navigate the challenges of setting up my own Unraid home server, I am definitely out of my depth here.

Over the last few weeks my Unraid server has been consistently shutting down unexpectedly. I think I have narrowed the potential issues to either the max_children setting or alternatively potentially hardware issues. Before I start making changes it would be great to confirm the best actions to take.

With a bit of googling I think that potentially I could change from maclan to ipvlan, and potentially address issues setting up a VLAN on my Unifi network. Or alternatively, it may be a CPU issue, and I potentially replace my CPUs in the server.

I have been able to cobble this home server together with second hand parts, and for the most part, it has run extremely well. Recently I have been going through the process of adding several new 8TB drives, and while that has been tedious process... I seem to still have a functioning array, with no issues... aside from these shutdowns. Not sure if they are related to the issues I am having. However, due to the server being mostly second hand parts, hardware issues are a realistic possibility. But looking at the logs... I am uncertain.

I have included diagnostics and syslog. Hopefully these don't display any vulnerable information.

Any help and guidance would be appreciated.

Thanks!

titan-diagnostics-20260217-1644.zip 2026-02-17.rar

If the server is actually powering down by ittelf, that's typically a hardware issue, but just to make sure nothing is initiating a shutdown, enable the syslog server and post that after the next event.

Not sure what rar file is supposed to be, but it's not logs.

Yeah sorry about that. Here are the syslog file while it happened a couple of times today.

syslog.txt

Edited February 17Feb 17 by Nassai

Feb 17 11:49:05 Titan emhttpd: read SMART /dev/sda

Feb 17 11:53:09 Titan plugin-manager: checking: /boot/config/plugins/unassigned.devices.preclear/tmux-3.4-x86_64-1.txz - MD5

I assume one of times happened between these two lines, and since there's no shutdown initiated, it suggests a hardware issue, PSU would be a good place to start; also, make sure the CPU is not overheating.

3 hours ago, JorgeB said:

Feb 17 11:49:05 Titan emhttpd: read SMART /dev/sda

Feb 17 11:53:09 Titan plugin-manager: checking: /boot/config/plugins/unassigned.devices.preclear/tmux-3.4-x86_64-1.txz - MD5

I assume one of times happened between these two lines, and since there's no shutdown initiated, it suggests a hardware issue, PSU would be a good place to start; also, make sure the CPU is not overheating.

Thanks for the help.

So I installed the Dynamix System Temp to monitor the CPU temps.

This jumped out to me... but this can't be right?

Those look like a false reading.

2 hours ago, JorgeB said:

Those look like a false reading.

Hope so.

So I will start the array, watch the CPU temps. And hopefully that will give me an indicator of next steps.

Thanks again for your help!

16 hours ago, JorgeB said:

Feb 17 11:49:05 Titan emhttpd: read SMART /dev/sda

Feb 17 11:53:09 Titan plugin-manager: checking: /boot/config/plugins/unassigned.devices.preclear/tmux-3.4-x86_64-1.txz - MD5

I assume one of times happened between these two lines, and since there's no shutdown initiated, it suggests a hardware issue, PSU would be a good place to start; also, make sure the CPU is not overheating.

Okay, I think it is the CPU overheating. I was watching the temps as closely as I could, and keeping an eye on the CPU usage on the dashboard and after starting the array for several minutes, everything was fine... however the CPU usage spiked... and then shortly after the system shut down.

I have ordered a couple of new CPUs... I will install and try those when they arrive hopefully later this week. And mark this thread as resolved if it sorts it out.

7 hours ago, Nassai said:

Okay, I think it is the CPU overheating. I was watching the temps as closely as I could, and keeping an eye on the CPU usage on the dashboard and after starting the array for several minutes, everything was fine... however the CPU usage spiked... and then shortly after the system shut down.

I have ordered a couple of new CPUs... I will install and try those when they arrive hopefully later this week. And mark this thread as resolved if it sorts it out.

Just to check the obvious, have you checked the CPU fans are working properly, and also that it is not a case of dried out thermal paste on the CPUs.

On 2/18/2026 at 9:22 PM, itimpi said:

Just to check the obvious, have you checked the CPU fans are working properly, and also that it is not a case of dried out thermal paste on the CPUs.

Thanks for that, so when upgrading the CPUs, I did check the fans and the thermal paste... All seemed fine.

On 2/17/2026 at 9:24 PM, JorgeB said:

Feb 17 11:49:05 Titan emhttpd: read SMART /dev/sda

Feb 17 11:53:09 Titan plugin-manager: checking: /boot/config/plugins/unassigned.devices.preclear/tmux-3.4-x86_64-1.txz - MD5

I assume one of times happened between these two lines, and since there's no shutdown initiated, it suggests a hardware issue, PSU would be a good place to start; also, make sure the CPU is not overheating.

Unraid loaded fine with the new CPUs... but when I started the array in seconds the machine shut down.

I am guessing through the process of elimination it is the PSU? The machine idles fine without the array starting, for days... However I am assuming that when all the devices are drawing power the PSU is crashing then?

3 hours ago, Nassai said:

However I am assuming that when all the devices are drawing power the PSU is crashing then?

It's possible.

4 hours ago, JorgeB said:

It's possible.

I have used a spare ITX powersupply. And it is running fine so far. I have ordered a replacement PSU.

Thanks for your help. Marked as resolved.