In this follow up post on the original Hold on to Your Hardware write-up we’re going to have a look at how to deal with faulty RAM on Linux, which is one of the major causes for system instability, crashes and data corruption on consumer hardware.
You must log in or # to comment.
Disclaimer: This is supposed to act as a temporary measure and not a long-term solution. Faulty RAM will cause headaches down the road and can lead to irreparable data corruption.
Important disclaimer at the end that I felt was worth repeating
For example filesystems like btrfs can be very sensitive to errors in ram due to all the checksumming. On the positive side you’ll know about it fast!
Thanks for 50 years of consumer CPUs not supporting ECC memory, Intel.
I’ve used this exact thing in the past with stellar results, a Yoga (forgot model) with soldered RAM that couldn’t even boot continued to be useful for many more years.
as to reliability, if you already tolerate non-ECC RAM in your workstation, you’re fine; it’s astounding how present bit flips are in everyday use, even from supposedly non-defective hardware, so automated backups of the multi-version kind should be the first thing you set up on your workstation.
