Like many others that I've seen on the forums lately, I too am suffering from my server becoming unresponsive after some amount of time.

My server has been unable to go more than 3 days without this issue happening. I have to manually reboot the system (holding the power button to shut it off) for it to become responsive. Obviously, I'll continue to cancel a Parity Check because of this. I've looked at the syslog-previous because I'm trying to diagnose this and it just looks like it abruptly ends. I've tried inputting this into Gemini, which also says the same thing.

The GUI is unreachable from another PC on the network. I can ping my servers IP address from my gaming PC, but trying to SSH into it, I get a connection refusal. I have a Windows 11 VM running on it. In the VM, I've seen it once where Unraid turns on all disks that are not on and then it starts the process of stopping the array. It never seemed to get there completely as eventually, my VMs just die. My server never reboots. It just stays powered on and completely unusable.

I was considering downgrading back to 7.2.0 that I came from. I'm glad I'm not the only one experiencing this. I'm on an AMD Epyc Platform.

Motherboard: Supermicro H12SSL-NT, BIOS 3.6

CPU: Epyc 7452

RAM: Samsung ECC RDIMM 3200

PCIe ACS Override is set to Both, as well as disabling the following features for trying to troubleshoot: USB Autosuspend, NVMe Deep Power States, PCIe ASPM, and PCIe Port PM

Containers running: Immich via Docker Compose Plus, two instances of Handbrake, Emby, JellyFin, Plex, Tautulli, VM_Custom_icons (these have not changed from when I was on 7.2.0, which I was not experiencing this issue).

I've attached a recent diagnostics zip file. I'm going to wait for when this happens again and I'll provide a syslog. I currently setup the syslog-server.

nakunraid-diagnostics-20260619_1102.zip

@JorgeB My apologies if I shouldn't be tagging you. Let me know if I can do this or not.

It the issue just happened again today. I've attached the Diagnostics and Syslog-Server. I think it happened at Jun 22 08:40:48 in the logs.

I also noticed when I tried to access my server via my tailscale IP address, the GUI was trying to put me through the new Onboarding Wizard. I thought it was weird that I could access it when this happened, but I have no idea why it would put me through the onboard wizard when I already did that. I attached a screenshot of my phone when I accessed it. While going through the wizard, the screenshot is what came up for a split second. I had to screen record to capture the image. It looks like there was something wrong with the license?

omegajvn1-diagnostics-20260622-1655.zip syslog-192.168.1.100.log

Nothing relevant was logged that I can see in the last lines before the crash, except maybe the Docker Compose lines; they don't look normal, but it may be worth retesting with the Docker engine disabled, or trying to run half the containers you have; if it still crashes, try the other half.

Jun 22 07:00:16 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 07:05:44 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 07:30:19 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 07:33:49 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 07:35:47 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 08:00:22 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 08:03:51 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 08:04:05 NakUnraid emhttpd: spinning down /dev/sdb

Jun 22 08:05:50 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 08:30:25 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 08:35:53 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 08:40:48 NakUnraid compose.manager: [INFO] [nchan] publisher starting

Jun 22 16:51:43 NakUnraid rc.rsyslogd: Syslog server daemon... Started.

Any thoughts on what it could be? I know other people are having very similar issues...

Edited June 24Jun 24 by omegajvn

I also started seeing hard hangs a couple weeks ago after updating to 7.3.1. I thought it was just me and replaced my HBA and my power cables thinking it's a hardware issue because of the abrupt stops in the logs

8 hours ago, omegajvn said:

Any thoughts on what it could be?

Since there's nothing relevant logged, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the individual docker containers.

7 hours ago, LumberJackGeek said:

I also started seeing hard hangs a couple weeks ago after updating to 7.3.1. I thought it was just me and replaced my HBA and my power cables thinking it's a hardware issue because of the abrupt stops in the logs

Yea the abrupt stop in logs is what's most annoying. At this point I'm ready to just reflash my USB drive back to the 7.2.0 image I made prior to upgrading to 7.3.1.

Very frustrating...

You can try downgrading to the previous known good release with your server to make sure the issues are related to the update.

On 6/24/2026 at 6:03 AM, JorgeB said:

You can try downgrading to the previous known good release with your server to make sure the issues are related to the update.

Yes sir. I moved back to 7.2.0. For some reason 2 of my disks dropped out of my array. I had to performance a New Config with Preservation to get them back in. Currently rebuilding parity. Once that is done, I'm going to backup, then upgrade to 7.2.7. I noticed that the docker version changes from 7.2.0 to 7.2.7. Maybe this could trigger the issues I was seeing previously. Maybe not. We'll see.

I wanted to chime in to say "me too".

I was on 7.2.6 previously. Not much has changed in my config - a new docker stack to replace two existing dockers. As others have reported, Unraid becomes completely unresponsive. Even the local CLI interface is (mostly) unresponsive. I have a login prompt which I can type a username in, but on pressing enter, I am never prompted to input a password, and after a minute or so, a timeout occurs and Im back to a username prompt.

I can't seem to find a way to tell when I upgraded to 7.3.1 but the files on my boot flash show May 27th which seems about right. My crashing issues only started about 5-7 days ago though. I've had 3 crashes since. Always the same. Once this morning, once yesterday, and once several days before. The one yesterday was particularly interesting because my bzmodules file on the USB ended up corrupted (it's SHA256 hash didn't match the hash file anymore, despite it's size being identical to the original) so I had to reapply a stock file.

In my particular case, I run 19 dockers, my docker.img is usually around 79% used (I increased the size eons ago to 50gb). I have 32gb of RAM and usually am around 40% to 50% used, with System using about 2.7gb, VM (just 1) using 2.3gb, and docker using the rest (about 7.5 to 10gb).

My crash yesterday was interesting as it happened immediately after I finished watching a show on Plex (docker) and I couldn't watch another so I went to my computer. The Unraid dashboard was already on my browser, though unresponsive, and it showed the RAM usage at 94%. Unsure if this is related or not.. on rare occasions the ram consumption does shoot up pretty high but thats usually during some specific video transcoding process.

I think we can pretty much rule out hardware failure. I believe I've seen about 3 or 4 other posts about this issue so I think it's extremely unlikely all of us are having hardware failures of some sort after this upgrade. That and Unraid support has told me in the past they suspected a hardware failure (on a different issue) and recommended replacing the ($500) motherboard. I did that at the time and the issue of the time persisted, so I'm very hesitant to accept a generic "hardware issue" answer as a cause until it can be well proven.

If this persists and there are no findings as to cause, I will be forced try unraid-diagnostics-20260626-0807.zipto go back to 7.2.6.

I am inclined to agree. I went back to 7.2.0, and I'm currently rebuilding parity and I'm at 1 day and 15 hours in (2 disks fell out of the array for some reason). I've had multiple "unresponsive states" occur with 7.3.1. If I go another 24 hours without it occuring, it will be the longest time it's gone without the issue happening. If that does come to pass, it is definitely a 7.3.0/7.3.1 issue. I'll try upgrading to 7.2.7 for the security updates, but I'll wait the last 7.3.X update prior to 7.4.X to have these bugs ironed out.

Just a quick update.

I downgraded back to 7.2.0, then upgraded to 7.2.7 successfully. Rebuilt my parity as 2 drives fell out of the array for some reason. The only issue I've experienced is that it takes a bit longer for VM's to startup. Might be from security vulnerability fixes? Not sure. But at time of writing, the uptime has been 3 days 22 hours 57 minutes. This is the longest time that I've gone without any issues, as opposed to when I was on 7.3.1. I'm now convinced that it is not a hardware issue, but one with 7.3.1. I'm not trying to be harsh, but I think there is more ironing out that needs to happen with the 7.3.X update.

I figured I'd chime in with my own update.

Since I had those 3 crashes very closely together.. I have not had another one since. knocks on wood immediately

I now have 6 days, 5 hours of uptime. With all my usual stuff running.

Still on 7.3.1.