From: David Rees <drees76@gmail.com>
To: Vishal Rao <vishalrao@gmail.com>
Cc: Mark Lord <kernel@teksavvy.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
jgarzik@pobox.com, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org, trivial@kernel.org,
stable@kernel.org
Subject: Re: [PATCH] ata: Disable NCQ for Crucial M225 brand SSDs
Date: Wed, 27 Jan 2010 15:41:02 -0800 [thread overview]
Message-ID: <72dbd3151001271541l7026389fgd2c91f9ee6502472@mail.gmail.com> (raw)
In-Reply-To: <aacba7e1001271516k3bb82a0fq7e019b28f3b8972f@mail.gmail.com>
On Wed, Jan 27, 2010 at 3:16 PM, Vishal Rao <vishalrao@gmail.com> wrote:
> 2010/1/28 Mark Lord <kernel@teksavvy.com>:
>> The errors in that log indicate bad media.
>> So the question is, can you demonstrate Win7rc NOT having the same
>> errors when accessing the SAME (logical) sectors ?
>
> Would that mean I have to blow away my precious ext4 partitions and
> have them Win7rc NTFS formatted and run a full check-disk with
> bad block checking enabled?
No - you just need a tool to do a full read of the partition. You
could use the cygwin tools and dd, for example.
> In the mean time, can I run a linux command (please tell me what it is or
> I will search for something to run online) or tool while NCQ is disabled (via
> libata.force=noncq) that can do a disk scan with bad block checking?
badblocks <name of partition>
See the man page for more details, but that should do a read test -
may want to boot from a rescue disk or from another disk if possible
to run the test.
-Dave
next prev parent reply other threads:[~2010-01-27 23:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 15:04 Vishal Rao
2010-01-26 16:02 ` Alan Cox
2010-01-26 16:19 ` Vishal Rao
2010-01-26 20:27 ` Willy Tarreau
2010-01-26 20:51 ` David Rees
2010-01-27 0:21 ` Vishal Rao
2010-01-27 0:32 ` David Rees
2010-01-27 0:49 ` Vishal Rao
2010-01-27 1:02 ` Alan Cox
2010-01-27 1:14 ` Vishal Rao
2010-01-27 22:44 ` Mark Lord
2010-01-27 23:16 ` Vishal Rao
2010-01-27 23:41 ` David Rees [this message]
2010-01-28 0:24 ` Vishal Rao
2010-01-28 2:12 ` Vishal Rao
2010-01-27 15:39 ` Jarod Wilson
2010-01-27 16:14 ` Vishal Rao
2010-01-28 20:12 ` Jarod Wilson
2010-01-26 21:46 ` Jeff Garzik
2010-01-27 0:24 ` Vishal Rao
2010-01-27 2:23 ` Mark Lord
2010-01-27 5:36 ` Vishal Rao
2010-01-27 12:15 ` Vishal Rao
2010-01-27 22:49 ` Mark Lord
2010-01-29 3:56 ` Mark Lord
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=72dbd3151001271541l7026389fgd2c91f9ee6502472@mail.gmail.com \
--to=drees76@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=trivial@kernel.org \
--cc=vishalrao@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
all inboxes | Powered by JetHome®