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

  • TheHolm@aussie.zone
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 days ago

    Imho not worth the risk. Nothing except ECC is protecting system from memory corruption. And consequences of flipped bit can be huge. Unless it is in a system you do not care about, just do not use it.

  • Passerby6497@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 days ago

    I tried this for a bit last year, and I never got it to work. I’m sure it was user error, but I’m super glad I got a new kit before shit blew up.

    Might have to track down the bad kit I had and give this another try for giggles.

  • Tetsuo@jlai.lu
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 days ago

    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.

    • kumi@feddit.onlineOP
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      edit-2
      2 days ago

      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.

      • Tetsuo@jlai.lu
        link
        fedilink
        English
        arrow-up
        3
        ·
        2 days 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…

  • linuxgator@lemmynsfw.com
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    4
    ·
    2 days ago

    First rule in computer building is to always buy twice as much RAM as you actually need so you can just remove the bad stick when this happens

    • muusemuuse@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 hours ago

      Second rule of computer building is just keep the receipt until after it passes 40 minutes of memtest. Third rule is to ignore rule one, nobody does that.

    • kumi@feddit.onlineOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      22 hours ago

      I always heard the first rule as “stay grounded”. Having 1TB of RAM on stock just in case sounds not grounded.

      A spare kit or two should be enough for most folks. With one or two spares of everything else so you can test suspicious parts separate from prod.

      A bit of redundancy and foresight is good but no need to be excessive about it.

        • kumi@feddit.onlineOP
          link
          fedilink
          English
          arrow-up
          2
          ·
          edit-2
          19 hours ago

          OK, so let’s cut it down and say we have 4 PCs for someone with a family and home server, each with 4 DIMMs each.

          You are saying the first rule of PC building says that this house should have at least 16 unused DIMMs on the shelf. I’d say 2-4 is reasonable if they are all compatible.

          “Buy two extra of everything” is a good rule and scales for the individual. “Buy double of everything” is not.