From: Stan Hoeppner <stan@hardwarefreak.com>
To: Barrett Lewis <barrett.lewis.mitsi@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Mdadm server eating drives
Date: Wed, 03 Jul 2013 21:21:16 -0500 [thread overview]
Message-ID: <51D4DC1C.7090709@hardwarefreak.com> (raw)
In-Reply-To: <CAPSPcXjoyn3VjxduJQ3J9fYWVpvOHtph8A+LAvGWHnw+Fxj_tg@mail.gmail.com>
On 7/3/2013 2:47 PM, Barrett Lewis wrote:
> I added the two non-fresh drives back to the array and they have been
> resyncing. The first one is almost complete. No errors so far.
> Everything is been very smooth since replacing the power supply.
> And I am paying extra close attention to make sure my TLER capable
> drives have it turned on, and the others have the driver timeout set
> to 180. From now on I will only be buying TLER capable drives.
> Just an update.
Good to hear. I hope things keep looking up.
> Also, this is likely the same drive making the same noise with the top
> off https://www.youtube.com/watch?v=a9i5yixsJbk
> I wonder if its PWM driving the actuator against the barrier.
Spinning HDDs use voice coil actuators to move the head. The voice coil
is driven by direct DC current, not pulse width modulation. PWM
generates constant voltage and current but cycles the circuit hundreds
or thousands of times per second. The lower the frequency the less
power to the device. The higher the frequency the greater the power.
Thus PWM is suitable for varying the speed of brushless DC fans and the
brightness of incandescent light bulbs. It simply won't work for
driving voice coil actuators.
Regarding HDD noises, identifying/diagnosing them is a voodoo science,
unless you happen to be an engineer at Seagate, WD, or Toshiba, which
are, sadly, AFAIK, the only 3 remaining HDD vendors left on the planet.
Seagate and WD have swallowed all the others.
--
Stan
next prev parent reply other threads:[~2013-07-04 2:21 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
2013-07-03 19:47 ` Barrett Lewis
2013-07-03 20:38 ` Jon Nelson
2013-07-04 2:21 ` Stan Hoeppner [this message]
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=51D4DC1C.7090709@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=barrett.lewis.mitsi@gmail.com \
--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).