From: John Robinson <john.robinson@anonymous.org.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: 'Linux-RAID' <linux-raid@vger.kernel.org>
Subject: Re: Samsung F1 RAID Class SATA/300 1TB drives
Date: Thu, 04 Nov 2010 01:54:41 +0000 [thread overview]
Message-ID: <4CD21261.8090701@anonymous.org.uk> (raw)
In-Reply-To: <4CD19603.4060308@tmr.com>
On 03/11/2010 17:04, Bill Davidsen wrote:
> Leslie Rhorer wrote:
[...]
>> I'm not entirely sure when the drives all went bad, but it was
>> within a week or two of each other.
>
> One possible cause for this is a marginal power supply which "can't keep
> up" when supporting lots of seeks and transfers on multiple drives. In
> every group of drives there will be some variance for low voltage (or
> noise, more likely) and the drive(s) which are sensitive appear to fail.
> I say this from experience, it does happen, and going to a better power
> supply will cure it. This might not be the problem, of course, but it's
> worth investigating before blaming the drives.
Yes, marginal PSUs can be, well, marginal, but it seems even half decent
PSUs can exhibit this behaviour as well, to some extent. So having read
the above I thought I'd look up some data sheets to see why this might
happen.
The spec for Seagate Constellation ES 1GB drives -
http://www.seagate.com/staticfiles/support/disc/manuals/enterprise/Constellation%203_5%20in/100516232f.pdf
- does say that while the average idle power is 5W[1], and the typical
peak operating power is 7W, the maximum transition power (whatever that
is) is 40W - yes, 40W - so I can well see a bundle of relatively
low-power drives placing some heavy stresses on an average or even
average-to-good PSU.
My rule of thumb of late is to expect 7.2k drives to draw ~7W, 10k ~10W
and 15k ~15W, then add a margin for safety and power-up, but having read
the above noted I might double it and make the margin bigger...
Cheers,
John.
[1] Rounded up to the nearest W.
next prev parent reply other threads:[~2010-11-04 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 23:17 Samsung F1 RAID Class SATA/300 1TB drives Mark Knecht
2010-10-28 23:37 ` John Robinson
2010-10-28 23:50 ` Mark Knecht
2010-11-01 21:26 ` David Rees
2010-11-01 21:57 ` Leslie Rhorer
2010-11-03 17:04 ` Bill Davidsen
2010-11-04 1:54 ` John Robinson [this message]
2010-11-04 10:34 ` Tim Small
2010-11-04 11:30 ` John Robinson
2010-11-01 19:50 ` Bill Davidsen
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=4CD21261.8090701@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=davidsen@tmr.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).