Date: Mon, 19 Oct 2009 10:39:33 -0400 (EDT)
From: Alan Stern <stern@rowland.harvard.edu>
To: Felipe Contreras <felipe.contreras@gmail.com>
cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       <linux-usb@vger.kernel.org>
Subject: Re: Annoying problems with lacie external hd (JMicron 0x2339?)
In-Reply-To: <94a0d4530910181517vc3a0766la727d7c97d7792b5@mail.gmail.com>
Message-ID: <Pine.LNX.4.44L0.0910191035260.3899-100000@iolanthe.rowland.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1341
Lines: 32

On Mon, 19 Oct 2009, Felipe Contreras wrote:

> On Thu, Oct 8, 2009 at 11:46 PM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
> > On Tue, Oct 6, 2009 at 11:10 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> >> A usbmon trace would contain more information.  We could see the exact
> >> sequence of commands and error codes.  I'm not sure it would help solve
> >> anything, though.
> >
> > I followed the tutorial and the resulting log is 73M long. I don't
> > know what I'm looking for, so there it is:
> > http://people.freedesktop.org/~felipec/1.mon.out
> 
> Can you take a look? Is there anything else I can provide?

Unforunately the usbmon trace isn't much help.  It shows several 
unrecovered read errors, but you already know that the disk has a bunch 
of bad sectors.

Then near the end, for no apparent reason, it shows a failure right in 
the middle of a READ command.  The computer tried to read 128 sectors;
the drive sent back 48 sectors of data and then stopped responding.  
Something in the firmware crashed; my guess is that the bridge chip 
failed.

Alan Stern

--
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/