All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael G. Morey" <mmorey@optivel.com>
To: Reiser Filesystem User List <reiserfs-list@namesys.com>
Subject: SMART Self-Test Reports UNC Errors on Dell Latitude D800 Hitachi Travelstar DK23FB
Date: Thu, 12 Aug 2004 11:22:03 -0500	[thread overview]
Message-ID: <1092327723.16346.7.camel@turing.optivel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

All,

I've installed and run the smartmontools package backported to Debian
GNU/Linux 3.0r1 from http://www.backports.org, and have run the short
and extended Offline self tests.  The results are as follows:

smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining 
LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       80%     
4089         8371832
# 2  Short offline       Completed without error       00%     
4088         -
# 3  Short offline       Completed without error       00%        
0         -

My manager suggested that I reformat the partitions (we use ReiserFS
3.6), to mark the bad blocks.  Is this a viable option?  Can the drive
be salvaged, or should it be replaced?

Thanks in advance.
-- 
Michael G. Morey <mmorey@optivel.com>
Optivel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-08-12 16:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12 16:22 Michael G. Morey [this message]
2004-08-12 17:32 ` SMART Self-Test Reports UNC Errors on Dell Latitude D800 Hitachi Travelstar DK23FB Bernd Schubert
2004-08-12 17:48   ` Michael G. Morey
2004-08-12 18:28     ` Bernd Schubert
2004-08-12 20:18   ` Lamont R. Peterson
2004-08-13  0:12     ` Philippe Gramoullé
2004-08-13  0:18       ` Lamont R. Peterson
2004-08-13  2:12         ` Philippe Gramoullé

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1092327723.16346.7.camel@turing.optivel.com \
    --to=mmorey@optivel.com \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.