public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
Date: Thu, 27 May 2010 11:52:00 +0800	[thread overview]
Message-ID: <1274932320.16963.24.camel@bunyip.localdomain> (raw)
In-Reply-To: <20100527024359.GA5123@solfire>

On Thu, 2010-05-27 at 04:43 +0200, meino.cramer@gmx.de wrote:
> walt <w41ter@gmail.com> [10-05-27 04:08]:
> > On 05/26/2010 05:19 PM, meino.cramer@gmx.de wrote:
> > 
> > >Is there any way to check the disk without damaging its
> > >contents?
> > 
> > Do you know about SMART?  Install sys-apps/smartmontools if you
> > don't already have it, and read the manpage for smartctl.
> > 
> > I add smartd to my default runlevel so the hard drives will test
> > themselves once every month and log the test results in syslog.
> > 
> > Hm.  I just noticed that smartd isn't actually running, so I need
> > to do some debugging now.  But that's the idea, anyway.
> > 
> 
> Hi,

> yes, I know smart...
> 
> I was more thinking of a tool, which test the whole disc surface
> and reports every bad sector.
> 
> Smarts is more of statistical kind: It counts events and tries
> to calculate dooms day from that ;)
> 
> 

Not so easy (coming in late on this thread, sorry if its been covered)

Modern hard drives insulate the outside from whats actually happening
internally.  They have a number of spare locations they can swap into
use when a bad patch develops.  This is invisible except to something
like smart reporting.  Rule of thumb - when a modern drive starts
showing bad sectors to the outside world, its already well past its use
by date.

So something like SMART is the only way for the average Joe to get the
health of a drive.

Google has lots on this sort of thing

BillK





  reply	other threads:[~2010-05-27  3:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  3:15 [gentoo-user] Harddisk trouble ... or not yet? meino.cramer
2010-05-26  6:38 ` [gentoo-user] howto increase INODE kitti jaisong
2010-05-26  7:09   ` Bert Swart
2010-05-26 11:16   ` Volker Armin Hemmann
2010-05-26 12:55   ` Alex Schuster
2010-05-26 11:17 ` [gentoo-user] Harddisk trouble ... or not yet? Volker Armin Hemmann
2010-05-26 14:22 ` [gentoo-user] " Grant Edwards
2010-05-26 17:09   ` meino.cramer
2010-05-26 17:59     ` Volker Armin Hemmann
2010-05-26 19:05       ` Neil Bothwick
2010-05-26 19:13         ` Volker Armin Hemmann
2010-05-26 20:40           ` Neil Bothwick
2010-05-27  0:19             ` meino.cramer
2010-05-27  1:48               ` walt
2010-05-27  2:43                 ` meino.cramer
2010-05-27  3:52                   ` W.Kenworthy [this message]
2010-05-27  4:29                     ` Iain Buchanan
2010-05-27  9:39                   ` Andrea Conti
2010-05-28  1:54                     ` meino.cramer
2010-05-28 23:24                       ` walt
2010-05-29  3:47                         ` meino.cramer
2010-05-29  7:25                       ` Andrea Conti
2010-05-29  8:16                         ` Volker Armin Hemmann
2010-05-29 19:05                           ` Alan McKinnon
2010-05-29 20:08                             ` Volker Armin Hemmann
2010-05-29  8:56                         ` meino.cramer
2010-05-29 19:13                           ` Andrea Conti
2010-05-27  8:17               ` Stroller

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=1274932320.16963.24.camel@bunyip.localdomain \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox