From: Bernd Schubert <bernd-schubert@web.de>
To: reiserfs-list@namesys.com
Subject: Re: SMART Self-Test Reports UNC Errors on Dell Latitude D800 Hitachi Travelstar DK23FB
Date: Thu, 12 Aug 2004 19:32:07 +0200 [thread overview]
Message-ID: <200408121932.08943.bernd-schubert@web.de> (raw)
In-Reply-To: <1092327723.16346.7.camel@turing.optivel.com>
> 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?
>
Whats your definition of 'reformating'? Its certainly not
'mkreiserfs /dev/my_partition'. You would need a tool for a low level format
of the disk, I don't know if there are any for IDE disks.
Smartctl should also return the 'reallocated sector count' values, if those
are only a few ones, it might be worth a try to run 'badblocks
-n /dev/my_device', I think most drives only reallocate sectors when data are
written to them. After this has finished, try the badblocks and smartctl
command again, if there are still any errors, I would just get a new drive.
Somewhere on the namesys site you will also find an article about badblocks
handling with reiserfs, but I would do this only in absolut emergency if I
would need to rescue my data.
Cheers,
Bernd
next prev parent reply other threads:[~2004-08-12 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 16:22 SMART Self-Test Reports UNC Errors on Dell Latitude D800 Hitachi Travelstar DK23FB Michael G. Morey
2004-08-12 17:32 ` Bernd Schubert [this message]
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=200408121932.08943.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--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.