linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russ Price <rjp_raid@fubegra.net>
To: 'LinuxRaid' <linux-raid@vger.kernel.org>
Subject: Re: Hard drive Reliability?
Date: Thu, 20 May 2004 17:27:56 -0500	[thread overview]
Message-ID: <40AD30EC.9070809@fubegra.net> (raw)
In-Reply-To: <200405200034.i4K0YpB17310@www.watkins-home.com>

Guy wrote:
> I have an old system with 2 18 Gig SCSI disks.  One IBM and one Seagate.
> Both run very hot!  I added extra cooling fans.  Both fans failed about 2
> years ago.  Only the CPU and power supply fans still work.   The disk drives
> are too hot to touch.  Much too hot to touch!  The system is running 99.99%
> of the time.  No disk problems.  The system is 4-5 years old as a guess.  To
> help date it, it is a P3-350Mhz.  My wife uses this computer.  :)

The lack of start-stop cycles may work in your favor; you don't have as 
many thermal expansion/contraction cycles or startup electrical surges 
to worry about.  Of course, if stiction strikes after a power-off, you 
could be in trouble...

In any case, it's not a bad idea to set up smartd and look after your 
system logs.  If your drives have temperature sensors, it's a good idea 
to tell smartd to report raw values for temperature (usually -r 194 -R 
194 in the smartd.conf file); the normalized values look wacky.

I also have hddtemp and the hddtemp plugin for gkrellm, so I can easily 
check the temperatures on my desktop, at least for my four-drive SATA 
RAID5 array.  My older 30GB Maxtors don't have temperature sensors, but 
they're in the same fan-cooled bays as the Samsung SATA drives, and they 
all run reasonably cool to the touch.  Current room temperature is about 
28 C, and the temperature display reports 29-33 C for the drives in the 
array.

	Russ

  parent reply	other threads:[~2004-05-20 22:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 19:58 Hard drive Reliability? John Lange
2004-05-19 20:49 ` Måns Rullgård
2004-05-19 21:28   ` Sevatio
2004-05-19 22:02     ` John Lange
2004-05-19 22:42       ` jim
2004-05-19 22:26     ` Guy
2004-05-19 23:53       ` maarten van den Berg
2004-05-20  0:49         ` TJ Harrell
2004-05-20  1:13           ` berk walker
2004-05-20  6:39           ` Måns Rullgård
2004-05-19 23:44     ` maarten van den Berg
2004-05-19 22:04 ` berk walker
2004-05-19 22:18 ` Guy
2004-05-19 23:40   ` maarten van den Berg
2004-05-20  0:34     ` Guy
2004-05-20  1:46       ` John Lange
2004-05-20 22:27       ` Russ Price [this message]
2004-05-20 15:51     ` Sevatio
2004-05-20  4:39 ` Mark Hahn
2004-05-20  7:15   ` John Lange
2004-05-20 12:15     ` Mark Hahn
2004-05-20 13:26       ` jim
2004-05-20 13:31       ` John Lange
2004-05-20 14:20         ` Mark Hahn
2004-05-20 13:32       ` Tim Grant
2004-05-20 14:38         ` Robin Bowes
2004-05-22  5:15           ` Brad Campbell
2004-05-24 13:25             ` Frank van Maarseveen
2004-05-24 18:35               ` Brad Campbell
2004-05-24 22:38                 ` maarten van den Berg
  -- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:54 Cress, Andrew R

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=40AD30EC.9070809@fubegra.net \
    --to=rjp_raid@fubegra.net \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).