From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: Need help understanding SATA error message. Date: Fri, 11 Apr 2008 15:16:41 +0900 Message-ID: <47FF0249.5040901@gmail.com> References: <47ED136F.9010501@rtr.ca> <47ED15D2.3080403@rtr.ca> <47EDBC87.8090109@rtr.ca> <47F0376F.2090000@gmail.com> <47F0FAD3.9060001@rtr.ca> <47F18127.8070509@gmail.com> <47F19764.9080705@rtr.ca> <47F224F9.40906@rtr.ca> <47F25FAD.1090200@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from po-out-1718.google.com ([72.14.252.158]:10076 "EHLO po-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752910AbYDKGQw (ORCPT ); Fri, 11 Apr 2008 02:16:52 -0400 Received: by po-out-1718.google.com with SMTP id y22so530868pof.1 for ; Thu, 10 Apr 2008 23:16:51 -0700 (PDT) In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Tomas Lund Cc: linux-ide@vger.kernel.org Tomas Lund wrote: > On Wed, 2 Apr 2008, Tomas Lund wrote: > >> Apr 2 04:14:17 envy kernel: ata2.00: exception Emask 0x0 SAct 0x0 >> SErr 0x0 action 0x0 >> Apr 2 04:14:17 envy kernel: ata2.00: irq_stat 0x40000001 >> Apr 2 04:14:17 envy kernel: ata2.00: cmd >> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 >> Apr 2 04:14:17 envy kernel: res >> 51/04:00:0a:24:f9/00:00:00:00:00/a9 Emask 0x1 (device error) >> Apr 2 04:14:17 envy kernel: ata2.00: status: { DRDY ERR } >> Apr 2 04:14:17 envy kernel: ata2.00: error: { ABRT } >> Apr 2 04:14:17 envy kernel: ata2.00: configured for UDMA/133 >> Apr 2 04:14:18 envy kernel: ata2: EH complete >> Apr 2 04:14:18 envy kernel: sd 1:0:0:0: [sdb] 1953525168 512-byte >> hardware sectors (1000205 MB) >> Apr 2 04:14:18 envy kernel: sd 1:0:0:0: [sdb] Write Protect is off >> Apr 2 04:14:18 envy kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 >> Apr 2 04:14:18 envy kernel: sd 1:0:0:0: [sdb] Write cache: enabled, >> read cache: enabled, doesn't support DPO or FUA > > The errors continue to occur at random interval, even after i stoped the > copy-alot-of-files-and-sync stresstest. > > Any other ideas or things to try? Looks like a broken drive to me. Can you put it on a different controller? -- tejun