2007/11/8, Derick Siddoway <[EMAIL PROTECTED]>:
> the filesystem. What's the best way to do this short of monitoring?
sysutils/smartmontools
Best
Martin
try a new IDE cable or if you can take the system offline, and
assuming you can boot off cd/floppy I would suggest trying MHDD from
http://hddguru.com/ it does some pretty nice low-level diagnostics.
I've fixed some disks with this {crosses fingers}
docs are very basic but there's more info on the
All drives develop read errors over time. When you write to these blocks,
it may automatically remap them and the errors disappear. Just because you
get some read errors doesn't meant the drive is necessarily about to die. But
if you develop new bad blocks with any frequency, you might want to r
knitti wrote:
- SMART didn't catch the errors. no monitoring is perfect, but it
seems unlikely that it won't notice read errors
Also, SMART thresholds are defined by the vendor. Setting them too high
reduces the number of warranty claims.
You'll notice wd1 has raw read errors and pending/of
On 11/8/07, Derick Siddoway <[EMAIL PROTECTED]> wrote:
> Trying to copy a file from one filesystem to another, I kept getting
> input/output errors. I noticed these messages in the logs:
>
> wd1a: uncorrectable data error reading fsbn 768416 of 768384-0 (wd1 bn
> 768416; cn 762 tn 5 sn 5), retry
Trying to copy a file from one filesystem to another, I kept getting
input/output errors. I noticed these messages in the logs:
wd1a: uncorrectable data error reading fsbn 768416 of 768384-0 (wd1 bn 768416;
cn 762 tn 5 sn 5), retrying
wd1a: uncorrectable data error reading fsbn 768416 of 76838
6 matches
Mail list logo
