From owner-freebsd-questions@freebsd.org Wed Aug 17 21:52:18 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2FC8BBDF27 for ; Wed, 17 Aug 2016 21:52:18 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from mail.kc8onw.net (kc8onw.net [206.55.216.50]) by mx1.freebsd.org (Postfix) with ESMTP id B7CEC1DAE for ; Wed, 17 Aug 2016 21:52:18 +0000 (UTC) (envelope-from jonathan@kc8onw.net) Received: from [10.70.3.102] (99-55-193-152.lightspeed.iplsin.sbcglobal.net [99.55.193.152]) by mail.kc8onw.net (Postfix) with ESMTPSA id DEF3D3912; Wed, 17 Aug 2016 17:52:17 -0400 (EDT) Subject: Re: Lexar flash drive dead? To: Alphons van Werven , RW References: <20160817130943.6c2315df@gumby.homeunix.com> <20160817131138.1775b70f@gumby.homeunix.com> <20160817125805.GA56841@spectrum.skysmurf.nl> Cc: freebsd-questions@freebsd.org From: Jonathan Stewart Message-ID: <6759c085-2906-8481-b2e4-4f80359ec994@kc8onw.net> Date: Wed, 17 Aug 2016 17:52:13 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160817125805.GA56841@spectrum.skysmurf.nl> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2016 21:52:18 -0000 On 8/17/2016 8:58 AM, Alphons van Werven wrote: > RW via freebsd-questions wrote: > > ["re-CC'ed" OP] > >>> If you haven't already tried try swapping the connectors around using >>> a different connector on a different motherboard socket. >> Sorry I missed the USB bit. > Nevertheless, if not already done so it might eliminate the possibility > that the problem is with the computer the drive is connected to rather > than the drive itself. > > Other than that, in my experience errors like these usually suggest that > the drive itself is broken on the hardware level and cannot be rescued on > a software level. Depending on exactly where the failure lies and whether > that's a user-serviceable part (e.g. a connector or controller or some- > thing), it *might* be possible to salvage the data by replacing the com- > ponent in question with a "donor" component from a healthy drive of the > same make and type--or at least a similar device with compatible com- > ponents. However, this usually requires considerable expertise and even > then USB drives in particular often don't have a whole lot of removable > components in the first place. > > Fonz I've tried several USB ports on several different computers with no luck. I've resoldered contacts and traces on USB drives before but from what I can see nothing is visibly broken. As noted in my other email since the drive responds and IDs itself I'm guessing the flash chip BGA array is broken, which I have no ability to do anything with. The drive is still sold so if I can find someone that can do BGA work it would theoretically be possible to move the flash chip to a donor drive, but I have no idea where to look for that. Thanks, Jonathan