From: Marc MERLIN <marc@merlins.org>
To: Roger Heflin <rogerheflin@gmail.com>
Cc: Adam Goryachev <mailinglists@websitemanagers.com.au>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: force remapping a pending sector in sw raid5 array
Date: Tue, 6 Feb 2018 14:46:05 -0800 [thread overview]
Message-ID: <20180206224605.jhw22hpvehe2flt4@merlins.org> (raw)
In-Reply-To: <CAAMCDeeFVY_NVnzdZYumyxJ_aUTy9_gybhFDqfazSMOqPOeU2A@mail.gmail.com>
On Tue, Feb 06, 2018 at 04:31:58PM -0600, Roger Heflin wrote:
> What kind of drive is it? I have had good luck getting seagates to
> remap, on my 3tb WD Red drive with bad sectors the drive does not seem
> to remap them as easily.
Device Model: WL6000GSA6457
Serial Number: WOL240367065
LU WWN Device Id: 5 0014ee 05932b834
Firmware Version: 82.00A82
User Capacity: 6,001,175,126,016 bytes [6.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 9
ATA Standard is: Not recognized. Minor revision code: 0x001f
> So far I have a lot of repeat bad sectors, but only 1 has remapped,
> even thought I am given the drive a lot of chances to remap the
> sectors.
Yeah, it seems that things don't work like they should.
Glad to know that it's not just me, then :)
I'll probably return these drives because that behaviour is not ok, but
at the same time it's interesting to learn about failure cases on data
that I could afford to lose (mostly it's the time lost to re-sync a very
big backup, i.e 1 to 2 weeks)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
next prev parent reply other threads:[~2018-02-06 22:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 18:14 force remapping a pending sector in sw raid5 array Marc MERLIN
2018-02-06 18:59 ` Reindl Harald
2018-02-06 19:36 ` Marc MERLIN
2018-02-06 20:03 ` Andreas Klauer
2018-02-06 21:51 ` Adam Goryachev
2018-02-06 22:02 ` Marc MERLIN
2018-02-06 22:31 ` Roger Heflin
2018-02-06 22:46 ` Marc MERLIN [this message]
2018-02-07 4:29 ` Marc MERLIN
2018-02-07 9:42 ` Kay Diederichs
2018-02-09 19:29 ` Marc MERLIN
2018-02-09 19:57 ` Kay Diederichs
2018-02-09 20:02 ` Roger Heflin
2018-02-09 20:13 ` Phil Turmel
2018-02-09 20:29 ` Marc MERLIN
2018-02-09 20:44 ` Phil Turmel
2018-02-09 21:22 ` Marc MERLIN
2018-02-09 22:07 ` Wol's lists
2018-02-09 22:36 ` Marc MERLIN
2018-02-09 20:52 ` Kay Diederichs
2018-02-11 20:52 ` Roger Heflin
2018-02-09 21:17 ` Kay Diederichs
2018-02-10 21:43 ` Mateusz Korniak
2018-02-11 15:41 ` Marc MERLIN
2018-02-11 16:41 ` Marc MERLIN
2018-02-11 17:13 ` Phil Turmel
2018-02-11 18:02 ` Wols Lists
2018-02-12 10:43 ` Mateusz Korniak
2018-02-12 15:29 ` Phil Turmel
2018-02-12 16:49 ` Marc MERLIN
2018-02-12 17:16 ` Phil Turmel
2018-02-12 17:30 ` Marc MERLIN
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=20180206224605.jhw22hpvehe2flt4@merlins.org \
--to=marc@merlins.org \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
--cc=rogerheflin@gmail.com \
/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