mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve Bromwich <kernel@fop.ns.ca>
To: Nico Schottelius <nico-kernel@schottelius.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: harddisk or kernel problem?
Date: Wed, 18 Feb 2004 09:30:11 -0400 (AST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0402180921120.7046@brain.fop.ns.ca> (raw)
In-Reply-To: <20040215233441.GJ1881@schottelius.org>

On Mon, 16 Feb 2004, Nico Schottelius wrote:

> Bartlomiej Zolnierkiewicz [Fri, Feb 13, 2004 at 05:17:34PM +0100]:
> I'm really down as this is the second disk
> dyeing within two month (and the second 2.5" hd even, I begin to think
> notebooks don't like me :/).
>
> I currently collect all data I get / find out to
>
> http://schotteli.us/~nico/hd-problem.02/

194 Temperature_Celsius     0x0022   100   050   000    Old_age   Always
-       48 (Lifetime Min/Max 14/65)

If I'm reading this correctly, you've been running the drive when it's
extremely cold and extremely hot (Min/Max 14/65, I'm guessing that's
either Fahrenheit or a raw unconverted reading from the thermistor). I
managed to completely hork a notebook drive after leaving my laptop in the
boot of my car for several hours (~-25C), taking it into a warm apartment
(~19C), booting it up and lifting the notebook off my lap sideways whilst
I shifted to get comfortable and putting it back on my lap. The hard drive
had a head crash (I think) on the sectors it was reading while I moved and
the partition was effectively toast - this was my Debian partition, and
wouldn't boot any more, but I could boot off the RedHat partition and
/home was (thankfully) still readable. I pulled all the data off in
preparation for the drive failing before I could get a new one (I was down
in Boston at the time), but the bad sectors slowly spread through the
entire drive over the course of a couple of days and I couldn't read any
data at all.

Lessons learned:

* Let laptops settle to room temperature after being exposed to sub-zero
temperatures for a while (this is probably in the manual, but I don't have
one)

* Laptop notebooks may be somewhat ruggedised but they still don't like
being moved when they're reading off the drive.

Running drives really hot is also a good way to toast them, too!

Cheers, Steve

  parent reply	other threads:[~2004-02-18 13:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13  7:54 Nico Schottelius
2004-02-13  8:11 ` Nico Schottelius
2004-02-13  9:52   ` Nico Schottelius
2004-02-13 16:17     ` Bartlomiej Zolnierkiewicz
2004-02-15 23:34       ` Nico Schottelius
2004-02-16  0:09         ` Bartlomiej Zolnierkiewicz
2004-02-18 16:55           ` Bruce Allen
2004-02-19  8:01             ` Nico Schottelius
2004-02-20 16:25               ` Bruce Allen
2004-03-02 20:07               ` Bruce Allen
2004-03-02 23:12                 ` Nico Schottelius
2004-02-18 13:30         ` Steve Bromwich [this message]
2004-02-18 14:12           ` Nico Schottelius
2004-02-18 16:41           ` Bruce Allen
2004-02-19  0:06             ` Steve Bromwich
2004-02-19  8:16               ` Nico Schottelius
2004-02-20 17:10                 ` Frédéric L. W. Meunier
2004-02-20 22:37                   ` Eric D. Mudama
2004-02-13 16:56 ` Alex Goller

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=Pine.LNX.4.58.0402180921120.7046@brain.fop.ns.ca \
    --to=kernel@fop.ns.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-kernel@schottelius.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®