Greetings fellow unRaiders!

 

Been a few years since I last posted, happened to go through my system logs today and found a couple errors, (2 servers, one on each), hoping just to get some quick feedback.

Both servers running 6.12.11

 

First server:
Servers been going strong for 6ys now no issues
Error seems to stem from the SSD Cache pool, and started 05:00 yesterday morning with the TRIM scheduler task

Aug 11 05:00:16 Colossus kernel: critical target error, dev sdg, sector 975284261 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2

I confirmed again by manually running TRIM:

Aug 12 18:58:40 Colossus kernel: critical target error, dev sdg, sector 975284261 op 0x3:(DISCARD) flags 0x800 phys_seg 1 prio class 2

Is the SSD Toast?


Second server
Running close to 10 yrs Been having Memory issues when I try to get the board back up to 128GB, still can't tell if it's a memory stick in one of my second sets, or one of the memory banks on the board itself (ASRock EP2C602-4L/D16)

For the time being, I've just gone back to 64GB but the issue is every time I boot now, I get this in the log.  I've read it's nothing to be concerned about a long as the server isn't throwing actual memory errors, (which it's not), just wanted to make sure that's the case.  (I'll continue the hunt for the actual memory error in the system later if so)
 

Aug  7 00:08:50 Juggernaut mcelog: Kernel in lockdown. Cannot enable DIMM error location reporting

Thanks for the feedback, and your time!

Edited August 13, 20241 yr by Drider
grammer

8 hours ago, Drider said:

Aug  7 00:08:50 Juggernaut mcelog: Kernel in lockdown. Cannot enable DIMM error location reporting

This one you can ignore, for the other one, please post the diagnostics.

35 minutes ago, JorgeB said:

This one you can ignore, for the other one, please post the diagnostics.

I would've included the diag, just figured this has come up a few times, and was recognized, and there might be quick "pop it out, check it here", kinda answer.

Diag attached

-Thanks

colossus-diagnostics-20240813-0432.zip

Edited August 13, 20241 yr by Drider

SMART looks good, for some reason that device stopped supporting TRIM, kind of strange, but not sure if means it's failing.

10 hours ago, JorgeB said:

SMART looks good, for some reason that device stopped supporting TRIM, kind of strange, but not sure if means it's failing.

Hmm..

 

I did recently relocate my servers from the racks in my office, back down to the racks in my basement,..  Perhaps one of the breakout cables wiggled around and is causing it?

Maybe I'll go down and wiggle the wires a little and see if it goes away,..