All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastien Koechlin <seb.kernel@koocotte.org>
To: harry <hfranklin97@excite.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: disk testing
Date: Fri, 17 Sep 2004 17:08:08 +0200	[thread overview]
Message-ID: <20040917150808.GK17204@koocotte.org> (raw)
In-Reply-To: <20040917025005.DC7F1395B@xprdmailfe9.nwk.excite.com>

On Thu, Sep 16, 2004 at 10:50:05PM -0400, harry wrote:
> 
> Tim and Neil have suggested (apparently correctly) that the disk had a bad
> sector and the firmware remapped it when I wrote to it. My question is,
> how many spare sectors does the typical disk have? More importantly, since
> the sector has been remapped, recreating the raid5 array worked fine, but
> is a failure right out of the box normal? I was going to return it but
> since its working now I'm not sure if I should or not.

Can you read SMART Attributes under any OS?

Every disk I use, have a SMART Reallocated_Sector_Ct Attribute:

------

# smartctl -A /dev/hde
smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID ATTRIBUTE_NAME        FLAG   VALUE WORST THRESH TYPE     UPDATED RAW_VALUE
 1 Raw_Read_Error_Rate   0x000f 065   063   006    Pre-fail Always  147852401
 3 Spin_Up_Time          0x0003 100   100   000    Pre-fail Always  0
 4 Start_Stop_Count      0x0032 100   100   020    Old_age  Always  0
 5 Reallocated_Sector_Ct 0x0033 100   100   036    Pre-fail Always  0
(...)

------

You should search for your hard-drive datasheet, but RAW_VALUE is probably a
counter of remapped sectors.

If RAW_VALUE is high, if VALUE is low and going near THRESH, it means you're
going to have troubles with this disk.

You can read http://www.linuxjournal.com/article.php?sid=6983

-- 
Seb, autocuiseur

  parent reply	other threads:[~2004-09-17 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17  2:50 disk testing harry
2004-09-17  9:18 ` Tim Small
2004-09-17 15:08 ` Sebastien Koechlin [this message]
     [not found] <20040914095208.E790A3969@xprdmailfe9.nwk.excite.com>
2004-09-14 12:17 ` Tim Small
  -- strict thread matches above, loose matches on Subject: below --
2004-09-14  9:54 harry
2004-09-14  9:04 harry
2004-09-14  8:50 harry
2004-09-14  9:06 ` Neil Brown
2004-09-14  9:15 ` Tim Small

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=20040917150808.GK17204@koocotte.org \
    --to=seb.kernel@koocotte.org \
    --cc=hfranklin97@excite.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 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.