My unraid server started to act strangely lately. At first, I suspected a one-of problem, but it is recurring...
To help in my diagnostic, I moved the server close to me and plugged a keyboard and monitor to it.

Symptoms: The server seemed te "hang", but was still able to reply to pings. A reboot seemed to be enough to fix the problem.

I think I can trigger the bug by asking to D/L a USB Flash backup. So, I suspected an issue with the USB key, but I'm able to do a full copy of the key in Windows, so the USB Flash drive isn't defective (if it is, it's not apparent).

On the console, I get the login prompt and the server is responsive when it "hangs", but when I type in my user/pw, it will timeout after 60 seconds. Is there any troubleshooting I could do? Log I could open/read from the console immediately after a boot?

Another possible thing that could happen is the parity check on the array and because of some problem (hardware?) would pin the CPU and/or a process?

Thanks for your tips and help in advance.

Edited February 3Feb 3 by LEKO

I may have found the root cause.

In safe mode, I was able to boot and login. Then, I started my array then immediately shutdown the Jellyfin docker (my only docker). So far, the server is responsive and it is running a parity check because of all "hangs" and hard reset I did. They array didn't liked it.

Attach Diagnostics ZIP to your NEXT post in this thread.

Attached anyway. I would like to learn of there's any clue in the diag.

tower-diagnostics-20260204-1950.zip

It is really my JellyFin docker. Once I start it, memory usage increase until the system become unresponsive.
I'll try to reinstall it, a "force update" didn't worked.

Update: even a fresh install cause the same problem. I suspect some data is corrupted in my media collection.

Edited February 5Feb 5 by LEKO

Didn't see any evidence of corruption in syslog from those earlier diagnostics. You could post new diagnostics now that you have a fresh install.

Setup syslog server

Tried again and again... I suspect of the file Jellyfin is trying to parse to be corrupted. The last number I saw before giving up was 260g of memory being used by Jellyfin! Ouch!

And nothing in the Jellyfin log helps. I don't anything suspicious or obvious: no specific file being loaded. I'll try to figure out if I can make jellyfin log more stuff.