From: Mark Lord <kernel@teksavvy.com>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata_mv and Highpoint RocketRAID 230x, corruption?
Date: Sat, 23 Oct 2010 11:49:17 -0400 [thread overview]
Message-ID: <4CC303FD.1000802@teksavvy.com> (raw)
In-Reply-To: <AANLkTin3QRgV5P4=BsTCeWhynGYMi3pd7BXrFpBXkWvj@mail.gmail.com>
On 10-10-23 11:20 AM, Mathias Burén wrote:
> Hi,
>
> Interesting, as the badblocks program doesn't think these sectors are
> bad. Can I test them any other way?
..
> On 23 October 2010 16:19, Mark Lord<kernel@teksavvy.com> wrote:
>> On 10-10-23 08:57 AM, Mathias Burén wrote:
..
>>> ata2.00: status: { DRDY }
>>> ata2: hard resetting link
>>> ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>>> ata2.00: configured for UDMA/133
>>> ata2.00: device reported invalid CHS sector 0
>>> sd 1:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
>>> sd 1:0:0:0: [sdb] Sense Key : 0xb [current] [descriptor]
>>> Descriptor sense data with sense descriptors (in hex):
>>> 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
>>> 00 00 00 00
>>> sd 1:0:0:0: [sdb] ASC=0x0 ASCQ=0x0
>>> sd 1:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 e7 70 c8 e8 00 05 40 00
>>> end_request: I/O error, dev sdb, sector 3882928360
>>> md/raid:md0: read error not correctable (sector 3882926312 on sdb1).
>>> md/raid:md0: Disk failure on sdb1, disabling device.
>>
>>
>> No, that error looks like a real disk media error -- bad sector(s) on the drive.
>>
>> The BIOS issue merely gives corrupted data, not read errors.
MMm.. you're right.
I just now looked at the full dmesg you posted,
and those are NOT media errors.
It looks like NCQ commands are behaving strangely for some reason
in your 2.6.36 kernel.
Can you retest with, say, 2.6.34 ?
There were a number of sata_mv updates in between,
and I'm wondering if perhaps one of them broke something?
Or if you just want to stabilize things, then turn off NCQ.
Cheers
next prev parent reply other threads:[~2010-10-23 15:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 20:03 sata_mv and Highpoint RocketRAID 230x, corruption? Mathias Burén
2010-10-23 1:59 ` Mark Lord
2010-10-23 2:21 ` Daniel Taylor
2010-10-23 15:21 ` Mark Lord
2010-10-23 12:57 ` Mathias Burén
2010-10-23 15:19 ` Mark Lord
2010-10-23 15:20 ` Mathias Burén
2010-10-23 15:49 ` Mark Lord [this message]
2010-10-23 16:08 ` Mathias Burén
2010-10-24 12:52 ` Mathias Burén
2010-10-25 21:26 ` Mark Lord
2010-10-25 21:31 ` Mathias Burén
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=4CC303FD.1000802@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.buren@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