From: Alexander <freebsd@nagilum.org>
To: FLD <fld@r00t3d.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Bad sectors on a degraded array
Date: Mon, 10 Jan 2011 08:42:43 +0100 [thread overview]
Message-ID: <20110110084243.370821zsnjv03bfo@cakebox.homeunix.net> (raw)
In-Reply-To: <20110108124953.GA8241@r00t3d.com>
See if these are "real" read errors, errors that the OS will see (dd
if=/dev/sdX of=/dev/null bs=1M).
If yes, get another disk and duplicate the problematic disk using
dd_rescue and use the new one instead of the old one.
Once the array is up again make sure to do a raid check in regular intervals.
Kind regards,
Alex.
----- Message from fld@r00t3d.com ---------
Date: Sat, 8 Jan 2011 14:49:53 +0200
From: FLD <fld@r00t3d.com>
Subject: Bad sectors on a degraded array
To: linux-raid@vger.kernel.org
> While waiting for my RMA'd disk to return I noticed that one device in
> my degraded (4 out of 5) raid5 has developed some bad sectors:
> 1 Raw_Read_Error_Rate 0x002f 200 200 051 - 0
> 196 Reallocated_Event_Count 0x0032 200 200 000 - 0
> 197 Current_Pending_Sector 0x0032 200 200 000 - 3
> 198 Offline_Uncorrectable 0x0030 200 200 000 - 3
>
> I did some Self-test'ing and got some errors:
> # 1 Extended offline Completed: read failure 50% 6640
> 1158803416
> # 2 Short offline Completed without error 00% 6637
> # 3 Extended offline Completed: read failure 50% 6634
> 1158820656
>
> At this point those bad secotrs haven't caused any harm or errors in
> dmesg while the array is mounted r/w and being used. What I'm wondering
> is what kind of steps should I take once the RMA replacement arrives?
> I know md doesn't like read errors very much and I'm thinking with smart
> output like that it's very likely theres gonna be some read errors during
> rebuild?
>
> According to smartmontool documentation this is a pretty common situation
> for a hard disk. There's a nice tutorial how to fix errors like this at:
> http://smartmontools.sourceforge.net/badblockhowto.html , so I wonder if
> I should --stop the array and try to manually fix the bad sectors before
> I try rebuilding?
> --
> 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
>
----- End message from fld@r00t3d.com -----
========================================================================
# _ __ _ __ http://www.nagilum.org/ \n icq://69646724 #
# / |/ /__ ____ _(_) /_ ____ _ nagilum@nagilum.org \n +491776461165 #
# / / _ `/ _ `/ / / // / ' \ Amiga (68k/PPC): AOS/NetBSD/Linux #
# /_/|_/\_,_/\_, /_/_/\_,_/_/_/_/ Mac (PPC): MacOS-X / Linux / MacOS-X #
# /___/ x86: FreeBSD/Linux/Solaris/Win2k ARM9: EPOC EV6 #
========================================================================
----------------------------------------------------------------
cakebox.homeunix.net - all the machine one needs..
prev parent reply other threads:[~2011-01-10 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 12:49 Bad sectors on a degraded array FLD
2011-01-10 7:42 ` Alexander [this message]
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=20110110084243.370821zsnjv03bfo@cakebox.homeunix.net \
--to=freebsd@nagilum.org \
--cc=fld@r00t3d.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).