From: "Molle Bestefich" <molle.bestefich@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: SATA repeated failure (command 0x35 timeout, status 0xd8)
Date: Sun, 24 Sep 2006 17:16:24 +0200 [thread overview]
Message-ID: <62b0912f0609240816q54c3535bt86f781745ecbfa13@mail.gmail.com> (raw)
Hi,
I have a box with the following hardware/software configuration.
# uname -r
2.6.16.5
# lspci | grep SATA
00:0b.0 CMD Technology Inc Silicon Image SiI 3112 SATARaid Controller (rev 02)
00:0d.0 CMD Technology Inc Silicon Image SiI 3112 SATARaid Controller (rev 02)
00:0f.0 CMD Technology Inc Silicon Image SiI 3112 SATARaid Controller (rev 02)
# cd /sys/bus/scsi/devices; for dev in `ls -1`; do name=`ls -1d
$dev/block*`; disk=`cat $dev/model`; echo "$name: $disk"; done
0:0:0:0/block:sda: Maxtor 6Y250M0
1:0:0:0/block:sdb: Maxtor 6Y200M0
2:0:0:0/block:sdc: Maxtor 6Y200M0
3:0:0:0/block:sdd: Maxtor 6Y200M0
4:0:0:0/block:sde: Maxtor 6Y200M0
5:0:0:0/block:sdf: Maxtor 6Y200M0
It can operate normally for the longest time, but all of a sudden the
following happens.
# dmesg
ata2: command 0x35 timeout, stat 0xd8 host_stat 0x1
ata2: translated ATA stat/err 0xd8/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata2: status=0xd8 { Busy }
sd 1:0:0:0: SCSI error: return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Scsi parity error
end_request: I/O error, dev sdb, sector 323729879
ATA: abnormal status 0xD8 on port 0xD095E0C7
ATA: abnormal status 0xD8 on port 0xD095E0C7
ATA: abnormal status 0xD8 on port 0xD095E0C7
--
ata2: command 0x35 timeout, stat 0xd8 host_stat 0x1
ata2: translated ATA stat/err 0xd8/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata2: status=0xd8 { Busy }
sd 1:0:0:0: SCSI error: return code = 0x8000002
sdb: Current: sense key: Aborted Command
Additional sense: Scsi parity error
end_request: I/O error, dev sdb, sector 323729887
ATA: abnormal status 0xD8 on port 0xD095E0C7
ATA: abnormal status 0xD8 on port 0xD095E0C7
ATA: abnormal status 0xD8 on port 0xD095E0C7
[ .. et cetera, always with sector += 8 .. ]
This usually happens during a write to the RAID.
Funny thing is, it always happens to /dev/sdb.
It's happened 100s of times, but not once to any other device than /dev/sdb.
Resetting and running Maxtor PowerMax reports that the drive has no
hardware problems whatsoever.
I can't think of anything useful, except that /dev/sdb sits on the
same controller card as /dev/sda, which is a slightly different disk
than the rest of the bunch.
What can/should I do?
next reply other threads:[~2006-09-24 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 15:16 Molle Bestefich [this message]
2006-09-26 5:10 ` Tejun Heo
2006-10-02 2:27 ` Molle Bestefich
2006-10-03 6:54 ` Tejun Heo
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=62b0912f0609240816q54c3535bt86f781745ecbfa13@mail.gmail.com \
--to=molle.bestefich@gmail.com \
--cc=linux-kernel@vger.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®