From: jbradford@dial.pipex.com
To: ed.sweetman@WMICH.EDU (Ed Sweetman)
Cc: linux-kernel@vger.kernel.org
Subject: Re: ide drive dying?
Date: Sun, 8 Sep 2002 21:11:53 +0100 (BST) [thread overview]
Message-ID: <200209082011.g88KBsdj004134@darkstar.example.net> (raw)
In-Reply-To: <3D7BA4BC.5050904@wmich.edu> from "Ed Sweetman" at Sep 08, 2002 03:27:56 PM
> Keep your drive cool and you can expect to keep it around for a very
> long time.
In a large tower case, it is worth while to leave a drive bay free between disks, instead of using them sequentially, like this:
------ ------
|****| |****|
------ ------
| | |****|
------ ------
|****| |****|
------ instead of ------
| | | |
------ ------
|****| | |
------ ------
| | | |
------ ------
Also, if you get a disk that suddenly doesn't spin up, don't assume that the motor has died - you can sometimes bring them back to life by connecting power to them, and giving them a very sharp angular jolt in the plane of the platters - the effect is called static friction, (A.K.A. stiction)
John.
next prev parent reply other threads:[~2002-09-08 19:59 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 0:02 ide drive dying? Dieter Nützel
2002-09-08 17:42 ` jbradford
2002-09-09 1:31 ` Nuitari
2002-09-08 19:27 ` Ed Sweetman
2002-09-08 20:11 ` jbradford [this message]
2002-09-09 2:37 ` Nuitari
2002-09-09 12:26 ` Joachim Breuer
2002-09-09 18:17 ` Thunder from the hill
2002-09-09 18:55 ` Mike Dresser
2002-09-10 12:48 ` Ookhoi
2002-09-10 13:59 ` Mike Dresser
2002-09-10 14:56 ` jbradford
2002-09-10 15:21 ` Mike Dresser
2002-09-10 15:29 ` Larry McVoy
2002-09-10 20:21 ` Andre Hedrick
[not found] <Pine.LNX.4.33.0209062017230.14523-100000@coffee.psychology.mcmaster.ca>
2002-09-07 6:09 ` jbradford
-- strict thread matches above, loose matches on Subject: below --
2002-09-06 20:40 Hell.Surfers
2002-09-06 21:01 ` Alan Cox
2002-09-07 1:02 ` Jason L Tibbitts III
2002-09-06 15:13 DevilKin
2002-09-06 15:26 ` Mike Dresser
2002-09-06 15:39 ` Alan Cox
2002-09-06 15:42 ` Mike Dresser
2002-09-06 16:14 ` Billy Harvey
2002-09-06 16:41 ` Mike Dresser
2002-09-06 18:00 ` jbradford
2002-09-06 17:58 ` Mike Dresser
2002-09-06 15:44 ` Richard B. Johnson
2002-09-06 16:19 ` Craig Ruff
2002-09-06 17:28 ` Daniel Egger
2002-09-06 15:36 ` jbradford
2002-09-06 15:55 ` DevilKin
2002-09-06 17:22 ` jbradford
2002-09-06 19:22 ` DevilKin
2002-09-07 9:30 ` Anders Fugmann
2002-09-07 9:37 ` Udo A. Steinberg
2002-09-07 15:54 ` Holger Lubitz
2002-09-07 16:31 ` jbradford
2002-09-07 12:31 ` Daniel Egger
2002-09-07 13:08 ` jbradford
2002-09-07 13:50 ` Daniel Egger
2002-09-07 15:02 ` jbradford
2002-09-07 20:19 ` Daniel Egger
2002-09-07 20:41 ` jbradford
2002-09-07 21:41 ` Alan Cox
2002-09-07 21:41 ` Alan Cox
2002-09-07 22:00 ` jbradford
2002-09-07 23:19 ` David Forrest
2002-09-08 10:56 ` Henning P. Schmiedehausen
2002-09-08 14:14 ` jbradford
2002-09-09 21:59 ` Alan Cox
2002-09-07 22:05 ` Andre Hedrick
2002-09-07 7:08 ` Andre Hedrick
2002-09-06 15:37 ` mbs
2002-09-06 15:54 ` Alan Cox
2002-09-06 15:38 ` Alan Cox
2002-09-06 17:33 ` Daniel Egger
2002-09-06 20:31 ` Alan Cox
2002-09-06 15:44 ` mbs
2002-09-06 17:46 ` mbs
2002-09-06 20:32 ` Alan Cox
2002-09-07 12:34 ` Daniel Egger
2002-09-07 7:02 ` Andre Hedrick
2002-09-07 7:42 ` jbradford
2002-09-07 7:50 ` Andre Hedrick
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=200209082011.g88KBsdj004134@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=ed.sweetman@WMICH.EDU \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.