From: Brad Campbell <brad@wasp.net.au>
To: Jim Paris <jim@jtan.com>
Cc: Guy <bugzilla@watkins-home.com>,
comsatcat@earthlink.net, linux-raid@vger.kernel.org
Subject: Re: Busted disks caused healthy ones to fail
Date: Wed, 15 Dec 2004 08:46:22 +0400 [thread overview]
Message-ID: <41BFC19E.2020906@wasp.net.au> (raw)
In-Reply-To: <20041214214946.GA23973@jim.sh>
Jim Paris wrote:
>>It's not that hard.
>>I have 4 drives loaded in the rear bays and 2 x 5 Way SATA Hotswap bays in
>>the 6 front 5.25 inch bays. 14 Drives. And yes, they are on a single 420w
>>PSU along with the motherboard, Athlon XP 2600+. and 5 80mm fans. Not much
>>else though.
>
>
> !!!!!! Holy crap!
>
> Let's pick a random typical hard drive, a Seagate 120GB SATA:
> http://www.mittoni.com.au/catalog/product_info.php/products_id/1690
> It lists maximum current draw as 2.8 A on the +12V line.
> Multiply that by 14 drives and we get __39.2 amps__.
Now, lets actually pick my hard drives shall we?
Max current draw on the 12v line is 1.56A at spinup, dropping to 600mA at seek and 556mA at Idle.
So _worst_ case is 21.84A for about 2 seconds (which does actually exceed the PSU ratings by nearly
3 amps). This machine only gets power cycled about once every three months and I did actually
monitor the 12V rail with a CRO to check specs and ripple and they never budged.
Worst case running load is 8.4A which leaves ~10A on my 12V rail for my motherboard. Ample.
> Now let's pick a random 420W power supply:
> http://www.newegg.com/app/viewproductdesc.asp?submit=Go&description=N82E16817103445
> Note how it's +12V output is rated for only __15 amps__.
Now lets pick my power supply http://www.wasp.net.au/~brad/p1000256.jpg
So yes, on spinup I'm exceeding my 12V rail by 3 Amps for about 1.5 Seconds (Which this supply has
amply proven capable of handling). Outside that I don't see an issue.
> Your numbers might differ a bit. But it is NO surprise that your
> drives are failing. The surprising part is that they and your power
> supply have worked this long.
I never said anything about failing disks! In fact, if you check back you will see me commenting I
have a bucket load of Maxtor Maxline-II drives in there that have been flawless to date. (In fact I
have just ordered 25 more, 15 for me and 10 for a mate. That should increase the sample a little)
They all sit at below 40 Degrees C and the PSU remains quite cool. (I'm an electronic technician by
trade and have several thermocouples I use to verify measurements).
Here is the reason the drives stay nice and cool. http://www.wasp.net.au/~brad/p1000250.jpg
--
Brad
/"\
Save the Forests \ / ASCII RIBBON CAMPAIGN
Burn a Greenie. X AGAINST HTML MAIL
/ \
next prev parent reply other threads:[~2004-12-15 4:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 6:42 Busted disks caused healthy ones to fail comsatcat
2004-12-14 6:55 ` Guy
2004-12-14 8:28 ` comsatcat
2004-12-14 14:11 ` Michael Stumpf
2004-12-14 22:34 ` comsatcat
2004-12-14 15:22 ` Guy
2004-12-14 20:13 ` Brad Campbell
2004-12-14 21:47 ` Guy
2004-12-14 23:54 ` Alvin Oga
2004-12-15 1:03 ` Guy
2004-12-15 1:23 ` Alvin Oga
2004-12-14 21:49 ` Jim Paris
2004-12-14 22:13 ` Guy
2004-12-15 4:46 ` Brad Campbell [this message]
2004-12-15 5:04 ` Guy
2004-12-15 5:22 ` Brad Campbell
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=41BFC19E.2020906@wasp.net.au \
--to=brad@wasp.net.au \
--cc=bugzilla@watkins-home.com \
--cc=comsatcat@earthlink.net \
--cc=jim@jtan.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).