From owner-freebsd-questions@FreeBSD.ORG Thu Apr 15 04:16:52 2010 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 7A714106566B for ; Thu, 15 Apr 2010 04:16:52 +0000 (UTC) (envelope-from tj@tjvarghese.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 42DE88FC19 for ; Thu, 15 Apr 2010 04:16:51 +0000 (UTC) Received: by gwaa12 with SMTP id a12so520491gwa.13 for ; Wed, 14 Apr 2010 21:16:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.182.2 with HTTP; Wed, 14 Apr 2010 21:16:48 -0700 (PDT) In-Reply-To: <84707499@bb.ipt.ru> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3B65FA89@MBX03.exg5.exghost.com> <84707499@bb.ipt.ru> Date: Thu, 15 Apr 2010 12:16:48 +0800 Received: by 10.100.21.27 with SMTP id 27mr14578514anu.93.1271305008734; Wed, 14 Apr 2010 21:16:48 -0700 (PDT) Message-ID: From: TJ Varghese To: Boris Samorodov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Peter Steele , "freebsd-questions@freebsd.org" Subject: Re: USB disk boot issues 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: Thu, 15 Apr 2010 04:16:52 -0000 On Mon, Apr 5, 2010 at 4:24 PM, Boris Samorodov wrote: > On Thu, 1 Apr 2010 07:38:53 -0500 Peter Steele wrote: > >> We clone systems from specially prepared USB flash sticks and this all w= orks well, except that occasionally the flash stick fails to boot. It fails= at the "mount root" step, saying that it cannot mount the specified root p= artition. We use a labeled partition on the disk to make it device independ= ent, so we have something like > >> /dev/label/usbroot =C2=A0/ =C2=A0 =C2=A0ufs =C2=A0 =C2=A0rw =C2=A0 =C2= =A0 1 =C2=A0 =C2=A0 =C2=A01 > >> in our fstab. When it fails it doesn't recognize this device, and even ?= doesn't list it as one of the available devices. If we reboot, it's likely= the problem won't occur again. It seems to be some kind of timing issue. I= s this a known problem? > > You can try to solve the problem by: > ----- > # echo "kern.cam.boot_delay=3D10000" >> /boot/loader.conf > ----- above did not work for me, however this did: kern.cam.scsi_delay=3D10000