Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263837AbTKXTT7 (ORCPT ); Mon, 24 Nov 2003 14:19:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263839AbTKXTT6 (ORCPT ); Mon, 24 Nov 2003 14:19:58 -0500 Received: from sweetums.bluetronic.net ([24.199.150.42]:20869 "EHLO sweetums.bluetronic.net") by vger.kernel.org with ESMTP id S263837AbTKXTT5 (ORCPT ); Mon, 24 Nov 2003 14:19:57 -0500 Date: Mon, 24 Nov 2003 14:17:44 -0500 (EST) From: Ricky Beam To: Larry McVoy cc: Linux Kernel Mail List Subject: Re: data from kernel.bkbits.net In-Reply-To: <20031124155034.GA13896@work.bitmover.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1127 Lines: 25 On Mon, 24 Nov 2003, Larry McVoy wrote: >Sorry to be short but I already said that I'd eliminated this source of >error. What did you think I was doing all weekend? Let me be equally short. Your original message gave no details of what debugging steps had been taken. (I can assume you would know what you're doing, but frankly, I could be wrong.) You venture a guess that the system had been h4x0r3d in some inventive way to prevent your attempts to recover data and proceed to paste error messages from the 3ware driver that indicate a problem with the hardware (either driver bug, cabling, controller, or channel on that controller) including the drive itself. Please do not attribute to hackers what is simply a half dead drive. So, was the machine powered down for an extended period as I aluded? (to preserve the machine until someone had time to look at it.) --Ricky - 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/