From owner-freebsd-current@freebsd.org  Fri Dec 28 22:12:17 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40C27142466E
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 28 Dec 2018 22:12:17 +0000 (UTC)
 (envelope-from andreast-list@fgznet.ch)
Received: from smtp.fgznet.ch (smtp.fgznet.ch [IPv6:2001:4060:1:1001::14:52])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B558D6DF25
 for <freebsd-current@freebsd.org>; Fri, 28 Dec 2018 22:12:16 +0000 (UTC)
 (envelope-from andreast-list@fgznet.ch)
Received: from [192.168.225.14] (dhclient-91-190-10-49.flashcable.ch
 [91.190.10.49])
 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by fgznet.ch (Postfix) with ESMTPSA id 22D7EC143C;
 Fri, 28 Dec 2018 23:12:06 +0100 (CET)
Subject: Re: r342378 fails sometimes on boot mounting root (error 2)
To: guru@unixarea.de, freebsd-current@freebsd.org
References: <20181228145432.GA2249@c720-r314251>
 <1546013269.78877.85.camel@freebsd.org> <20181228184509.GA2231@c720-r314251>
From: Andreas Tobler <andreast-list@fgznet.ch>
Message-ID: <dd2ef23e-02c1-91a7-ce6a-1eaab5b28cd7@fgznet.ch>
Date: Fri, 28 Dec 2018 23:12:00 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0)
 Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <20181228184509.GA2231@c720-r314251>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: de-CH
Content-Transfer-Encoding: 8bit
X-Scanned-By: Obelix Submit on 127.0.1.1
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Dec 2018 22:12:17 -0000

On 28.12.18 19:45, Matthias Apitz wrote:
> El día viernes, diciembre 28, 2018 a las 09:07:49a. m. -0700, Ian Lepore escribió:
> 
>> Try setting vfs.mountroot.timeout= in loader.conf to a value long
>> enough to let the usb drive get probed reliably. The default is 3
>> seconds, maybe a value like 5 or 10 would work better for you.
>>
>> -- Ian
> 
> Thanks. I did so, but this does not help. When I does not work even
> after 20 secs it fails to mount. After a lot of boot attempts I have the
> following picture:
> 
> 1. It always mounts fine when verbose message is selected.
> 
> 2. It mounts fine when the line below about 'umass0:1:0: Attached to ... ' is
>     printed, if it is not, the mount fails later after 20 secs waiting;
>     

Hm, here on my rpi3b+, with an attached usb disk I have to use this 
setting in loader.conf:

kern.cam.boot_delay="15000"

With the vfs.mountroot.timeout="xx" I end up in a shell because I'm not 
able to mount the partition in time. With the cam.boot_delay things are 
working fine.

Maybe this helps?

Andreas