Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: Gavin Flower <gavinflower@yahoo.com>
Cc: "Mathias Burén" <mathias.buren@gmail.com>,
	neilb@suse.de, linux-raid@vger.kernel.org
Subject: Fw: RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive
Date: Thu, 14 Apr 2011 11:15:24 +0600	[thread overview]
Message-ID: <20110414111524.092a47df@natsu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2537 bytes --]

@Gavin
Please learn to use your mail client properly, don't drop all CC: when
replying!!


Begin forwarded message:

Date: Wed, 13 Apr 2011 21:39:04 -0700 (PDT)
From: Gavin Flower <gavinflower@yahoo.com>
To: Roman Mamedov <rm@romanrm.ru>
Subject: Re: RAID6 data-check took almost 2 hours, clicking sounds, system
unresponsive



--- On Thu, 14/4/11, Roman Mamedov <rm@romanrm.ru> wrote:

> From: Roman Mamedov <rm@romanrm.ru>
> Subject: Re: RAID6 data-check took almost 2 hours, clicking sounds, system
> unresponsive To: "Gavin Flower" <gavinflower@yahoo.com>
> Cc: "Mathias Burén" <mathias.buren@gmail.com>, neilb@suse.de,
> linux-raid@vger.kernel.org Date: Thursday, 14 April, 2011, 16:08
> On Wed, 13 Apr 2011 17:15:42 -0700
> (PDT)
> Gavin Flower <gavinflower@yahoo.com>
> wrote:
> 
> > Note that smart reports no bad blocks.
> 
> It reports 24 bad blocks:
> 
> 183 Runtime_Bad_Block   
>    0x0032   076   076   000 
>   Old_age   Always
> -       24

Hmm... I am so used to just looking at item #5 (which I had thought, was the
bad block count!):

5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always
-       0

> 
> Try running a long SMART self test on the drive (smartctl
> -t long /dev/sdX).

Running now.

> 
> Also for a bit of common sense - why not just try the disk
> on another PC. If it
> produces clicking sounds and "frozen" errors when running
> "badblocks" even
> there, then what else do you expect it to do, jump out of
> the PC and say "i'm
> broken please replace me"? :)

I thought that modern hardware was so smart that the first I should know of
it, is when the cost of the placement disk appeared on my credit card!!!

More seriously... with my eyesight (at about 400 mm from the screen, text
appears a little fuzzy, and that is on a good day), I don't trust myself
changing hardware like that.  I have friends that can do the hardware part,
but I try to do as much investigation myself before I ask them for help.

> 
> -- 
> With respect,
> Roman
> 

Hi Mathias,

Comments above.

I was not expecting help from this list on this matter, but it is appreciated.

The disk used for /dev/sdc was only replaced very recently, and I have a
strong suspicion it is a cable and/or connector problem.  I do have one spare
hard disk I can use, but I had it earmarked to replace the one which is very
near its limit on reallocated sectors.


Thanks,
Gavin



-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2011-04-14  5:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14  5:15 Roman Mamedov [this message]
2011-04-14  6:58 ` Fw: RAID6 data-check took almost 2 hours, clicking sounds, system unresponsive 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=20110414111524.092a47df@natsu \
    --to=rm@romanrm.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox