From: "Mathias Burén" <mathias.buren@gmail.com>
To: Gavin Flower <gavinflower@yahoo.com>
Cc: neilb@suse.de, linux-raid@vger.kernel.org
Subject: Re: RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive
Date: Wed, 13 Apr 2011 23:28:05 +0100 [thread overview]
Message-ID: <BANLkTinc-+cb-ZLJBr7m4283xf_MjZ2VmQ@mail.gmail.com> (raw)
In-Reply-To: <724474.42236.qm@web65102.mail.ac2.yahoo.com>
On 13 April 2011 23:24, Gavin Flower <gavinflower@yahoo.com> wrote:
>
> --- On Fri, 8/4/11, Gavin Flower <gavinflower@yahoo.com> wrote:
>
>> From: Gavin Flower <gavinflower@yahoo.com>
>> Subject: RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive
> [...]
>> This morning, I noticed my system was extremely
>> unresponsive, and that there were clicking sounds coming
>> from one of my 5 hard drives.
> [...]
>
> Hi Neil,
>
> When I do
> badblocks -s -v /dev/sdc
> I hear clicking sounds from the hard drive, and notice lots and lots of log messages such as:
> ata3: exception Emask 0x10 SAct 0x0 SErr 0x90200 action 0xe frozen
> ata3: irq_stat 0x00400000, PHY RDY changed
> ata3: SError: { Persist PHYRdyChg 10B8B }
> ata3: hard resetting link
> ata3: softreset failed (device not ready)
> ata3: applying SB600 PMP SRST workaround and retrying
> ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata3.00: configured for UDMA/33
> ata3: EH complete
>
> So I assume that the clicking corresponds to the hard reset, but I'm not certain of that. Initially, I thought it might be some kind of disk head problems. Note that smart reports no bad blocks.
>
>
> Regards,
> Gavin
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Perhaps you could post the full smartctl -a output?
Regards,
Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-04-13 22:28 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 [this message]
2011-04-14 0:15 ` Gavin Flower
2011-04-14 4:08 ` Roman Mamedov
2011-04-14 13:16 ` Phil Turmel
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=BANLkTinc-+cb-ZLJBr7m4283xf_MjZ2VmQ@mail.gmail.com \
--to=mathias.buren@gmail.com \
--cc=gavinflower@yahoo.com \
--cc=linux-raid@vger.kernel.org \
--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 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).