Server freezes in 6.12.6 - not macvlan or realtek related

First things you should always do in any situation like this is run Memtest from the boot menu for at least a couple of passes.

 

To roll back though, all you have to do would be to download the appropriate .zip file from https://unraid.net/download

 

Shutdown the server, pull out the flash and replace all of the bz* files in the root of the flash drive with those in the archive.  Power back up.

 

Alternatively you can also create a folder on the flash drive named "previous" and put all of the files in the root of the archive into that folder and then Update OS will offer you a rollback option

Thanks! I ran memtest off the boot drive and it seemed to freeze after printing "Loading memtest... ok". I'll poke around to see what that's about; I don't see my exact motherboard listed here but there are some very similar ones that seem to have issues. Copying the 6.12.4 files into a "previously" folder did give me an option to rollback through the web GUI again, but I'm going to hold off to see if I can get useful syslog info out of the current distribution before I do so.

 

If I do roll back, I assume it will still use my old configs, right? (So I won't need to set up my dockers and array again?)

Edited January 1 by thither

Well, the system froze again and I restarted it. Here's my syslog and syslog-previous from the flash drive. I restarted at around 4:00am, and then again this morning at 10:30. I personally can't see much suspicious here, I have community apps set to auto-update nightly and that runs. It does seem a  little weird that the system boots at 4:08 and the "Unraid API started" message doesn't appear until 7:30, but I don't know how normal that is.

 

Anyways, I'm going to roll back to 6.12.4 and will report back on whether that seems more stable.

syslog.txt syslog-previous.txt

Do you use NFS a lot? I've had a lot of issues with Unraid freezing up with the symptoms you describe (server is still up, but unresponsive and login attempts freeze), which seemed to be related to NFS in my case. The ultimate cause was shfs deadlocking itself for whatever reason, causing most disk I/O to get stuck until it was killed (or the server was power cycled, since it couldn't perform a proper shutdown).

 

I had the issue on 6.11.5 but it became much worse when I upgraded to 6.12.6 to see if that would fix my problems.

 

It looks like my issue is related to a long standing issue.

I'm not running NFS, no.

 

Actually I just downgraded back to 6.12.4 and while the system was stable for longer, it's now frozen up again. I'm guessing this points to some kind of hardware fault in my server, which just happened to rear its head after the upgrade.

Thinking about this a little more, the weird thing is that it seems like something is just eating up all the CPU, whereas I would expect a hardware fault to result in a kernel panic or something.

 

Is there something I can run that will give me a graph or log of historical CPU load, or maybe load per docker container or something?

As a historical note, I downgraded back to 6.11.5 and have had 2 months, 14 days of uninterrupted uptime since then.

Edited May 22 by thither