From: Colin McCabe <Colin.P.McCabe@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: unreadable drives can be synchronized?
Date: Fri, 18 May 2007 14:10:50 -0400 [thread overview]
Message-ID: <464DEC2A.6040209@gmail.com> (raw)
In-Reply-To: <200705181447.l4IElO2a000640@cichlid.com>
Andrew Burgess wrote:
>> Basically, B appears to be "write-only"; it will never return an error on a
>> write, but just try to read from it, and you will be sorry.
>
> It would be interesting to see what SMART says about drive B, especially
> the short and long self tests.
>
> -
> 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
>
On my hard drives, automatic online testing is turned on, and so is
automatic offline testing. I run the long self-test once a week.
I have two drives which can play the role of B. One of them has this
SMART output:
[root@cmccabe-devel root]# smartctl -d ata /dev/sdb -H
smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
Drive failure expected in less than 24 hours. SAVE ALL DATA.
Failed Attributes:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 004 004 024 Pre-fail
Always FAILING_NOW 133273031255
The other one passes SMART.
Both of them eat data, though.
Colin
next prev parent reply other threads:[~2007-05-18 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 14:47 unreadable drives can be synchronized? Andrew Burgess
2007-05-18 15:04 ` Tomasz Chmielewski
2007-05-18 18:18 ` Colin McCabe
2007-05-23 17:46 ` Bill Davidsen
2007-05-18 18:10 ` Colin McCabe [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-16 15:50 Colin McCabe
2007-05-16 17:22 ` Bill Davidsen
2007-05-16 20:09 ` Colin McCabe
2007-05-16 20:18 ` Colin McCabe
2007-05-17 0:54 ` Neil Brown
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=464DEC2A.6040209@gmail.com \
--to=colin.p.mccabe@gmail.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.