From owner-freebsd-stable@FreeBSD.ORG Sat Jan 4 07:12:48 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 005CCD4D for ; Sat, 4 Jan 2014 07:12:47 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id B684C19D6 for ; Sat, 4 Jan 2014 07:12:46 +0000 (UTC) Received: from [96.28.178.143] ([96.28.178.143:61500] helo=localhost) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 43/76-14229-524B7C25; Sat, 04 Jan 2014 07:11:34 +0000 Date: Sat, 04 Jan 2014 07:11:33 +0000 Message-ID: <43.76.14229.524B7C25@cdptpa-oedge01> From: "Thomas Mueller" To: freebsd-stable@freebsd.org Subject: How to make boot wait a few seconds more for device response? X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jan 2014 07:12:48 -0000 How do I make boot wait a few seconds more if it can't mount the root device immediately? Device in question is a USB 3.0 USB stick, 32 GB where I installed FreeBSD 10-prerelease i386. Booting process can't mount the root device fast enough, and I get mountroot> prompt. I have succeeded every time in booting, sometimes after several attempts due to not knowing the ddevice name/number. Being able to enter ufs:/dev/gpt/FB10USB3i386-root helps, especially when more than one USB stick is present, and enables me to get it correct the first time. But it still is annoying, and I would like to avoid this extra step, if possible. It seems like a matter of a USB stick not responding as fast as a hard drive, or maybe this USB 3.0 stick is slower for initial response than USB 2.0 sticks.. So how do I tell the system to allow several seconds more? Relevant kernel messages are: Dec 29 21:23:09 amelia4 kernel: ugen1.7: at usbus1 Dec 29 21:23:09 amelia4 kernel: Root mount waiting for: usbus1 Dec 29 21:23:09 amelia4 kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 0 0 00 24 00 Dec 29 21:23:09 amelia4 kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB reque st completed with an error Dec 29 21:23:09 amelia4 kernel: (probe0:umass-sim0:0:0:0): Retrying command Dec 29 21:23:09 amelia4 kernel: ugen1.8: at usbus1 Dec 29 21:23:09 amelia4 kernel: Trying to mount root from ufs:/dev/gpt/FB10USB3i 386-root [rw]... Dec 29 21:23:09 amelia4 kernel: mountroot: waiting for device /dev/gpt/FB10USB3i 386-root ... Dec 29 21:23:09 amelia4 kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 0 0 00 24 00 Dec 29 21:23:09 amelia4 kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB reque st completed with an error Dec 29 21:23:09 amelia4 kernel: (probe0:umass-sim0:0:0:0): Retrying command Dec 29 21:23:09 amelia4 kernel: Mounting from ufs:/dev/gpt/FB10USB3i386-root fai led with error 19. But I am then able to mount this device/partition from mountroot> prompt. By the way, I also notice some instabilities with USB; this is on FreeBSD 10-prerelease amd64 as well as i386: ugen1.4: at usbus1 (disconnected) ums0: at uhub6, port 2, addr 4 (disconnected) ugen1.4: at usbus1 ums0: on usbus1 ums0: 8 buttons and [XYZT] coordinates ID=0 though this mouse is actually connected and responsive all the time. I just checked for 9.2-STABLE amd64 and 11-HEAD i386 and amd64: these USB mouse-related messages don't occur. Now I'm afraid to upgrade to 10.0 on computer where 9.2-STABLE is installed and re(4) works OK. 11-HEAD is stabler than 10-prerelease? FreeBSD version on computer with newer MSI Z77 MPOWER motherboard is 10.0-prelease from about the time of RC3: FreeBSD amelia4 10.0-PRERELEASE FreeBSD 10.0-PRERELEASE #3: Mon Dec 30 01:38:00 UTC 2013 root@amelia4:/usr/obj/usr/src/sys/SANDY10 amd64 Tom