From: Phil Turmel <philip@turmel.org>
To: Gavin Flower <gavinflower@yahoo.com>
Cc: "Mathias Burén" <mathias.buren@gmail.com>,
neilb@suse.de, linux-raid@vger.kernel.org
Subject: Re: RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive
Date: Thu, 14 Apr 2011 09:16:36 -0400 [thread overview]
Message-ID: <4DA6F3B4.7040303@turmel.org> (raw)
In-Reply-To: <541553.42147.qm@web65113.mail.ac2.yahoo.com>
Hi Gavin,
I think you might want to investigate your *power supply* ...
On 04/13/2011 08:15 PM, Gavin Flower wrote:
[snip /]
> SMART Attributes Data Structure revision number: 10
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000f 115 099 006 Pre-fail Always - 87918991
> 3 Spin_Up_Time 0x0003 099 097 000 Pre-fail Always - 0
> 4 Start_Stop_Count 0x0032 085 085 020 Old_age Always - 16014
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
> 7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 20251386
> 9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 2940
> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
> 12 Power_Cycle_Count 0x0032 093 093 020 Old_age Always - 7999
SMOKING GUN ^^^^
I suspect your power supply is good enough to slowly spin up your drives and get them talking, but when you ask them to work hard, especially when writing, the PS voltage dips enough to reset the drive.
Look up all the power consumption specs for all of your components, and add up the *peak* current requirements. Make sure your PS can handle it.
HTH,
Phil
next prev parent reply other threads:[~2011-04-14 13:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 22:24 RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive Gavin Flower
2011-04-13 22:28 ` Mathias Burén
2011-04-14 0:15 ` Gavin Flower
2011-04-14 4:08 ` Roman Mamedov
2011-04-14 13:16 ` Phil Turmel [this message]
2011-04-14 21:12 ` Gavin Flower
2011-04-14 22:23 ` Phil Turmel
2011-04-28 20:03 ` Gavin Flower
2011-04-28 20:11 ` Roman Mamedov
2011-04-28 22:11 ` Phil Turmel
2011-04-28 22:40 ` Phil Turmel
2011-04-13 23:09 ` NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2011-04-14 21:14 Gavin Flower
2011-04-14 21:19 ` Mathias Burén
2011-04-14 23:15 ` John Robinson
2011-04-08 2:01 Gavin Flower
2011-04-08 1:34 Gavin Flower
2011-04-08 1:32 Gavin Flower
2011-04-08 9:34 ` NeilBrown
2011-04-08 9:59 ` Gavin Flower
2011-04-08 11:50 ` NeilBrown
2011-04-11 6:50 ` Gavin Flower
2011-04-12 21:30 ` Gavin Flower
2011-04-13 10:57 ` John Robinson
2011-04-13 11:13 ` NeilBrown
2011-04-13 11:58 ` John Robinson
2011-04-13 20:30 ` Gavin Flower
2011-04-07 21:58 Gavin Flower
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=4DA6F3B4.7040303@turmel.org \
--to=philip@turmel.org \
--cc=gavinflower@yahoo.com \
--cc=linux-raid@vger.kernel.org \
--cc=mathias.buren@gmail.com \
--cc=neilb@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.