public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Rik van Riel <riel@redhat.com>,
	Alexander Nagel <feuerschwanz76@web.de>,
	linux-kernel@vger.kernel.org
Subject: Re: new harddrive with media error
Date: Mon, 01 Jan 2007 13:21:36 +0900	[thread overview]
Message-ID: <45988C50.5070001@gmail.com> (raw)
In-Reply-To: <20061231001201.GT17561@ftp.linux.org.uk>

Al Viro wrote:
> From the look of it, I'd say that it's size reported by disk being
> more than what's accessible.  Take a look at the block numbers...

How so?

ata1.00: ATA-7, max UDMA/133, 976773168 sectors: LBA48 NCQ (depth 0/32)

sda: Current: sense key: Medium Error
     Additional sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sda, sector 976751999
Buffer I/O error on device sda1, logical block 976751936

It seems like a genuine media error to me.  Many drives suffer a number 
of media errors in its lifetime.  Read errors happen regularly and most 
such errors are corrected by ECC, but sometimes you're just not lucky 
enough.  Some of them are real bad sectors while others might be due to 
degraded record quality even when the sector itself isn't necessary bad. 
  In most cases, the drive will reallocate the area including the sector 
when you write to it.

Simply rewriting the affected file should solve the problem.  Examine 
the result of 'smartctl -d ata -a' just in case.  For data of any 
importance, it's always wise to use raid 1 or 5 and backup regularly. 
Both help keeping your data safe in more than one way.  Raid re-sync is 
an easy way out of partial media failures and backing up not only gives 
you another copy of the data but gives the drives chance to detect 
degrading area quickly and reallocate before actual read failures begin 
to occur.

-- 
tejun


  reply	other threads:[~2007-01-01 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-30 22:44 new harddrive with media error Alexander Nagel
2006-12-30 23:33 ` Rik van Riel
2006-12-31  0:12   ` Al Viro
2007-01-01  4:21     ` Tejun Heo [this message]
2007-01-01 16:01       ` Alexander Nagel

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=45988C50.5070001@gmail.com \
    --to=htejun@gmail.com \
    --cc=feuerschwanz76@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=viro@ftp.linux.org.uk \
    /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