Date: Thu, 15 Apr 2010 12:16:48 +0800 From: TJ Varghese <tj@tjvarghese.com> To: Boris Samorodov <bsam@ipt.ru> Cc: Peter Steele <psteele@maxiscale.com>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: USB disk boot issues Message-ID: <p2hc7f2adc21004142116jde248a2anb063fb758214785@mail.gmail.com> In-Reply-To: <84707499@bb.ipt.ru> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3B65FA89@MBX03.exg5.exghost.com> <84707499@bb.ipt.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 5, 2010 at 4:24 PM, Boris Samorodov <bsam@ipt.ru> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p2hc7f2adc21004142116jde248a2anb063fb758214785>