From owner-freebsd-questions@FreeBSD.ORG Mon May 18 17:51:26 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A221F1065675 for ; Mon, 18 May 2009 17:51:26 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by mx1.freebsd.org (Postfix) with SMTP id 42B148FC0A for ; Mon, 18 May 2009 17:51:25 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from source ([209.85.146.183]) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKShGgHTqVPC61n+9GhVD5Q4kbisLN5Dp0@postini.com; Mon, 18 May 2009 10:51:26 PDT Received: by wa-out-1112.google.com with SMTP id k17so1320949waf.20 for ; Mon, 18 May 2009 10:51:25 -0700 (PDT) Received: by 10.114.183.1 with SMTP id g1mr11625888waf.150.1242669085198; Mon, 18 May 2009 10:51:25 -0700 (PDT) Received: from localhost ([76.231.178.131]) by mx.google.com with ESMTPS id k35sm5419899waf.57.2009.05.18.10.51.17 (version=SSLv3 cipher=RC4-MD5); Mon, 18 May 2009 10:51:17 -0700 (PDT) Date: Mon, 18 May 2009 10:51:15 -0700 (PDT) From: Peter Steele To: David Roberts Message-ID: <9187715.781242668995771.JavaMail.HALO$@halo> In-Reply-To: <26654369.761242668497177.JavaMail.HALO$@halo> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: umass0: BBB reset failed, TIMEOUT X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 May 2009 17:51:26 -0000 >Any ideas? I can't offer any solutions but I can tell you that we've seen this exactly problem, and many times. I have a script that copies a tar image into a USB thumb drive and that operation fails frequently. To better guarantee success, I have to boot the system first, and then the copy command works reliably. If I don't do a reboot, I see this same kind of failure, usually as much as 50% of the time. My impression is that USB drive support is simply not that solid.