From: Bruce Allen <ballen@gr...> - 2006-07-27 18:55:12
A full self-test moves the disk head across the entire disk surface to
read all the sectors. If a disk is suffering from mechanical problems,
this might be "the straw that breaks the camel's back". But in most cases
a self-test error is just due to a corrupted sector. In this case,
continued self-tests will not do any harm.
On Mon, 17 Jul 2006, shebert wrote:
> Message body follows:
> Greetings Mister Allen,
> I have a technical question about smartctl. I'm building a
> system on which i start a smart selftest every day. If i
> found an error on the disk it is possible the system will
> run with the damaged disk for several days. Furthermore it
> is not a big deal if the system stop working or if we lost
> all the disk data. However, when smartctl report an error
> should i stop doing my daily test until we change the disk.
> Can the smart sefltest cause more damage on a disk already
> damaged ?
> PS: I'm sorry to send this question directly to you, but the
> mailing list is in read-only for me.
> This message has been sent to you, a registered SourceForge.net user,
> by another site user, through the SourceForge.net site. This message
> has been delivered to your SourceForge.net mail alias. You may reply
> to this message using the "Reply" feature of your email client, or
> using the messaging facility of SourceForge.net at: