From: Tejun Heo <htejun@gmail.com>
To: Molle Bestefich <molle.bestefich@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: SATA repeated failure (command 0x35 timeout, status 0xd8)
Date: Tue, 03 Oct 2006 15:54:53 +0900 [thread overview]
Message-ID: <4522093D.9040506@gmail.com> (raw)
In-Reply-To: <62b0912f0610011927k789b63f4r370b419e5b98bb5f@mail.gmail.com>
Molle Bestefich wrote:
[--snip--]
> The above repeats itself thru modes UDMA/66, UDMA/44, UDMA/33,
> UDMA/25, UDMA/16, PIO4, PIO3, PIO1 and PIO0.
Can you full dmesg for this? Preferably w/ timestamp?
> At which point /dev/sdb disappears completely, only to reappear as
> /dev/sdh:
> ===============
> SCSI device sdh: 398297088 512-byte hdwr sectors (203928 MB)
> sdh: Write Protect is off
> sdh: Mode Sense: 00 3a 00 00
> SCSI device sdh: drive cache: write back
> SCSI device sdh: 398297088 512-byte hdwr sectors (203928 MB)
> sdh: Write Protect is off
> sdh: Mode Sense: 00 3a 00 00
> SCSI device sdh: drive cache: write back
> ===============
>
> (Odd.)
>
> I don't get why PowerMax works this drive just fine while Linux
> doesn't. Perhaps because PowerMax only uses SMART commands and
> doesn't transfer data over the SATA bus?
>
> Anyway, with the device now failing fairly consistently, I guess I
> should begin moving around cables, controllers, disks etc. again. I'm
> very worried about doing this though, since I'm pretty sure that it'll
> break the MD array on the disks very quickly..
Your problem seems to be hardware transmission error. I don't know what
a powermax is and doesn't know what it does, so you'll have to play the
swap-and-see-what-breaks game to figure out the problematic part.
Thanks.
--
tejun
prev parent reply other threads:[~2006-10-03 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62b0912f0609240816q54c3535bt86f781745ecbfa13@mail.gmail.com>
2006-09-26 5:10 ` SATA repeated failure (command 0x35 timeout, status 0xd8) Tejun Heo
2006-10-02 2:27 ` Molle Bestefich
2006-10-03 6:54 ` Tejun Heo [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=4522093D.9040506@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=molle.bestefich@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).