44
Dealing with faulty RAM modules in 2026 (blog.kumio.org)
submitted 10 months ago by to c/selfhosted@lemmy.world
11 comments fedilink hide all child comments
 

How to test and safely keep using your janky RAM without compromising stability using memtest86+ and the memmap kernel param.

you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 10 months ago (2 children)

Very cool to be able to do that even though I'm not sure it's worth it to run a RAM module that has a known defect.

If the fault spreads there will be corruption again.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 7 points 10 months ago* (last edited 10 months ago) (1 child)

    There is one part in the post mentioning how to "pad holes" in failing areas. Maybe I should expand it with some details around aligning reserved address space.

    Otherwise, corruption of the RAM itself does not usually spread like mold in bread or wear out and fail in similar ways to flash memory.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 10 months ago

    By spreading I meant thar if there is an underlying manufacturing defect it would be really difficult to predict where and when it would happen on memory. And if there is already a fault detected more might come later.

    But I'm glad you documented how to do these types of workaround. It might be helpful with memory prices skyrocketing...

  • permalink
  • fedilink
  • source
  • parent