From: PFC <lists@peufeu.com>
To: kernel-lists@projecthugo.co.uk, Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: [git patch] 2.6.x libata fix
Date: Thu, 12 Jan 2006 11:57:49 +0100 [thread overview]
Message-ID: <op.s29h2nbncigqcu@apollo13> (raw)
In-Reply-To: <43C628FE.9020303@projecthugo.co.uk>
Hello,
I've had a lot of problems with nv_sata (nforce3) and Maxtor harddrives.
Basically it always boils down to :
Dec 24 23:04:34 apollo13 ata3: command 0x35 timeout, stat 0xd0 host_stat
0x21
Dec 24 23:04:34 apollo13 ata3: translated ATA stat/err 0x35/00 to SCSI
SK/ASC/ASCQ 0x4/00/00
Dec 24 23:04:34 apollo13 ata3: status=0x35 { DeviceFault SeekComplete
CorrectedError Error }
Dec 24 23:04:34 apollo13 sd 2:0:0:0: SCSI error: return code = 0x8000002
Dec 24 23:04:34 apollo13 sdc: Current: sense key=0x4
Dec 24 23:04:34 apollo13 ASC=0x0 ASCQ=0x0
Dec 24 23:04:34 apollo13 end_request: I/O error, dev sdc, sector 490223295
Dec 24 23:04:34 apollo13 raid5: Disk failure on sdc1, disabling device.
Operation continuing on 3 devices
Plugging the Maxtor drives on the not-nv SATA sockets solved it (thanks
god I have 2 maxtor and 2 seagate drives)...
If you want more info, just ask.
next prev parent reply other threads:[~2006-01-12 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060109171104.GA25793@havoc.gtf.org>
[not found] ` <43C4DB86.7030603@projecthugo.co.uk>
2006-01-12 10:01 ` [git patch] 2.6.x libata fix Matt Darcy
2006-01-12 10:57 ` PFC [this message]
2006-01-13 9:26 ` Matt Darcy
2006-01-12 11:46 ` Matt Darcy
2006-01-13 11:26 ` [git patch] 2.6.x libata fix more information (sata_mv problems continued) Matt Darcy
2006-01-13 11:42 ` Jens Axboe
2006-01-13 17:14 ` Sebastian Kuzminsky
2006-01-13 19:51 ` Matt Darcy
2006-01-13 21:06 ` [git patch] 2.6.x libata fix more information DEBUG INFO !!! Matt Darcy
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=op.s29h2nbncigqcu@apollo13 \
--to=lists@peufeu.com \
--cc=jgarzik@pobox.com \
--cc=kernel-lists@projecthugo.co.uk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).