Hi UnRaiders,

I’m reaching out for some help with an issue I’ve encountered. Fix Common Problems has reported an error and suggested I post my diagnostics here. Could someone more knowledgeable take a look to help identify what might be going wrong with my server?

I also noticed the following error in the logs:
 

Cubus kernel: ffmpeg[26609]: segfault at 152b4f960ee8 ip 0000152b57c921eb sp 00007ffcf0d59200 error 4 in libavformat.so.60.16.100[152b57c0f000+1ce000] likely on CPU 6 (core 6, socket 0)

I’m not sure if this is related to the issue flagged by Fix Common Problems or just a separate occurrence.

For context, the server has been running quite stable for the past six months since I upgraded the CPU.

I’ve attached the diagnostics file for review. Any insights or guidance would be greatly appreciated.

Thanks in advance!

cubus-diagnostics-20250120-0956.zip

Jan  6 01:03:31 Cubus kernel: ffmpeg[22669]: segfault at 14ba0c15aee8 ip 000014ba146921eb sp 00007fffd76914b0 error 4 in libavformat.so.60.16.100[14ba1460f000+1ce000] likely on CPU 7 (core 7, socket 0)

 

I'd start with running a memtest from the boot menu for at least a couple of passes.  Quite often (not always) segfaults can be caused by memory issues.

 

The mce has nothing to do with this initially, and is listed as a "corrected" error, but again may also be memory related

5 hours ago, Mati369 said:

Hi UnRaiders,

I’m reaching out for some help with an issue I’ve encountered. Fix Common Problems has reported an error and suggested I post my diagnostics here. Could someone more knowledgeable take a look to help identify what might be going wrong with my server?

I also noticed the following error in the logs:
 

Cubus kernel: ffmpeg[26609]: segfault at 152b4f960ee8 ip 0000152b57c921eb sp 00007ffcf0d59200 error 4 in libavformat.so.60.16.100[152b57c0f000+1ce000] likely on CPU 6 (core 6, socket 0)

I’m not sure if this is related to the issue flagged by Fix Common Problems or just a separate occurrence.

For context, the server has been running quite stable for the past six months since I upgraded the CPU.

I’ve attached the diagnostics file for review. Any insights or guidance would be greatly appreciated.

Thanks in advance!

cubus-diagnostics-20250120-0956.zip 472.44 kB · 1 download

 

Are you encoding video by chance? I've noticed this segfault specifically when abruptly stopping handbrake when encoding video with my intel arc gpu

Here’s what happened:

• To eliminate variables, I detached hardware – removed all PCI cards and disconnected USB devices except for a keyboard. I kept the HDDs and NVMe drives connected.
• I ran memtest86 overnight. The first pass completed successfully, so I left it running.
• By morning, I was greeted with a black screen and no response from the server. IPMI was still functional, but all sensors showed no connections, and I couldn’t restart the server through IPMI (no response at all).

This was frustrating, so I decided to check for a BIOS update for the X470D4U motherboard. I was previously running version 4.26 (6/21/2022) and found a newer version, 4.29A (4/11/2024).

Here’s what I did:

1. Powered off the PSU manually, back on, flashed the new 4.29A BIOS, and rebooted.
2. Ran memtest86 again.
3. After approximately 8 hours, I was greeted with 4 successful passes and no issues.

I booted into unRaid, and so far, no new issues have been flagged by Fix Common Problems. My conclusion for those using the X470D4U with a 5950X: if you’re encountering issues, consider updating to the latest BIOS version. You can find it here:
ASRock Rack X470D4U Downloads

Big thanks to @Squid for your amazing plugins and all your support!

What’s still persisting:
I still see the following errors in my logs:

 

Cubus kernel: ffmpeg[26609]: segfault at 152b4f960ee8 ip 0000152b57c921eb sp 00007ffcf0d59200 error 4 in libavformat.so.60.16.100[152b57c0f000+1ce000] likely on CPU 6 (core 6, socket 0)

 

@MowMdown
This server is used for video encoding, primarily via Jellyfin (using a GPU for transcode and trickplay) and Immich (also GPU-based).

If anyone has insights into this error, I’d greatly appreciate your thoughts.

I suspect a GPU driver bug more than anything given it's an FFMPEG related segfault. I can replicate a very similar segfault if I start an encode with handbrake and cancel the encode while it's running.

@Mati369

 

I think us talking about my own MCE caused another one on my own server

 

Feb  4 01:33:12 PlexRAID kernel: mce: [Hardware Error]: Machine check events logged
Feb  4 01:33:12 PlexRAID kernel: [Hardware Error]: Deferred error, no action required.
Feb  4 01:33:12 PlexRAID kernel: [Hardware Error]: CPU:1 (19:21:2) MC17_STATUS[-|-|-|-|-|-|Deferred|-|-]: 0x9090909090909090
Feb  4 01:33:12 PlexRAID kernel: [Hardware Error]: IPID: 0x0000000000000000
Feb  4 01:33:12 PlexRAID kernel: [Hardware Error]: Bank 17 is reserved.
Feb  4 01:33:12 PlexRAID kernel: [Hardware Error]: cache level: RESV, tx: INSN

 

Here's what popped up the other day. Didn't notice it until now, this makes it MCE #2 for me.