Re: Bad Spot on Disk

> Query smart and see what that says. If smart does not like the drive > replace it with all possible haste.

     Thanks, that helped.
     SMART *did* see an error, but aborted its testing immediately so all I 
knew was there was at least one read error. (The quick test didn't find 
anything, and the extended test aborted as described. Not very impressive.)
     On the other hand, "/sbin/badblocks /dev/hda3" (the failing partitition) 
was much more descriptive. It turned up 23 failures. One of my associates 
said I could then use "/sbin/e2fsck -c /dev/hda3" to essentially map-out the 
bad areas but, with that number of failures, a replacement drive was probably 
a good idea.
     I'm gonna replace it tomorrow.
     Tonight I'll pick up a 2.5" --> IDE adapter and attempt to "dd" a copy on 
my workstation and then dump (er, "dd") that back out to the new drive. 
(That'll copy the bad block list, too -- not sure what to do about that 
except re-run e2fsck on the new drive.)
     Anyway, thanks again.

This message is part of the following thread:
	the complete thread tree sorted by date
	Rob Wultsch at
	Rob Wultsch at