Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #286810
| From | Andrew Latham <lathama@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Schrödinger's hash |
| Date | 2026-05-22 18:30 +0200 |
| Message-ID | <MXAV3-74fQ-1@gated-at.bofh.it> (permalink) |
| References | <MXAs1-73P1-5@gated-at.bofh.it> <MXABI-749f-11@gated-at.bofh.it> <MXALn-74cP-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Yes, I should have added that this RAM was only failing when warm/hot which was not fun to discover. On Fri, May 22, 2026 at 10:14 AM Charles Curley <charlescurley@charlescurley.com> wrote: > > On Fri, 22 May 2026 10:05:56 -0600 > Andrew Latham <lathama@gmail.com> wrote: > > > I had an issue some months back. It turned out to be a bad RAM stick > > in my NAS. The issues would not show up on a restart but after some > > usage it would hit the RAM errors and :( > > This is not impossible. I recently had some RAM go bad, failing > memtest. I have replaced it with new RAM, which does not fail > memtest. Maybe I should let it run for several passes. > > Thanks. > > -- > Does anybody read signatures any more? > > https://charlescurley.com > https://charlescurley.com/blog/ > -- - Andrew "lathama" Latham -
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar
Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 18:00 +0200
Re: Schrödinger's hash Andrew Latham <lathama@gmail.com> - 2026-05-22 18:10 +0200
Re: Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 18:20 +0200
Re: Schrödinger's hash Andrew Latham <lathama@gmail.com> - 2026-05-22 18:30 +0200
Re: Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 19:00 +0200
bad RAM (Was: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-22 19:40 +0200
Re: bad RAM (Was: Schrödinger's hash) Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 22:10 +0200
Re: bad RAM (Was: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-22 22:30 +0200
Re: bad RAM (Was: Schrödinger's hash) Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 23:10 +0200
Re: bad RAM (Was: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-22 23:30 +0200
Re: bad RAM (Was: Schrödinger's hash) David Christensen <dpchrist@holgerdanske.com> - 2026-05-23 02:00 +0200
Re: bad RAM (Was: Schrödinger's hash) Andy Smith <andy@strugglers.net> - 2026-05-25 13:20 +0200
Re: bad RAM (Was: Schrödinger's hash) David Christensen <dpchrist@holgerdanske.com> - 2026-05-25 23:20 +0200
Re: bad RAM Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2026-05-25 11:50 +0200
Re: Schrödinger's hash The Wanderer <wanderer@fastmail.fm> - 2026-05-22 18:20 +0200
Re: Schrödinger's hash Charles Curley <charlescurley@charlescurley.com> - 2026-05-22 19:10 +0200
Re: Schrödinger's hash David Christensen <dpchrist@holgerdanske.com> - 2026-05-22 20:10 +0200
Re: Schrödinger's hash Van Snyder <van.snyder@sbcglobal.net> - 2026-05-22 20:40 +0200
Re: Schrödinger's hash nwe <nwe@gitcoding.net> - 2026-05-22 21:50 +0200
Re: Schrödinger's hash David Christensen <dpchrist@holgerdanske.com> - 2026-05-23 01:30 +0200
Re: Schrödinger's hash Van Snyder <van.snyder@sbcglobal.net> - 2026-05-23 01:40 +0200
Re: Schrödinger's hash nwe <nwe@gitcoding.net> - 2026-05-23 02:20 +0200
Re: Schrödinger's hash David Christensen <dpchrist@holgerdanske.com> - 2026-05-23 07:50 +0200
Home server (Was: Re: Schrödinger's hash) nwe <nwe@gitcoding.net> - 2026-05-23 17:00 +0200
Re: Home server (Was: Re: Schrödinger's hash) David Christensen <dpchrist@holgerdanske.com> - 2026-05-24 04:30 +0200
csiph-web