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
On 10/12/2013 03:06 PM, Tom Metro wrote:
For those using the Cinnamon desktop environment, you may be interested
to know that this past week the project had a big update from 1.8 to
2.0. They've added a pile of new features.
This is the version that will go into the November release of Linux
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
