Re: force remapping a pending sector in sw raid5 array

[Marc MERLIN <marc@merlins.org>]

On Sun, Feb 11, 2018 at 07:41:58AM -0800, Marc MERLIN wrote:
> As a last update on those drives, sadly they seem to have real problems
> with SMART, which is why I was confused when using them.
> 
> myth:~# badblocks -fsvn -b512 /dev/sdf
> /dev/sdf is apparently in use by the system; badblocks forced anyway.
> Checking for bad blocks in non-destructive read-write mode
> From block 0 to 3131110575
> Checking for bad blocks (non-destructive read-write test)
> Testing with random pattern: done                                                 
> Pass completed, 0 bad blocks found. (0/0/0 errors)
> 
> That means a full read/write scan ran ok.
> Yet:
> 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
> 197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       7
> 
> 7 sectors still marked as pending. This makes no sense...
 
And it gets "better", just re-ran a long self test, and still got:
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%       561         569442000

So, the disk sees bad blocks, SMART says there are bad blocks, and
badblocks run over the entire drive in read/write mode, finds nothing
anymore.

Anyway, those drives are going back in the box and the mail tomorrow,
but that sure is/was weird...

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