April 7, 20251 yr This morning I woke up to hardware errors reported by Fix Common Problems, but I am unable to figure out what the error is. Can someone review my diagnostics and help point me in the right direction? I'm running some fairly old equipment, so I would not be surprised if the hardware error is legitimate. supermicro-diagnostics-20250407-0947.zip
April 7, 20251 yr Community Expert when they occur its bet to stop unriad reboot and at grub boot launch run mem test. most times this is ece ram checks and a flag to mcelog that ram corrected itself. I'm not seeing anything specific in the diag. This may be a one off event. However you do have something filling up the casche... Quote Apr 3 08:12:50 SuperMicro shfs: share cache full ### [PREVIOUS LINE REPEATED 57 TIMES] ### Apr 3 11:01:59 SuperMicro kernel: ffprobe[1455135]: segfault at 330 ip 00001509320eb822 sp 00007ffeb1664d00 error 6 in libavcodec.so.60.31.102[150931e11000+b1a000] likely on CPU 29 (core 5, socket 0) Apr 3 11:01:59 SuperMicro kernel: Code: 74 33 cc 00 49 8b 17 48 85 d2 74 27 be 01 00 00 00 48 89 ef ff 15 36 38 cc 00 48 85 c0 0f 84 75 06 00 00 49 c7 07 00 00 00 00 <41> 83 8c 24 30 03 00 00 02 41 8b 4f 28 85 c9 74 49 49 8b 47 20 31 Apr 3 11:06:40 SuperMicro shfs: share cache full ### [PREVIOUS LINE REPEATED 4 TIMES] ### Apr 3 11:07:54 SuperMicro webgui: Successful login user root from 192.168.1.63 Apr 3 11:08:27 SuperMicro shfs: share cache full ### [PREVIOUS LINE REPEATED 1 TIMES] ### Apr 3 11:08:28 SuperMicro monitor_nchan: Stop running nchan processes Apr 3 11:09:40 SuperMicro shfs: share cache full ### [PREVIOUS LINE REPEATED 464 TIMES] ### Edited April 7, 20251 yr by bmartino1 Data
April 7, 20251 yr Author Thanks. I currently have a Parity check running, which I believe was already in progress when I downloaded the diagnostics this morning. I'm going to wait for that to complete before I try to the mem test on reboot. Thanks for pointing out the "share cache full" errors as well. Once the parity check is done I will review that issue as well.
July 6, 2025Jul 6 Did you ever find a source for this issue? getting similar errors and identical kernel codes with no luck so far.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.