Diagnostics file generated today 6/25/24 11:19 AM EST.

Crash occurred earlier around 10:50AM-11:00AM EST after enabling automatic scan on plex server.
I saw an error 4 and error 7 related to plex scan so I disabled automatic scan on plex server and a few minutes after server became unresponsive and disconnected from my network.

Hard reboot did not initially work.
Turned off again unplugged Unraid stick was able to boot into BIOS.
Plugged stick in again and rebooted second time Booted into Unraid no problem.

Can access console and through WebUI.

 

lyftserver-diagnostics-20240625-1118.zip

Diags are after rebooting so not much to see, enable the syslog server and post that after a crash, or if you think Plex is the problem, post in the appropriate container support thread:

 

 

Thanks JorgeB, I attached the relevant syslogs generated prior to crash.

syslogs20240625.txt

I don't use Plex, but I'm used to seeing a lot of those Plex Media Scan segfaults on various users diags, so possibly those are harmless, what is not normal is this:

 

Jun 25 10:15:43 LyftServer kernel: mce: [Hardware Error]: Machine check events logged

 

And all the other call traces, suggesting you may have a hardware issue, start by running memtest.

Thank you will run memtest and report back.

 

 

Server was actually up and running this past week until late on 28th June.
After it froze again and became unresponsive, unreachable from webgui etc I ran Memtest.

It passed, ran 8 passes all 8 passes. Which is strange considering I thought the RAM would be the culprit.

But after looking at the logs it seems like to me at least:

Quote

Jun 28 09:02:58 LyftServer kernel: Plex Media Scan[25177]: segfault at 23d0 ip 00001471f11ae4a3 sp 00007ffdca2c5e00 error 4 in libopencv_dnn.so.405[1471f10fc000+1ef000] likely on CPU 8 (core 16, socket 0) Jun 28 09:02:58 LyftServer kernel: Code: c2 48 8b 85 10 ff ff ff 48 03 85 98 fa ff ff 48 89 85 10 ff ff ff 44 03 8d 1c fe ff ff 4c 3b 95 08 fc ff ff 0f 85 74 ff ff ff <4c> 8b 45 c8 4c 8b 8d b0 fe ff ff 48 8b 8d 78 fe ff ff 4c 8b 9d 58

My CPU might be the culprit? I had ran prime 95 to burn in for about 8 hours and my 14900k hadn't crashed, it was running fairly hot but I only have a 120mm peerless assassin cooling it.
 

Attached new sys logs and diagnostics zip.

EDIT:

If it really is looking like a plex issue I will move my discussion to the plex container. Thank you.

 

lyftserver-diagnostics-20240629-0846.zip syslog-192.168.0.106.log

Edited June 29, 20242 yr by iamlyft
added additional context.

20 hours ago, iamlyft said:

My CPU might be the culprit?

It's a possibility, though as mentioned those Plex Media Scan segfaults appear to be harmless, but if are you still getting MCE errors, there's likely a hardware issue.

I also have these segfaults with one just now.

These do trigger a notification on my plex android devices "Plex database was found to be corrupt" and plex continues to play the whole time and I can't tell if there is any corruption.  Contributing my diags to help the cause because this is quite annoying.

 

tower-diagnostics-20241015-1031.zip