From: Robert Hancock <hancockrwd@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Ask for help with "qc timeout" and "failed to read log page 10h"
Date: Sun, 06 Jan 2013 22:02:31 -0600 [thread overview]
Message-ID: <50EA48D7.7000606@gmail.com> (raw)
In-Reply-To: <CACna6rxYU3Gap30nVbi8bXpxHF2pToPUUd-ckg0-40kT0FR7VQ@mail.gmail.com>
On 01/06/2013 02:59 AM, Rafał Miłecki wrote:
> I'm using old notebook (coming from about 2008) and recently
> experienced my first problem with the harddrive. There is one file I
> can not fully read. It's size is 4.4GB, but after copying 3.4GB I get
> that errors in dmesg and copying hangs.
>
> This is the only case where I experience this issue. As long as I
> don't touch that problematic file I don't see any problems/errors.
>
> Is this possible some part of the file was saved on a bad block of my
> hard drive? Can this mean some problem with the driver scanning for
> the bad blocks? Or could that be just an accident that block became a
> bad one after using it (when it was OK)?
>
> EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
> ata1.00: qc timeout (cmd 0x2f)
> ata1: failed to read log page 10h (errno=-5)
> ata1.00: exception Emask 0x1 SAct 0x3 SErr 0x0 action 0x6 frozen
> (... see dmesg.txt)
>
From the dmesg output (specifically the UNC bit) it looks like the
drive is reporting it is unable to read a number of sectors. I would
back up all important data possible from it and replace it ASAP.
Not sure what you mean by "the driver scanning for the bad blocks".
prev parent reply other threads:[~2013-01-07 4:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 8:59 Ask for help with "qc timeout" and "failed to read log page 10h" Rafał Miłecki
2013-01-07 4:02 ` Robert Hancock [this message]
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=50EA48D7.7000606@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=zajec5@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).