On Thursday, 7 March 2019 17:19:42 GMT Peter Humphrey wrote:
> Mick 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
Mick 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. Numbers of files in the portage tree suddenly
changed owner (or group), and when I fixed that git complained that my numerous
local
Grant Edwards wrote :
> Perhaps it's already been mentioned, but failing RAM can cause all
> sorts failures that might appear to be failing disks, failing network
> cards, failing video cards whatever. I'd run memtest86 for at least
> 12 hours just to make sure...
Good idea. I'll try that.
--
On Thursday, 7 March 2019 14:45:31 GMT Rich Freeman wrote:
> On Thu, Mar 7, 2019 at 9:29 AM Grant Edwards
wrote:
> > On 2019-03-07, Mick wrote:
> > > I can think of 3 things, but more learned M/L contributors may add to
> > > these:
> > >
> > > 1. The SATA connection has come loose. With time
On Thu, Mar 7, 2019 at 9:29 AM Grant Edwards wrote:
>
> On 2019-03-07, Mick wrote:
>
> > I can think of 3 things, but more learned M/L contributors may add to these:
> >
> > 1. The SATA connection has come loose. With time and movement it can come
> > (slightly) adrift. Pushing it back in
5 matches
Mail list logo
