From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Random reboots. Where to start?
Date: Sun, 27 Feb 2011 14:23:22 -0600 [thread overview]
Message-ID: <4D6AB2BA.7070202@gmail.com> (raw)
In-Reply-To: <201102271943.13901.michaelkintzios@gmail.com>
Mick wrote:
> On Sunday 27 February 2011 17:15:40 Grant Edwards wrote:
>
>> On 2011-02-26, Dale<rdalek1967@gmail.com> wrote:
>>
>>> This appears to be a corrupt file somewhere.
>>>
>> In my experice, failing RAM often appears as a corrupt file
>> somewhere.
>>
> Yep, when I had a failing memory module I would often end up with corrupted
> files all over the place. Think about it, when the memory gave up some write
> on disk function was invariably foo-barred.
>
This was my logic tho. Reboots when using the OS on the hard drive.
Runs fine when booted from something else, memtest, system rescue or
even Knoppix. If it was memory, then it should fail on everything at
some point. Since it only failed when booted from the hard drive, I was
looking for issues with it.
What you are saying is completely correct tho. If I load a file into
ram that is bad, then it gets written back to the drive, that file is
broke. That will cause problems eventually and who knows what sort of
flakey issue that will be.
Anyway, recompiling everything gives me this:
root@fireball / # uptime
14:05:46 up 1 day, 5:29, 4 users, load average: 0.43, 0.24, 0.23
root@fireball / #
I think it is going to be OK now. Some file was having a bad hair day.
lol
Dale
:-) :-)
next prev parent reply other threads:[~2011-02-27 20:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 15:33 [gentoo-user] Random reboots. Where to start? Dale
2011-02-25 16:56 ` Helmut Jarausch
2011-02-25 23:06 ` Dale
2011-02-26 15:33 ` Yohan Pereira
2011-02-26 15:46 ` Dale
2011-02-27 17:52 ` Jason Weisberger
2011-02-27 20:12 ` Dale
2011-02-27 23:32 ` Peter Humphrey
2011-02-28 1:38 ` Dale
2011-02-28 7:03 ` Dale
2011-03-01 23:25 ` Jason Weisberger
2011-03-02 0:53 ` Dale
2011-03-02 14:15 ` Paul Hartman
2011-02-25 17:08 ` [gentoo-user] " Grant Edwards
2011-02-25 23:10 ` Dale
2011-02-26 22:20 ` walt
2011-02-26 22:40 ` Mark Knecht
2011-02-26 22:52 ` Dale
2011-02-25 17:14 ` [gentoo-user] " Mark Knecht
2011-02-25 18:03 ` Paul Hartman
2011-02-26 0:18 ` Dale
[not found] ` <4d67fbde.83a0df0a.5870.3917@mx.google.com>
2011-02-26 0:24 ` Dale
2011-02-26 9:27 ` Mick
2011-02-26 14:28 ` Dale
2011-02-27 17:15 ` [gentoo-user] " Grant Edwards
2011-02-27 19:43 ` Mick
2011-02-27 20:23 ` Dale [this message]
2011-02-27 23:34 ` Peter Humphrey
2011-03-01 23:14 ` Mick
2011-03-01 23:51 ` Peter Humphrey
2011-03-02 15:51 ` Mick
2011-03-02 16:29 ` Neil Bothwick
2011-03-02 16:37 ` Mick
2011-03-02 16:51 ` Neil Bothwick
2011-03-02 16:52 ` Alex Schuster
2011-03-02 23:52 ` Peter Humphrey
2011-02-26 16:18 ` [gentoo-user] " Volker Armin Hemmann
2011-02-27 10:02 ` Volker Armin Hemmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6AB2BA.7070202@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox