From: Julien Banchet <julien@banchet.net>
To: jerome lacoste <jerome.lacoste@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Huge unreliability - does Linux have something to do with it?
Date: Fri, 04 Feb 2005 10:20:54 +0100 [thread overview]
Message-ID: <1107508854.2425.23.camel@dhcp0.fdpsolutions.com> (raw)
In-Reply-To: <5a2cf1f605020401037aa610b9@mail.gmail.com>
Le vendredi 04 f?rier 2005 à 10:03 +0100, jerome lacoste a écrit :
> [Sorry for the sensational title]
>
> I have had this laptop for three years. It ran Linux (Debian unstable)
> from the start and its hardware has been very unreliable: I changed
> hard disks twice and the motherboard thrice. My DVD drive started
> failing some days ago (this one is 'original', 3 years old). But I
> don't mind as I am not under warranty anymore... This morning the
> machine booted with fsck errors on my hard disk. I am not sure if I
> did the right thing, but I said clear the inodes, and I ended up
> loosing some programs(*) (du, dircolors, etc..). The day starts well
> isn't it? Sounds like I will have to switch disks again...
>
> I halted the machine correctly yesterday night. I never dropped the
> box in 3 years. Am I just being unlucky? Or could the fact that I am
> using Linux on the box affect the reliability in some ways on that
> particular hardware (Dell Inspiron 8100)? I run Linux on 3 other
> computers and never had single problems with them.
>
> How can the file system (ext3) be messed up the way it was this
> morning after I stopped the machine correctly yesterday?
> Could a hardware failure look like bad sectors to fsck?
>
> Attached the output of smartctl -a /dev/hda, whatever that helps.
>
> Jerome
>
> (*) I accept tips on discovering and maybe recovering which files have
> been taken out of my system...
I honestly beleive that your simply out of luck, not that 3 years is
alot for a laptop, but simply the "shit happens" thing.
Even though the Distro you run is tagged "Unstable" I'd rather run a
battery of stress tools on your computer it before posting here, 'cus
it's maybe a bit beyond the scope of lkml (I bet you tried more than one
versions of the kernel in 3 years, problems never remain too long, I
also hope you tried fresh installs too).
I don't think that en Inspiron 8100 carries anything exotic, so ...
well... Go for a memtest86 then try disk stress tools (my memory wen't
blank right now, ask google ;-) )
JB,
PS: Heu Jérome.... BTS Info Indus à l'Isle sur la Sorgue ?
--
Julien Banchet <julien@banchet.net>
next prev parent reply other threads:[~2005-02-04 9:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 9:03 jerome lacoste
2005-02-04 9:20 ` Julien Banchet [this message]
2005-02-04 10:31 ` Jim Nelson
2005-02-04 10:45 ` Bernd Eckenfels
2005-02-04 11:28 ` jerome lacoste
2005-02-04 17:13 ` Horst von Brand
2005-02-04 11:27 ` Andre Tomt
2005-02-04 11:51 ` DervishD
2005-02-04 12:18 ` Wakko Warner
2005-02-04 14:44 ` Dmitry Torokhov
2005-02-06 15:58 ` Dell Inspiron sensors (was: Re: Huge unreliability - does Linux have something to do with it?) Giuseppe Bilotta
2005-02-06 16:58 ` kernel
2005-02-06 21:58 ` Giuseppe Bilotta
2005-02-05 10:38 ` Huge unreliability - does Linux have something to do with it? jerome lacoste
2005-02-05 12:27 ` Willy Tarreau
2005-02-05 15:11 ` Wakko Warner
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=1107508854.2425.23.camel@dhcp0.fdpsolutions.com \
--to=julien@banchet.net \
--cc=jerome.lacoste@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome