From: Gene Heskett <gene.heskett@verizon.net>
To: JG <jg@cms.ac>
Cc: linux-kernel@vger.kernel.org
Subject: Re: could someone plz explain those ext3/hard disk errors
Date: Mon, 9 Feb 2004 06:52:12 -0500 [thread overview]
Message-ID: <200402090652.12434.gene.heskett@verizon.net> (raw)
In-Reply-To: <20040209095227.AF4261A9ACF@23.cms.ac>
On Monday 09 February 2004 04:52, JG wrote:
>hi,
>
>> I have had the same exact errors.. and i have RMA'ed two disks...
>> already. i just thought it was bad luck..
>>
>> i power down properly and i dont think its power surges, since i
>> am in school and it only happens to me. i would expect my
>> neighbors to have problems too.
>
>really strange, me too.
>now...hm, it all started when i upgraded from kernel 2.4.19 to 2.6.0
> in late decemeber, the system worked very fine for a week or so
> (having great response times!) but then all of a sudden the
> problems started. 2 disks died. then my gigabit network card was
> only able to transmit 200kb/s (but this was really a hardware
> problem, a new card is working fine again, well...). a week later
> the next disks are having problems and i have yet to RMA three
> disks. and now the next two disks..., i'm getting insane ;) i can't
> see any EXT3 error anymore *g* the next disks will be reiserfs only
> to see other error messages ;) well, but that doesn't solve the
> problem of 6 disks within 2 months...this is so unlikely.
>
>JG
This thread seems to be related to a slashdot story about a
mis-formulated epoxy-b that went into production circa 18-20 months
ago. It contains a time bomb chemical reaction involving trace
anounts of red phosphorus, and is said to be the reason all HD makers
went to a 1 year warranty. You may have to google for the story now
as I don't have a record of the link, sorry.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2004-02-09 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 17:53 JG
2004-02-08 18:55 ` Micha Feigin
2004-02-08 19:05 ` JG
2004-02-09 1:47 ` Heriberto A Tejeda
2004-02-09 9:52 ` JG
2004-02-09 10:26 ` John Bradford
2004-02-09 11:06 ` JG
2004-02-18 13:31 ` Bill Davidsen
2004-02-18 14:42 ` John Bradford
2004-02-18 15:54 ` JG
2004-02-18 18:26 ` Bill Davidsen
2004-02-09 11:52 ` Gene Heskett [this message]
2004-02-18 13:41 ` Bill Davidsen
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=200402090652.12434.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=jg@cms.ac \
--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
all inboxes | Powered by JetHome®