From: Stan Hoeppner <stan@hardwarefreak.com>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: Barrett Lewis <barrett.lewis.mitsi@gmail.com>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Mdadm server eating drives
Date: Wed, 03 Jul 2013 12:32:00 -0500 [thread overview]
Message-ID: <51D46010.6040109@hardwarefreak.com> (raw)
In-Reply-To: <CAKuK5J0nYf3j_zTLCjBOKw49ADTKqJwU+fa7pVo4incW8J9RBQ@mail.gmail.com>
On 7/3/2013 9:03 AM, Jon Nelson wrote:
> A quick google search shows the ST2000DM001 (which I have 2 of) *do*
> make "chirping" or "beeping" noises. Additionally
Yes, Seagate still makes some relatively noisy drives compared to others
on the market. I had ST225s and ST251s in the late 80s that could be
heard across a large room. All drives were noisy back then due to the
use of stepper motors. Drives have used voice coil actuators since the
early 90s, shortly after the IDE spec was adopted, which are an order of
magnitude quieter. These are very old and thus a bit noiser, but not
all that much:
http://www.youtube.com/watch?v=NYEkC7FBXa4
http://www.youtube.com/watch?v=RZMrwdQBVf4
But surely nobody would confuse this random mechanical drive noise for
an audible alarm. And of course, with dirty power as in the OP's case,
drives will make more noise due to the firmware doing constant
recalibration of the heads as the spindle constantly drops below minimum
RPM threshold and comes back up again when voltage increases.
I think some people have simply become accustomed to ultra quiet drives
that rarely make a peep, and when they do people get all nervous.
--
Stan
next prev parent reply other threads:[~2013-07-03 17:32 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 13:47 Mdadm server eating drives Barrett Lewis
2013-06-12 13:57 ` David Brown
2013-06-12 14:44 ` Phil Turmel
2013-06-12 15:41 ` Adam Goryachev
[not found] ` <CAPSPcXihHrAi2TB9Fuxb1qOGMc_WzwGoXAA7nHdwe2knkO0LkQ@mail.gmail.com>
[not found] ` <CAPSPcXib4YZ9Ah-jLvL_kPwpKHLxaGT0rNaDL4XQcFm=RtjcAQ@mail.gmail.com>
2013-06-14 0:19 ` Barrett Lewis
2013-06-14 2:08 ` Phil Turmel
[not found] ` <CAPSPcXgMxOF-C2Szu_nf4ZLDC8p+yJFOtvLPu7xy1DTW9VAHjg@mail.gmail.com>
2013-06-14 21:18 ` Barrett Lewis
2013-06-14 21:20 ` Barrett Lewis
2013-06-14 21:25 ` Phil Turmel
2013-06-14 21:30 ` Phil Turmel
2013-06-17 21:37 ` Barrett Lewis
2013-06-18 4:13 ` Mikael Abrahamsson
2013-06-27 0:23 ` Barrett Lewis
2013-06-27 17:13 ` Nicolas Jungers
2013-07-02 0:17 ` Barrett Lewis
2013-07-02 1:57 ` Stan Hoeppner
2013-07-02 15:48 ` Barrett Lewis
2013-07-02 19:44 ` Stan Hoeppner
2013-07-02 19:54 ` Stan Hoeppner
2013-07-02 20:07 ` Jon Nelson
2013-07-02 20:23 ` Stan Hoeppner
2013-07-02 20:58 ` Barrett Lewis
2013-07-03 1:50 ` Stan Hoeppner
2013-07-03 5:26 ` Barrett Lewis
2013-07-03 14:03 ` Jon Nelson
2013-07-03 14:36 ` Phil Turmel
2013-07-03 17:32 ` Stan Hoeppner [this message]
2013-07-03 19:47 ` Barrett Lewis
2013-07-03 20:38 ` Jon Nelson
2013-07-04 2:21 ` Stan Hoeppner
2013-07-03 17:05 ` Stan Hoeppner
2013-07-02 21:49 ` Phil Turmel
2013-06-14 21:24 ` Phil Turmel
2013-07-29 22:25 ` Roy Sigurd Karlsbakk
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=51D46010.6040109@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=barrett.lewis.mitsi@gmail.com \
--cc=jnelson-linux-raid@jamponi.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).