On 10/12/2013 02:42 PM, Tom Metro wrote:
Jerry Feldman wrote:
..would I be better served by removing this from the RAID pair,
and run a full destructive bad block scan 'badblocks -wsv /dev/sda ...
Yes. Even a non-destructive read-write scan (-n), followed by a RAID
resync would do the trick
Matthew Gillen wrote:
Might be quicker to take the drive out of your RAID, attempt to write
just to that block that you know is bad...
Definitely quicker, but if you can live without the drive for a bit,
better to do a full write test on the drive, because Ed might be right,
and it could be an
Tom Metro wrote:
Definitely quicker, but if you can live without the drive for a bit,
better to do a full write test on the drive, because Ed might be right,
and it could be an expanding problem.
I'm with Ed. Any problem that isn't automatically corrected by a disk's
on-board controller is
I've brought this up before. One of the drives in my RAID reports an
unreadable sector. I'm not worried about thisas this otherwise seems to
be a serviceable driveand I take frequent backups. One question I might
have is would I be better served by removing this from the RAID pair,
and run a full
On 10/12/2013 8:06 AM, Jerry Feldman wrote:
I've brought this up before. One of the drives in my RAID reports an
unreadable sector. I'm not worried about thisas this otherwise seems to
be a serviceable driveand I take frequent backups. One question I might
have is would I be better served by
On Sat, 12 Oct 2013, Jerry Feldman wrote:
I've brought this up before. One of the drives in my RAID reports an
unreadable sector. I'm not worried about thisas this otherwise seems to
be a serviceable driveand I take frequent backups. One question I might
have is would I be better served by
From: discuss-bounces+blu=nedharvey@blu.org [mailto:discuss-
bounces+blu=nedharvey@blu.org] On Behalf Of Jerry Feldman
I've brought this up before. One of the drives in my RAID reports an
unreadable sector. I'm not worried about thisas this otherwise seems to
be a serviceable
Also, at the hardware level, invisible to the OS, drives reserve a certain
number of blocks for transparent remapping. So if the number of bad blocks on
your drive is higher than the number the drive can cover up... You might find
that the specific addresses of bad blocks reported to your OS
