Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161632AbWJaLkn (ORCPT ); Tue, 31 Oct 2006 06:40:43 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161635AbWJaLkn (ORCPT ); Tue, 31 Oct 2006 06:40:43 -0500 Received: from mta.songnetworks.no ([62.73.241.54]:49394 "EHLO pebbles.fastcom.no") by vger.kernel.org with ESMTP id S1161632AbWJaLkm (ORCPT ); Tue, 31 Oct 2006 06:40:42 -0500 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: References: <453960B3.6040006@gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Roy Sigurd Karlsbakk Subject: Debugging I/O errors further? Date: Tue, 31 Oct 2006 12:40:44 +0100 To: linux-kernel@vger.kernel.org X-Mailer: Apple Mail (2.752.2) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1064 Lines: 34 >> Roy Sigurd Karlsbakk wrote: >> >>> Hi all >>> Stresstesting a SATA drive+controller, I get the error below >>> after a while. How can I find if this error is due to a >>> controller failure, a bad driver, or a drive failure? >> >> Is there any libata/SCSI error messages in your log? >> > > Nope. Just the ones from ext3. I first tried with a kernel from > debian etch, and then switched to 2.6.18.1. Same errors on both Hi all Sorry for stressing this, but is there a way I can debug this further? it's a seagate drive connected to a sata_sil controller. I only get ext3 errors, and it fails after a while whatever I do thanks roy -- Roy Sigurd Karlsbakk roy@karlsbakk.net ------------------------------- MICROSOFT: Acronym for "Most Intelligent Customers Realise Our Software Only Fools Teenagers" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/