[Linux-disciples] SMART error (OfflineUncorrectableSector) detected on host: JeffTweedy (fwd)

[Adam Rosi-Kessel]

On Mon, Nov 29, 2004 at 08:44:20AM -0500, Stephen R Laniel wrote:
> I started running e2fsck with the -c option last night
> around midnight, and eight hours later it was only about
> halfway done checking for bad blocks. Is there a faster way
> to do that? I assume sysadmins for large sites don't need to
> take their servers down for 16 hours at a time to fix a bad
> sector.

No, they replace their hard drives immediately and deal with the problem
drives offline.  

I'm not sure why your system is so slow, but e2fsck -c (or -c -c) is how
I always deal with this.  It did take quite a long while on my laptop,
but was fairly quick on another similar laptop with the same sized drive.

On Sun, Nov 28, 2004 at 10:58:25PM -0500, Stephen R Laniel wrote:
> I've had what appears to be my first really serious SMART
> error. Can someone who's run into one before tell me what to
> do with this? How do I fix it? (Last 100 lines in syslog
> matching 'smartd' below.)

> Nov 28 20:52:02 JeffTweedy smartd[1191]: Device: /dev/hdd, 1 Currently unreadable (pending) sectors 

This is common. It's happened on many of my new drives, and is not fatal.

SMART will try very hard to read a bad block; once it reads it once
successfully, it relocates the data and marks the block off-limits.  If
it can't ever read the block, it is never "released" and you keep getting
this error.

The badblocks howto, linked from the smartmontools FAQ, describes in
detail exactly how to deal withhis problem.  I'm not online right now so
I don't have the link, but it should be easy to find.
-- 
Adam Rosi-Kessel
http://adam.rosi-kessel.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.bostoncoop.net/pipermail/linux-disciples/attachments/20041129/2a86c7aa/attachment-0001.pgp