From: Vishal Rao <vishalrao@gmail.com>
To: David Rees <drees76@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: Thu, 28 Jan 2010 05:54:46 +0530 [thread overview]
Message-ID: <aacba7e1001271624r4111908ch7a54e315ede54bbb@mail.gmail.com> (raw)
In-Reply-To: <72dbd3151001271541l7026389fgd2c91f9ee6502472@mail.gmail.com>
2010/1/28 David Rees <drees76@gmail.com>:
>
> 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.
The first "badblocks /dev/sda7" run went ahead with no output.
Now running "badblocks -nv /dev/sda7" on this unmounted 20gb partition
and it's taking a little while for the nondestructive read+write test but
so far again no output indicating errors - will post full output shortly.
---
Yes, I'd come across this one - ran just the plain command first on
hopefully the same disk "areas" which initially had Arch and Fedora
partitions which also exhibited the same problem but I blew them away
and repartitioned/reformatted as ext4 from my ubuntu installation.
I trust (based on the man page) that badblocks re-checks any blocks
marked away by formatting (i didnt select the 'check bad blocks' option
during formatting via gparted) so the problem is not hidden?
next prev parent reply other threads:[~2010-01-28 0:24 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
2010-01-28 0:24 ` Vishal Rao [this message]
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=aacba7e1001271624r4111908ch7a54e315ede54bbb@mail.gmail.com \
--to=vishalrao@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drees76@gmail.com \
--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 \
/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®