On Thursday, 7 March 2019 17:19:42 GMT Peter Humphrey wrote: > Mick <michaelkintz...@gmail.com> wrote : > > I can't recall the OP mentioning corrupt data, which is > > usually the first thing observed with faulty memory. > > I did, actually, last Friday.
Oops! My mistake. > Numbers of files in the portage tree suddenly > changed owner (or group), and when I fixed that git complained that my > numerous local changes would be lost and refused to sync. Of course I > hadn't made any local changes. OK, first port of call in these cases is a memory test. If errors are reported then reseat the RAM modules. If the errors persist you're in the market for replacement modules. If no memory errors are reported it may be RAM is not to blame and other causes should be investigated next. > I've just ordered a new SSD; let's see how that goes. It's twice the size of > the current one, so when it wears itself out I can move all the partitions > to a new part of the disk and get a second life out of it. > > Thanks all for helpful contributions. Did you run memtest86 and if yes, what did it report? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
