Tanker

After lots of testing and messing with chat GPT, I seem to have identified the issue and fixed it. I had a script to ffprobe all my media which flagged 8 files that were bad, but the issue persisted even after removing those. Then had a script to watch the ffprobe segfaults and determine which container was sending reports. Bazarr was the container sending the segfaults and it looks to have stemmed from an older version of ffmpeg with older codecs. installed a separate ffmpeg and mapped a path for Bazarr and so far it seems to be working with no errors. Hopefully this helps someone in the future if they ever get a similar issue.

might just have to do that in the near future.

Swapped ports on the router and it seems to have fixed the issue. Wish I had thought of doing that before asking, but appreciate the help!

Tried new cable and issue persists. Changed drivers and it did nothing either. Only one port on the integrated NIC. I could try troubleshooting if its the port or the NIC, but unless I put in a dedicated NIC I worry the MB is cooked then.

Every day for the past couple weeks I have been watching my logs grow and when I check I am met with the following behavior. br0 seems to be struggling but I have no idea why. No changes were made to anything network related since I first set up the system and I either haven't found a solution or simply did not understand the solution if I saw it. I am already dealing with tracking down a segfault issue so I am hoping this will be a quick and easy fix. Thanks in advance. Jul 27 23:56:29 MediaServer kernel: br0: port 1(bond0) entered disabled state Jul 27 23:56:30 MediaServer dhcpcd[2050]: br0: carrier lost Jul 27 23:56:30 MediaServer dhcpcd[2050]: br0: deleting route to 192.168.1.0/24 Jul 27 23:56:30 MediaServer dhcpcd[2050]: br0: deleting default route via 192.168.1.1 ... Jul 27 23:56:34 MediaServer kernel: br0: port 1(bond0) entered blocking state Jul 27 23:56:34 MediaServer kernel: br0: port 1(bond0) entered forwarding state Jul 27 23:56:34 MediaServer dhcpcd[2050]: br0: rebinding lease of 192.168.1.163 Jul 27 23:56:37 MediaServer dhcpcd[2050]: br0: probing address 192.168.1.163/24 ... Jul 27 23:56:42 MediaServer dhcpcd[2050]: br0: leased 192.168.1.163 for 85085 seconds Jul 27 23:56:42 MediaServer dhcpcd[2050]: br0: adding route to 192.168.1.0/24 Jul 27 23:56:42 MediaServer dhcpcd[2050]: br0: adding default route via 192.168.1.1 ... Jul 27 23:57:54 MediaServer kernel: br0: port 1(bond0) entered disabled state Jul 27 23:57:55 MediaServer dhcpcd[2050]: br0: carrier lost Jul 27 23:57:55 MediaServer dhcpcd[2050]: br0: deleting route to 192.168.1.0/24 Jul 27 23:57:55 MediaServer dhcpcd[2050]: br0: deleting default route via 192.168.1.1 mediaserver-diagnostics-20250728-1706.zip

I have 4 sticks total, 2 from the initial build and added 2 not long before the issue started. removed the new 2 and rebooted, no error until I put plex back on then it popped up again. swapped the old for the new and same results, so back to it likely being some plex issue. I did see one other post with similar issues, but waiting to see if they ever found a fix.

Just to add insult to injury I went into Tdarr and requeued some tasks, was met with the following errors in system logs. Jul 9 08:48:31 MediaServer kernel: HandBrakeCLI[44062]: segfault at 147f40d52570 ip 0000147f40d52570 sp 0000147fa5bfd518 error 15 likely on CPU 3 (core 1, socket 0) Jul 9 08:54:42 MediaServer kernel: HandBrakeCLI[149407]: segfault at 1521b02fea30 ip 00001521b02fea30 sp 00001521d85fd518 error 15 likely on CPU 9 (core 4, socket 0) Jul 9 08:55:28 MediaServer kernel: HandBrakeCLI[156443]: segfault at 14c6003027b0 ip 000014c6003027b0 sp 000014c629dfd518 error 15 likely on CPU 10 (core 5, socket 0)Makes me more suspicious that the CPU is either failing or somehow isn't seated properly.

Did you ever find a source for this issue? getting similar errors and identical kernel codes with no luck so far.

Diags finally captured. Hopefully this can help. mediaserver-diagnostics-20250629-1136.zip

diag files didnt want to download for some reason but I can try again. Plex app data was being weird and I moved it into the cache but I think the issues with it are just correlation not causation. rebooted with plex off and waited, still getting the error. Only other container I can imagine using ffprobe is Tdarr so ill try that next.

I can try the codecs folder first and hopefully that can work, any ideas on how to quickly track down the problem file? I have nearly 70,000 videos in my library.

I ran memtest with 3 passes and no issues, I was hoping it would just be some ram sticks to replace and not the CPU.

Jun 24 04:24:31 MediaServer kernel: ffprobe[371562]: segfault at 330 ip 000014bcf74eb822 sp 00007fff6e17d8e0 error 6 in libavcodec.so.60.31.102[2eb822,14bcf7211000+b1a000] likely on CPU 4 (core 2, socket 0) Jun 24 06:52:20 MediaServer kernel: ffprobe[595425]: segfault at 330 ip 0000152f8daeb822 sp 00007ffe5f2ef870 error 6 in libavcodec.so.60.31.102[2eb822,152f8d811000+b1a000] likely on CPU 6 (core 3, socket 0)I have been having this error populate regularly for the last month or so. Usually it is CPU 6, but core and socket change. I don't know if there is correlation, but all Plex users have been having playback issues for approximately the same time. Perhaps also related, the syslog has been slowly filling up, I feel like every time I chase down a fix, it ends up being nothing. Have performed memtest86 and passed with 0 issues. I will provide a diagnostics once it is finished downloading, but is taking a long time. I have tried searching all over for a fix or a cause, but nothing has come up. Any help would be greatly appreciated.