Re: Spontaneous unclean reboots

On Mon, 22 Sep 2008 15:36:00 +0000, Curt wrote:

On 2008-09-21, David W. Hodgins <dwhodgins@xxxxxxxxxxxxxxxxx> wrote:

I'm going to do that from the Knoppix cd I have, although I'm not sure
how to do it? Do I chroot into the partition, then run fsck?

No! The filesystem must not be mounted, when you run the fsck.


Right, sorry for the stupid question.

I've run smartctl several times from knoppix cd as well as memtest86
(it's a knoppix boot option).

No errors have been found.

fsck found lots of errors however on my root filesystem and I answered
yes to every question.

I even did a badblocks -n on my root file system, though I probably
shouldn't have, because the man page was cryptic to me.

This morning, the psu blew and there was a smell of burning rubber and
hellfire and I turned off the machine.

To make a long story short, I bought a new psu and installed it and am
keeping my fingers crossed.

I would like to check for corrupted files. I was running debsums when
the sparks began to fly this morning. I'm not sure about the procedure;
some packages don't have debsums, some appeared to have incorrect ones.
I'll try to google that out. Thank all of you for your help.

As your machine seems to be working and in a later post you noted
possible bad capacitors on your motherboard, you should back up all your
important data NOW. Then, do a complete install of your OS, formatting
all partitions, including the destructive 4 pass, read/write badblocks
test--the -w option--to make absolutely sure your hard drive is okay. Be
patient. This badblocks test is very thorough and takes a long time. I
did it on any older 80 Gig drive, and it took about 30 hours. If you use
the -v option, too, you will get output to see if the test is running and
hasn't stalled.

And I think it's time to consider replacing the current motherboard, also
called the "main" board. (Years ago, computers had both mother/main
boards and daughter boards. Not today.) Also, I'd suggest that you
budget for a new hard drive to be on the safe side. Your current one is
rather old, and with all that's been happening to it, it might be better
to retire it or if still good, delegate it for non-critical use.

Stef
.

Relevant Pages

  • Re: Weired after crash
    ... See below to run fsck on the filesystem. ... > is the root partition but not the boot partition. ... If it's a raid device you'll have to start it first ...
    (comp.os.linux.misc)
  • Re: Weired after crash
    ... See below to run fsck on the filesystem. ... > is the root partition but not the boot partition. ... If it's a raid device you'll have to start it first ...
    (comp.os.linux.misc)
  • Re: how to use a 1TB disk?
    ... Can just make 1 huge 1TB partition or maybe it's better to split the disk in two partions? ... That varies somewhat with the filesystem. ... For some filesystems, such as XFS, the fsck uses more memory for larger partitions - it is possible to build a filesystem that your machine can't fsck at all due to memory constraints. ...
    (comp.os.linux.hardware)
  • Re: fsck and dump freeze freebsd. any ideas?
    ... I took the partition out of the startup check for now. ... I performed a fsck and a dump confirming ... I did not yet have the array rebuild the ... My experience has been that dump *with snapshot* of a live filesystem ...
    (freebsd-questions)
  • Re: fsckd - FIXED
    ... filesystem errors on boot, with the "hit control-D to continue or give root ... to fix the errors with fsck. ... filesystem and inability to reboot. ...
    (Debian-User)