From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Cox Subject: Re: Problem with ata layer in 2.6.24 Date: Tue, 29 Jan 2008 19:34:03 +0000 Message-ID: <20080129193403.62fe95e8@core> References: <200801272122.21823.gene.heskett@gmail.com> <1201539043.31293.7.camel@zem> <1201540830.6526.19.camel@localhost> <200801281230.32910.gene.heskett@gmail.com> <479E1D9E.3000900@bobjweil.com> <20080129121201.2f727f5f@core> <20080129184613.16846ae5@core> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:53302 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752839AbYA2Tii (ORCPT ); Tue, 29 Jan 2008 14:38:38 -0500 In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Daniel Barkalow Cc: Richard Heck , Gene Heskett , Zan Lynx , Calvin Walton , Linux Kernel Mailing List , Linux ide Mailing list > I've seen a lot of verbosity out of SCSI messages, but I haven't seen a > straightforward interpretation of the problem in there. It's all > information useful for debugging, not information useful for system > administration. It tells you what is going on. Unfortunately that frequently requires some basic knowledge of how to interpret the error report. Drive interface behaviour simply doesn't boil down to a fault light on the dashboard or a "tighten the cable". For most common fault types you'll get errors most administrators should find meaningful - like "Media error" > On the other hand, bringing the system down because a device is > misbehaving is a poor idea. I've personally recovered most of the data off Hence we have RAID and SATA hotplug. Alan