omegajvn

I am running the latest version at 3.6……….but maybe that’s broke something. Good point, I’ll look into that. I wonder if it could be an issue with my cpu and the newer kernel. Maybe there is something wrong with it internally since all I/O goes through the CPUs I/O die. Still weird how it doesn’t happen on 7.2.7 or older

I wonder what could be causing my issue then. I have an H12SSL-NT motherboard. Maybe that’s the issue? Not sure why going beyond 7.2.7 causes the problem though.

Well, to provide everyone with an update, it seems like a kernel level USB regression that affects the Epyc platform. I’ve since moved to internal boot, purchased a TPM 2.0 module, and am going to move licensing off of the USB drive altogether.

Sure do! The unfortunate thing is that it is always abrupt when it happens, apparently. No one has ever been able to find what is wrong from the syslog. It’s an apparent USB issue. I’m hoping that moving to internal NVMe SSD boot fixes the unresponsive occurrences as USB issue no longer the boot device

I'm not going to try troubleshooting this anymore. I've made the jump to internal boot + data on one of my internal NVMe SSDs. I don't believe there should be issues anymore as USB is no longer the booting bus.

Issue it sadly NOT fixed. I wasn't able to make it to 3 days without it becoming unresponsive. I went straight to the servers GUI and it was frozen. I keep a keyboard attached to it and the cursor in the username field was frozen, nor would it accept keyboard input.

Just an update for everyone. I've installed 7.3.2 and as of time of writing, my system uptime is at 1 day and 12 hours. Version 7.2.8 couldn't last that long before going unresponsive due to USB issues. It is early to call, I'm still waiting longer to confirm, but I think the kernel update in version 7.3.2 may have fixed the issue I had.

I’ll give 7.3.2 a go if it had a kernel update. Maybe that fixes the issue.

Why would this happen in 7.2.8+, but not on 7.2.7 or older? Can this be forwarded on to the development team? I’ve tried different USB ports and used my add-on USB expansion card. My system hasn’t been able to last even 24 hours again. I don’t have this issue on 7.2.7 or older. I think this may be an issue with a kernel level usb driver

Out of abundance of caution, I decided to replace the USB drive. Went from a Samsung Bar Plus USB 3.1, to a SanDisk Cruzer Blade USB 2.0. I still had this issue occur. I've included my syslog from today (Aug 4, 2026) only. syslog-192.168.1.100 (Aug 4).log

Hello all. This is initially an issue I faced previously. Link here: Unraid 7.3.1 system becomes unresponsive That was going from 7.2.0, to 7.3.1. I then downgraded back to 7.2.0 because of the issues I experienced with 7.3.1. I upgraded to 7.2.7 and never had issues like before. I recently upgraded to 7.2.8 due to the many security features. The issue began again. So far, it has happened to me twice since installing 7.2.8. This time, I was able to still get some sort of connection to my Unraid server. However, it was a bit odd. I've attached some images to show it, as well as my syslog (which is rather long. I'm paying attention mostly to the end toward July), and diagnostics. It shows my Unraid OS os "Blacklisted" for some reason. I've purchased a Lifetime license, so I'm not sure what that's about. The center message points to my USB drive being corrupt or offline. It's a fairly new (maybe a year old?) Samsung Bar Plus 128GB usb drive. I have a Supermicro H12SSL-NT motherboard with an AMD Epyc 7452 CPU, just FYI. Any ideas? Thanks! syslog-192.168.1.100.log nakunraid-diagnostics-20260802-1906.zip

My system has been online for 12 days and nine hours at the time of writing. It’s pretty safe to say that at this point it is definitely not a hardware related issue.

What’s your current uptime? Previously, how long would your uptime be vs after your finding? Is this an Unraid feature or one installed from the store? I have snapshots for my VMs but no dedicated app

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 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.